Re: Panic on Mac Q700 with 2.2.25
- To: Finn Thain <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: Panic on Mac Q700 with 2.2.25
- From: Steve Brown <firstname.lastname@example.org>
- Date: Tue, 06 Feb 2007 10:10:42 -0700
- Message-id: <1170781842.5268.55.camel@lithium>
- In-reply-to: <Pine.LNX.email@example.com>
- References: <firstname.lastname@example.org> <Pine.LNX.email@example.com>
I am still getting lockups with 2.6.18 after three or four days. I
cannot get a serial console to work with this kernel, nor does the
kernel write the panic text to the syslog. What are my options to best
record the stack trace?
Any other kernels I should try? This machine is only a dumb web server.
I only need the onboard SONIC Ethernet as far as drivers go, though
serial would be nice for debugging like this.
Thanks, Steve Brown
On Sat, 2007-01-27 at 13:30 +1100, Finn Thain wrote:
> That's the SONIC driver bug. It has been fixed in 2.6.
> > What should I do? I would like to keep this system as low-maintenance
> > as possible. Should I upgrade to the 2.4 or 2.6 lines? What is the
> > best stable kernel for Macs these days?
> The Q700 should be ok with this one (depending on what sort of nubus cards
> you want to use with it):
> Only trouble is you'll need to extract the vmlinux.gz and make it
> available to the bootloader under MacOS.
> > Am I using the completely wrong kernel and should I go for the official
> > Debian one?
> No, 2.2.25 is generally OK... you were unlucky. Macs running 2.6 don't yet
> have a working real time clock, so use ntp to set the clock at boot up,
> and disable the timestamp based fsck with tune2fs -i 0 /dev/sdXY before
> you boot into 2.6.
> You'll probably want to upgrade to etch too.