Anyway, has someone been playing with the scsi cd code?
Here is an expert from my /var/log/kern.log (debian system) with some
wierd stuff:
Jan 24 23:14:38 debian kernel: ISO 9660 Extensions: Microsoft Joliet
Level 3
Jan 24 23:14:38 debian kernel: ISOFS: changing to secondary root
Jan 24 23:14:38 debian kernel: sr4: CDROM (ioctl) reports ILLEGAL
REQUEST.
Jan 24 23:14:38 debian last message repeated 2 times
Jan 24 23:14:38 debian kernel: VFS: Disk change detected on device
sr(11,4)
Jan 24 23:15:02 debian kernel: sr4: CDROM (ioctl) reports ILLEGAL
REQUEST.
Jan 24 23:15:02 debian kernel: ISO 9660 Extensions: Microsoft Joliet
Level 3
Jan 24 23:15:02 debian kernel: ISOFS: changing to secondary root
Jan 24 23:15:02 debian kernel: sr5: CDROM (ioctl) reports ILLEGAL
REQUEST.
Jan 24 23:15:02 debian last message repeated 2 times
Jan 24 23:15:02 debian kernel: VFS: Disk change detected on device
sr(11,5)
Jan 24 23:15:14 debian kernel: sr5: CDROM (ioctl) reports ILLEGAL
REQUEST.
Jan 24 23:15:14 debian kernel: ISO 9660 Extensions: RRIP_1991A
Jan 24 23:37:39 debian kernel: sr3: CD-ROM error: Current error sr0b:03:
sense key Illegal Request
Jan 24 23:37:39 debian kernel: Additional sense indicates Logical block
address out of range
Jan 24 23:37:39 debian kernel: command was: Read (10) 60 00 00 e1 c4 00
00 0e 00
2 debian kernel: SCSI CD error : host 0 id 5 lun 0 return code =
28000002
I have noticed, that the couple of times I've witnessed the lockup, I
was accessing the changer. Once playing mp3's from a cd that a friend
burned for me, and once while mounting the cd changer.
I'm not sure which occurance the above log fragment represents.
Hope this helps.
Chris
gandalf wrote:
>
> At 20:59 26.01.99 +0100, you wrote:
> >2.2.0 final locks up on my machine the same way as 2.2.0-pre8-ac1 and
> >2.2.0-pre9 did (I posted the error on the list few days ago).
> >
> I'm experiencing the same problem since pre8. I already posted this a few
> days ago.
> My setup is kinda complex (p200, 64mb,some ide disks, soft raid1, aha-2920
> with 4 7-cd-changers attached, a quickcam running as webcam, some perl
> 'daemons' running an mp3 jukebox, X, samba, netatalk, etc.) , so I really
> can't tell where the problem lies.
> All I can say is that this system has been under _heavy_ load since the
> early 2.0.x kernels and has never had a hard lock-up before.
> CPU load is usually very high, especially when someone's on the webcam and
> mp3 tunes are being played at the same time.
> With only 64mb of RAM, there's quite often swapping...
> Since pre8, I've had about a lock-up a day, in different situations,
> sometimes with nothing than a few idle daemons running under no heavy cpu
> or network load.
> No network response, no response to keyboard input, no kernel oops, nothing
> in the logs.
> All I can do is push the reset button and wait till my raid devices have
> been checked =(
>
> If anyone has an idea, I'm willing to try everything ;)
>
> -
> 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/
-
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/