Tomasz Motylewski wrote:
>
> The kernel reproducibly crashes on boot (while detecting SCSI disks).
>
> scsi0: Adaptec ... 5.2.0/3.2.4
> scsi: 1 host
> (scsi0:0:0:0) Synchronous at 5.0 Mbytes/s offset 15
> kernel BUG at /usr/src/23/linux/include/asm/pci.h:58!
> invalid operand: 0000
> CPU: 1
> EIP: 0010:[<c023a50f>] (c0230e94=sd_init)
> EFLAGS: 00010086
> process swapper (pid 0, stackpage: c1279000)
> call trace: c02ce869, c02cea00, c023f4fd, c023fa07 ...
> CODE: 0f 0b 83 c4 0c 8b 54 24 4c 8b 42 10 81 c7 00 00 00 40 89 38
I had a similar problem.
Try cp .configure ..;make mrproper; cp ../.configure .; make oldconfig
dep bzImage modules; rm -Rf /lib/module/2.3.47/*; make modules_install
Or change the compiler/binutils/linker (maybe use gcc-2.7.2.3).
I don't know where is the problem. The last week, all kernel that I
compiled has the problem (CODE: 0f 0b... is a Pentium code). Upgrading
debian and recompiling the code, now all kernel 2.3.4x works.
The strange is that it happend only on scsi code.
giacomo
> Aiee, killing interrupt handler
> Kernel panic: attempt to kill the idle task
> In interrupt handler, not syncing
>
> System.map and .config in http://crds.chemie.unibas.ch/linux/2.3.47pre6/
> http://crds.chemie.unibas.ch/linux/2.2.15/messages contains dmesg from
> 2.3.43pre3 being run on the same machine.
>
> Regards,
> --
> Tomasz Motylewski
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:30 EST