Hi,
Yeah I've had this bug for a while. From kernels 2.0.35 =>
2.2.0-pre7 which is what I'm currently using. Could it be an SMP problem?
Thanks,
~~Kev
On Sun, 24 Jan 1999, Gerard Roudier wrote:
>
>
> On Sun, 24 Jan 1999, Kevin Z Grey wrote:
>
> > Hello PPL,
> >
> > I've got 2 scsi cdroms on my scsi chain. The first is a
> > Plextor cd-r that is mountable. The second is a Pioneer DR-506S which
> > whenever the cd-r is on the chain, will not be mountable. If I remove the
> > cd-r from the chain the cdrom works perfectly. Now I haven't been able to
> > define this as a non-jumper termination problem. The cdrom (I was told)
> > was set as terminant, and the cd-r was non-terminant. They both have
> > different IDs also. Here is some info on my system:
> >
> > Motherboard: ASUS P2B-D
> > SCSI card: Symbios Logic SYM8951U
> > SCSI card: Symbios Logic 875
> >
> > I think this is the error: Anyone know what it means, or can tell me how
> > to remedy it?
> >
> > Jan 17 11:08:25 kevlar kernel: sr1: CDROM (ioctl) error, command: Mode Sense 00 2a
>00 80 00
> > Jan 17 11:08:25 kevlar kernel: extra data not valid Current error sr00:00: sense
>key Aborted Command
> > Jan 17 11:08:25 kevlar kernel: Additional sense indicates Initiator detected error
>message received
>
> It means, at least, that you have triggerred some buglet in the kernel,
> since the command failed and the code bahaves as it had succeeded, given
> the next message.
>
> > Jan 17 11:08:25 kevlar kernel: sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda
>tray
>
> Apart the kernel buglet that doesn't look like the cause of the problem,
> the error is indeed very strange.
>
> - "sr00:00" in the 2nd message claims that the involved device is MAJOR 0,
> MINOR 0 that does not match the sr1 device.
>
> - The device said "Initiated detector message received", but the ncr
> driver tries sending such a message only in case of parity error and
> prints out a loudly message to the log (I didn't see any in your log).
>
> [ ... ]
>
> > sr1: CDROM (ioctl) error, command: Read TOC 00 00 00 00 00
> > 00 00 0c 40
> > extra data not valid Current error sr00:00: sense key Aborted Command
> > Additional sense indicates Initiator detected error message received
>
> Same problem there.
>
> [ ... ]
>
> > Thanks for making it this far, and please don't rip me too hard if there's
> > a really simple solution, I'm very new to scsi.
>
> Did you give a 2.0 kernel (2.0.36 for example) a try ?
> If not, you should, at least to see if it makes difference.
>
>
> G�rard.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
