On Tue, 6 Feb 2007, Christian T. Steigies wrote:
> On Tue, Feb 06, 2007 at 10:10:42AM -0700, Steve Brown wrote:
> > 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
> Unfortunately the Falcon is continously crashing now, maybe I have to clock
> it down. But it seems I have also lost the software to slow down the
> clock... so I found xcontrol and put xcontrol.acc in C:, now I get a
> segfault during boot. Yeah, how do I get around that? Does zcontrol work any
On Tue, Feb 06, 2007 at 10:10:42AM -0700, Steve Brown wrote:
> 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?
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
> > > Yes, SCSI is disabled, but if you say it works, I can try. Thee is not
> > > much
> >
> > Please do - if you have all my patches it should work (i.e. recover from
> > timeout/reset cycles).
>
> I've built one with SCSI drivers, it will appear as:
>
> http://people.debian.org/~cts/debian-m68k
5 matches
Mail list logo
