Doug McNaught:
> Have you tried 2.4.21pre? It may have fixes to handle newer hardware.
Not yet, I did try 2.4.19, to see if that worked better, but got the
same crash. 2.4.18 seems to be different, however, since it does not
autodetect the drives (and does not crash when I pass the IDE addresses
manually).
> Does the machine pass memtest86?
No errors were reported.
Mark Hahn:
> well, posting an undecoded oops is one mistake.
Someone decoded it and posted a decoded trace. Did that not arrive to
the list properly?
> can you dispense with the silly hardware dumb-raid, and just use
> kernel software raid? (faster, more robust).
I'd prefer to use the on-board RAID to be compatible with other OSes.
And, according to people I have asked, the Linux software-RAID is not
very reliable either, so I don't feel especially inclined to switch.
> I decoded your oops, below. it's not much use without someone also
> running objdump -D drivers/block/ll_rw_blk.o on your system and
> figuring out how the eip=0 happened. it's obviously some callback.
If I run this (I can boot the machine using 2.4.18), what should I
look for? I haven't debugged the kernel before, it has just always
worked for me, on all the machines I've tried it. I've only ever had
the kernel crash once on me before since 1996.
> it's also somewhat odd that prink is in the backtrace.
That might be a typo on my part.
> there are no printk's before the oops?
The last thing that happens before the crash is that it tries to
enumerate the hard disk partitions. I lists a few but then crashes.
-- \\// Peter - http://www.softwolves.pp.se/I do not read or respond to mail with HTML attachments.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jan 31 2003 - 22:00:15 EST