>     Interesting.  The bus scan is still taking place - it is probably poking
> at unit 7 here.  The fact that it has printed out the result for 6 is quite
> odd - it indicates that the thing actually did return somewhat intelligent
> data for LUN 6, but it did the right thing for lun 5.  This thing probably
> has some buggy firmware.  Anyways, moving on....
> 
>     The single lun thing won't help you at this level.   It is serially
> poking at the devices one at a time to learn more about them.  Offhand I am
> guessing that the firmware for the thing is slowing going insane.  For
> testing purposes, you might add the max_scsi_luns=5 boot parameter - this
> will prevent it from probing logical units 5, 6 and 7.

Okay, well booting with max_scsi_luns=5 and then insmod BusLogic (manually
again, after bootup) yields:

scsi0 : BusLogic BT-930
scsi : 1 host.
  Vendor: LASOUND   Model: CDX7405           Rev: 3.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
  Vendor: LASOUND   Model: CDX7405           Rev: 3.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
  Vendor: LASOUND   Model: CDX7405           Rev: 3.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
  Vendor: LASOUND   Model: CDX7405           Rev: 3.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
  Vendor: LASOUND   Model: CDX7405           Rev: 3.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
scsi0: Target 3: Queue Depth 3, Synchronous at 3.33 MB/sec, offset 8

which is much better.  The insmod also finishes right away.

> > wait_on_bh, CPU 0:
> > irq:  0 [0 0]
> > bh:   1 [0 1]
> > <[c010b35d]> <[c01a0c4c]> <[c0140d93]> <[c01a17eb]> <[c01a6c10]>
> <[c0198c84]>  <5>scsi0: Target 3: Queue Depth 3, Asynchronous
> > Unable to handle kernel NULL pointer dereference at virtual address
> 00000003
> > current->tss.cr3 = 07142000, %cr3 = 07142000
> > *pde = 00000000
> > Oops: 0000
> > CPU:    1
> 
>     Probably the error handling code going nuts.  You need to take the
> kernel addresses and work back to function names and offsets.

Ewww..  Is there value in this?

Now, upon mount -t iso9660 /dev/scd0 /local/cdx01, after a lot of mechanism
ka-chunking, I get (in the log):

Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
Detected scsi CD-ROM sr1 at scsi0, channel 0, id 3, lun 1
Detected scsi CD-ROM sr2 at scsi0, channel 0, id 3, lun 2
Detected scsi CD-ROM sr3 at scsi0, channel 0, id 3, lun 3
Detected scsi CD-ROM sr4 at scsi0, channel 0, id 3, lun 4
sr0: scsi3-mmc drive: 0x/0x caddy
sr1: scsi3-mmc drive: 0x/0x caddy
sr2: scsi3-mmc drive: 0x/0x caddy
sr3: CDROM (ioctl) error, command: Mode Sense 60 2a 00 80 00 
[valid=0] Info fld=0x0, Current sr00:00: sense key Hardware Error
Additional sense indicates Mechanical positioning error
sr3: scsi3-mmc drive: 0x/0x caddy
sr4: CDROM (ioctl) error, command: Mode Sense 80 2a 00 80 00 
[valid=0] Info fld=0x0, Current sr00:00: sense key Hardware Error
Additional sense indicates Mechanical positioning error
sr4: scsi3-mmc drive: 0x/0x caddy

which is strange.  Similar to last night, it doesn't seem to like
sr3 or sr4.  What is "sense key Hardware Error", "Additional sense
indicates Mechanical positioning error"?  Is this a physical
drive defect?  Should I return the drive?

I can also mount the second and third platter, but trying to 
mount the fourth platter yields:

sr3: CDROM (ioctl) error, command: Test Unit Ready 60 00 00 00 00 
[valid=0] Info fld=0x0, Current sr00:00: sense key Hardware Error
Additional sense indicates Mechanical positioning error
cdrom: open failed.
scsi : aborting command due to timeout : pid 69, scsi0, channel 0, id 3, lun 3 Test 
Unit Ready 60 00 00 00 00 
scsi0: Aborting CCB #76 to Target 3
SCSI host 0 abort (pid 69) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Sending Bus Device Reset CCB #77 to Target 3
SCSI host 0 channel 0 reset (pid 69) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-930 due to Target 3
scsi0: *** BusLogic BT-930 Initialized Successfully ***

wait_on_bh, CPU 1:
irq:  0 [0 0]
bh:   1 [1 0]
<[c010b35d]> <[c01a0c4c]> <[c0140d93]> <[c01a17eb]> <[c01a6c10]> <[c0198c84]> <3>sr3: 
CDROM (ioctl) error, command: Read TOC 60 00 00 00 00 00 00 0c 40 
[valid=0] Info fld=0x0, Current sr00:00: sense key Hardware Error
Additional sense indicates Mechanical positioning error
sr3: CDROM (ioctl) error, command: Read TOC 60 00 00 00 00 00 00 0c 00 
[valid=0] Info fld=0x0, Current sr00:00: sense key Hardware Error
Additional sense indicates Mechanical positioning error

until mount returns

mount: No medium found

By the way there's a lot of mechanism ka-chunking during this [failed]
mount.  Mounting the fifth platter does the same thing.  After a lot of
scsi bus resets, I kernel panic the same way I did last time with the
"in swapper task--not syncing".

I started to wonder about the 4th and 5th slots...  ...two MSDEV CDs.
Oh well, I had to put something in there!  I replaced them with SuSE
CDs, we'll see what happens.

[re: kernel panic]

>     Yow.  That should never happen.  Does this happen right away?  If this
> comes up again (and repeatably) you could turn up logging to infinity and
> you will get a lot more details about the last thing that happened with
> success.

Yes, it happened right away after I tried to mount the second lun.  This
last time it somewhere in a myriad of scsi resets while I tried to mount
the fourth and fifth platters...  It seems to be repeatable, but I don't 
know which is the exact [fatal] step.
 

Brendan

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to