Kernel panic: Loop 1 (aic7xxx driver)
Since kernel version 2.4.9 I haven't compiled a kernel until recently. With 2.4.17 I always got the "Kernel panic: Loop 1" from the aic7xxx driver. When I removed this driver the kernel started correctly. My research on the net showed that "Gregoire Favre (Kernel panic: Loop 1 (aic7xxx under 2.4.13-ac[246]))" has the same problem as I and his report is almost exactly as mine. I won't write mine here since I don't know how to save it into a file, anything is lost after the hard reset (does anybody know how to save/retrieve kernel messages after a panic?).
Well but I can give a hint where to look for since the problem disappears when I compile the aic7xxx driver into the kernel. If (with make menuconfig) the option "SCSI support" and the low level driver "Adaptec aic7xxx support" is set to "M" the problem occurs. It occurs only if the option _"SCSI support"_ is set to "M". I guess only very few people use this option.
O. Wyss
Signature · 2 lines
Author of "Debian partial mirror synch script"
("http://dpartialmirror.sourceforge.net/")The easiest way is to use a serial console. Maybe you should have a look at
http://kgdb.sourceforge.net/, too.
Greetings,
Thomas
Quoted 25 lines · Otto Wyss
Since kernel version 2.4.9 I haven't compiled a kernel until recently. With 2.4.17 I always got the "Kernel panic: Loop 1" from the aic7xxx driver. When I removed this driver the kernel started correctly. My research on the net showed that "Gregoire Favre (Kernel panic: Loop 1 (aic7xxx under 2.4.13-ac[246]))" has the same problem as I and his report is almost exactly as mine. I won't write mine here since I don't know how to save it into a file, anything is lost after the hard reset (does anybody know how to save/retrieve kernel messages after a panic?).
Well but I can give a hint where to look for since the problem disappears when I compile the aic7xxx driver into the kernel. If (with make menuconfig) the option "SCSI support" and the low level driver "Adaptec aic7xxx support" is set to "M" the problem occurs. It occurs only if the option _"SCSI support"_ is set to "M". I guess only very few people use this option.
O. Wyss
--
Author of "Debian partial mirror synch script" ("http://dpartialmirror.sourceforge.net/")
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines
Since kernel version 2.4.9 I haven't compiled a kernel until recently. With 2.4.17
If you are using 2.4.17, apply the patch to upgrade your driver to version 6.2.5 which corrects this problem:
http://people.FreeBSD.org/~gibbs/linux/
A patch for 2.4.18-rc will be made available as soon as I have a bit more testing on it - probably tomorrow morning.
--
Justin