Bug#459732: linux-image-2.6.23-1-amd64: scsi changer device not working - error in scsi subsystem
On Tue, Jan 08, 2008 at 12:57:44PM +0100, Thomas Kotzian wrote:
> the media changer device doesn't work. on startup an error -EEXIST for a ch kobject gets triggered.
>
> linux-image-2.6.21-2-amd64 (2.6.21-6) works
> every kernel later (even upstream) doesn't
>
> the working snippet ...
>
> ch0: type #1 (mt): 0x1+1 [medium transport]
> ch0: type #2 (st): 0x1000+81 [storage]
> ch0: type #3 (ie): 0x10+6 [import/export]
> ch0: type #4 (dt): 0x100+2 [data transfer]
> ch0: dt 0x100: ID/LUN unknown
> ch0: dt 0x101: ID/LUN unknown
> ch0: INITIALIZE ELEMENT STATUS, may take some time ...
> ch0: ... finished
> ch 2:0:0:1: Attached scsi changer ch0
> sd 1:0:0:0: Attached scsi generic sg0 type 0
> st 0:0:0:0: Attached scsi generic sg1 type 1
> sd 3:0:0:0: Attached scsi generic sg2 type 0
> st 2:0:0:0: Attached scsi generic sg3 type 1
> ch 2:0:0:1: Attached scsi generic sg4 type 8
>
> the failing snippet ...
>
> scsi 2:0:0:1: Medium Changer ADIC Scalar i500 400G PQ: 0 ANSI: 3
> kobject_add failed for 2:0:0:1 with -EEXIST, don't try to register things with the same name in the same directory.
>
> Call Trace:
> [<ffffffff802febc0>] kobject_shadow_add+0x16e/0x1a2
> [<ffffffff80365450>] device_add+0x99/0x614
> sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled, doesn't support DPO or FUA
> [<ffffffff8805955a>] :scsi_mod:scsi_sysfs_add_sdev+0x35/0x218
> [<ffffffff88057640>] :scsi_mod:scsi_probe_and_add_lun+0x953/0xa95
> [<ffffffff88055f7f>] :scsi_mod:scsi_execute_req+0x82/0xde
> [<ffffffff88058041>] :scsi_mod:__scsi_scan_target+0x407/0x5c3
> [<ffffffff880587d0>] :scsi_mod:scsi_scan_target+0x96/0xbb
> [<ffffffff880b49ed>] :scsi_transport_fc:fc_scsi_scan_rport+0x59/0x7a
> [<ffffffff880b4994>] :scsi_transport_fc:fc_scsi_scan_rport+0x0/0x7a
> [<ffffffff80243481>] run_workqueue+0x7f/0x10b
> [<ffffffff80243db8>] worker_thread+0x0/0xe4
> [<ffffffff80243e92>] worker_thread+0xda/0xe4
> [<ffffffff80246b96>] autoremove_wake_function+0x0/0x2e
> [<ffffffff80246a79>] kthread+0x47/0x76
> [<ffffffff8020cc08>] child_rip+0xa/0x12
> [<ffffffff80246a32>] kthread+0x0/0x76
> [<ffffffff8020cbfe>] child_rip+0x0/0x12
>
> error 1
> st 2:0:0:0: Unexpected response from lun 1 while scanning, scan aborted
> sd 3:0:0:0: [sdb] 1874933760 512-byte hardware sectors (959966 MB)
> sd 3:0:0:0: [sdb] Write Protect is off
> sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
> sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled, doesn't support DPO or FUA
> sdb: sdb4 < sdb5 >
> sd 3:0:0:0: [sdb] Attached SCSI disk
> SCSI Media Changer driver v0.25
> ch 2:0:0:1: rejecting I/O to dead device
> ch0: type #1 (mt): 0x0+0 [medium transport]
> ch0: type #2 (st): 0x0+0 [storage]
> ch0: type #3 (ie): 0x0+0 [import/export]
> ch0: type #4 (dt): 0x0+0 [data transfer]
> ch0: INITIALIZE ELEMENT STATUS, may take some time ...
> ch 2:0:0:1: rejecting I/O to dead device
> ch0: ... finished
> ch 2:0:0:1: Attached scsi changer ch0
> st 1:0:0:0: Attached scsi generic sg0 type 1
> sd 0:0:0:0: Attached scsi generic sg1 type 0
> st 2:0:0:0: Attached scsi generic sg2 type 1
> ch 2:0:0:1: Attached scsi generic sg3 type 8
> sd 3:0:0:0: Attached scsi generic sg4 type 0
nice, please check out 2.6.23-rc7 from trunk and
see if it makes a difference, see apt lines
-> http://wiki.debian.org/DebianKernel
if aboves makes *no* progress, then please holler
upstream in bugzilla.kernel.org and let us know
the upstream bug number.
debian carries no scsi specific patches, although
the changer was long time such a boy.
best regards
--
maks
Reply to: