Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

The crash occurs whenever I try to switch vts (Alt-F1, from one MDA 
console to another MDA console, using mdacon compiled for this kernel) 
while running make bzImage or even make dep.  It occurs with my vesafb 
kernel with scsi support compiled in, without scsi support compiled in but 
with it as modules, and with David's 2.2.16 kernel without any scsi 
support.  It does not occur with the standard zimage for BL2 or with the 
kernel that I compiled similar to the above but no framebuffer.

So it is framebuffer related.  I will try to reproduce it on another 
computer with a framebuffer kernel.  It may be specific to this 
motherboard, which during boot gave some message about hdb timed out 
waiting for... and IRQ timeout (these did not remain in dmesg- would 
syslogd catch them?).  I had replaced a previous hdb trying to fix this 
message, and also turned off UDMA in CMOS because I was getting timouts 
during operation.  I might try turning it off again.

Does framebuffer use DMA oddly?


On Mon, 19 Dec 2005, sindi keesan wrote:

> Does BL2 keep a log of error messages produced just before a crash?
> Or do I need to start some program to keep the log?
>
> After I upgraded one computer from 350 to 500MHz (AMD K6-2) and also
> switched to a kernel that I compiled with added scsi (general and sd) and
> framebuffer (vesafb) support, I have had three sudden crashes, including
> two freezes, and just now when I switched vts:
> unable to handle kernel NULL pointer dereference at virtual address:.....
> .....
> oops:0000
> ....killing interrupt handler
>
> The keyboard also acted screwy a few times - either stopped responding at
> all, or keys started typing double (some not at all).  Interrupt problem?
>
> I was online now and at least one time when the keyboard acted up.
>
> /proc/interrupts - keyboard 1, serial 3
>
> Web research implies this is some sort of kernel bug, possibly related to
> scsi.  I would like to record the whole message from last time or at least
> next time.
>
> If I run syslogd it will put something into /var/log/messages (currently
> empty) - is this the answer?
>
> If it is a scsi problem in 2.2.16, I will switch to a 2.4.31 kernel which
> David has offered to compile with the same config, for the scsi computers.
>
> keesan AT sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org