'The Joshua Tree'-Bug
I had a Kernel Panic today on my Debian system and was able to reproduce
it. The message displayed was:
Kernel Panic: scsi: trying to call schedule() in interrupt, file scsi.c,
line 1370
In swapper task - not syncing
The Panic was followed by timeouts on the scsi bus.
My system is as follows:
Amiga 1200 / Blizzard 1260/50 / 16 MB ram / BlizzardIV scsi / 4GB scsi
on ID 0 / HP Surestore CD-Writer on ID 1 / 4 GB scsi on ID 2 / 'The
Joshua Tree' CD from U2 inserted in the CD-rom / Debian Hamm / Kernel
Linuxm68k 2.0.29
The CD seems important. I copied another CD before that, which worked
just fine. The first one had only 10 tracks, whereas this one has 11 +
lead-out and the panic comes at the end or after track 11.
How i got the kernel panic:
I loged in as root and changed to an AFFS partition, there I did
> ~/ripCD (which contains the following)
>> cdda2wav -D /dev/sg1 -t 1 -b 8 track01.wav
>> cdda2wav -D /dev/sg1 -t 2 -b 8 track02.wav
...
>> cdda2wav -D /dev/sg1 -t 10 -b 8 track10.wav
>> cdda2wav -D /dev/sg1 -t 11 -b 8 track11.wav
It panics at the end of this one.
>> cdda2wav -D /dev/sg1 -t 12 -b 8 track12.wav
...
The disk has 11 tracks and a lead-out. Doing the same causes the same
kernel panic again, same file, same line. A nearly full output of the
errors comes now:
The first time it said the following:
SCSI disk error: host 0 channel 0 id 2 lun 0 return code=5000
scsidisk I/O error: dev 08:12, sector 211364
Kernel panic: scsi: trying to call schedule() in interrupt, file scsi.c,
line 1370
In swapper task - not syncing
scsi: aborting command due to timeout: pid 44615, scsi 0, channel 0, ide
2, lun 0 Write(6) 04 94 46 F4 00
SCSI disk error: dev 08:12, sector 211362
scsi: aborting command due to timeout: pid 44614, scsi 0, channel 0, ide
2, lun 0 Write(10) 00 00 31 9C 0a 00 00 02 00
scsidisk I/O error: dev 08:05, sector 163850
....
The second time it showed two kernel panics, and some scsi errors like
the once above:
Kernel panic: scsi: trying to call schedule() in interrupt, file scsi.c,
line 1370
In swapper task - not syncing
...
Kernel panic: EXT2-FS panic (device 08:05): ext2_write_inode: unable to
read i-node block - inode = 19608 block 81925
...
I think the EXT2-FS panic is caused because teh scsibus can't recover
from the first error.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: