In article <3DAE8E90.D3E7CACF@aitel.hist.no>,
Helge Hafting <helgehaf@aitel.hist.no> wrote:
| Helge Hafting wrote:
|
| > It produced a backtrace so long that most of it
| > scrolled off the screen, before stating that
| > it didn't sync in an interrupt handler.
| >
| Some of the functions in the trace was scsi stuff.
| I have a tekram scsi controller, driven by
| "SYM53C8XX Version 2 SCSI support"
|
| The crash happens immediately after initializing
| the controller and discovering the two
| disks. This is where autodetection
| of RAID usually happens.
| So it seems to me that it is either some
| scsi problem, or a RAID problem.
|
| The problem affects both 2.5.43 and 2.5.43-mm2.
Is it an OOPS or just a BUG? I got a BUG until I applied the patch, now
my SCSI devices don't actually work, but I don't get an OOPS.
See my other post on the patch, or write my off-list if you can't find it.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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 : Wed Oct 23 2002 - 22:00:47 EST