Re: 2.6.39 and Powerfile c200

Re: 2.6.39 and Powerfile c200

[Stefan Richter]

(Cc: lsml)

On May 27 Jonathan Isom wrote to linux1394-user:
> After upgrading to 2.6.39,  I'm getting "rejecting I/O to offline
> device" repeatedly in dmesg.  Full log is attached.
> I can load disks into the DVD drives, however the drives a not usable.
>  The Powerfile C200 is a 200 Disk DVD
> Changer with 2 drives. I didn't turn on the Changer till 249508.718311.

Which is:

[249508.718311] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[249509.320382] firewire_core: created device fw1: GUID 003060f200002759, S400
[249509.458787] scsi8 : SBP-2 IEEE-1394
[249509.659575] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
[249509.661749] scsi 8:0:0:0: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
[249509.666218] sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
[249509.666479] sr 8:0:0:0: Attached scsi CD-ROM sr1
[249509.666611] sr 8:0:0:0: Attached scsi generic sg5 type 5
[249509.668791] firewire_sbp2: fw1.0: logged in to LUN 0001 (0 retries)
[249509.671056] scsi 8:0:0:1: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
[249509.676162] sr2: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
[249509.676385] sr 8:0:0:1: Attached scsi CD-ROM sr2
[249509.676514] sr 8:0:0:1: Attached scsi generic sg6 type 5
[249509.678677] firewire_sbp2: fw1.0: logged in to LUN 0002 (0 retries)
[249509.683634] scsi 8:0:0:2: Medium Changer    Escient  Powerfile C200   04A  PQ: 0 ANSI: 3

OK.

[249509.685951] ch0: reading element address assigment page failed!

Don't know if this is bad or not.

[249509.685962] ch0: INITIALIZE ELEMENT STATUS, may take some time ...
[249509.686719] ch0: ... finished
[249509.686729] ch 8:0:0:2: Attached scsi changer ch0
[249509.686948] ch 8:0:0:2: Attached scsi generic sg7 type 8

OK.

[249539.712075] firewire_sbp2: fw1.0: sbp2_scsi_abort
[249549.712062] firewire_sbp2: fw1.0: sbp2_scsi_abort
[249549.712287] sr 8:0:0:0: Device offlined - not ready after error recovery
[249549.712393] sr 8:0:0:0: rejecting I/O to offline device
[249583.704061] firewire_sbp2: fw1.0: sbp2_scsi_abort
[249593.704070] firewire_sbp2: fw1.0: sbp2_scsi_abort
[249593.704307] sr 8:0:0:1: Device offlined - not ready after error recovery
[249593.704423] sr 8:0:0:1: rejecting I/O to offline device
[249593.706254] sr 8:0:0:0: rejecting I/O to offline device
[249593.706276] sr 8:0:0:0: rejecting I/O to offline device
[249593.706948] sr 8:0:0:0: rejecting I/O to offline device
[249593.706976] sr 8:0:0:0: rejecting I/O to offline device
[249593.709258] sr 8:0:0:1: rejecting I/O to offline device
[...repeated almost 2000 times...]
[250542.004258] sr 8:0:0:0: rejecting I/O to offline device
[250542.004269] sr 8:0:0:0: rejecting I/O to offline device
[250542.004340] sr 8:0:0:1: rejecting I/O to offline device
[250542.004350] sr 8:0:0:1: rejecting I/O to offline device

All three SCSI units were probed and attached successfully.  This involves
successful execution of a few basic SCSI commands.

30 seconds after that, and again after additional 10 seconds and further
34 seconds + additional 10 seconds, firewire-sbp2 logs that in total four
SCSI commands timed out.  The kernel's SCSI subsystem decides to take the
two DVD-ROM logical units offline.

Why the time-outs happened is is not clear.  Also, I have no idea what
could be done with the kernel's SCSI subsystem so that it logs *which*
commands timed out.

Was the 2.6.39 kernel update the only change that you did on your system,
or were there userland updates too?  If yes, maybe you have a program now
that sends weird commands that crash the Powerfile's firmware.
-- 
Stefan Richter
-=====-==-== -=-= ===--
http://arcgraph.de/sr/

Re: 2.6.39 and Powerfile c200

[Jonathan Isom]

On Sat, May 28, 2011 at 1:26 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> (Cc: lsml)
>
> On May 27 Jonathan Isom wrote to linux1394-user:
>> After upgrading to 2.6.39,  I'm getting "rejecting I/O to offline
>> device" repeatedly in dmesg.  Full log is attached.
>> I can load disks into the DVD drives, however the drives a not usable.
>>  The Powerfile C200 is a 200 Disk DVD
>> Changer with 2 drives. I didn't turn on the Changer till 249508.718311.
>
> Which is:
>
> [249508.718311] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
> [249509.320382] firewire_core: created device fw1: GUID 003060f200002759, S400
> [249509.458787] scsi8 : SBP-2 IEEE-1394
> [249509.659575] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
> [249509.661749] scsi 8:0:0:0: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
> [249509.666218] sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
> [249509.666479] sr 8:0:0:0: Attached scsi CD-ROM sr1
> [249509.666611] sr 8:0:0:0: Attached scsi generic sg5 type 5
> [249509.668791] firewire_sbp2: fw1.0: logged in to LUN 0001 (0 retries)
> [249509.671056] scsi 8:0:0:1: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
> [249509.676162] sr2: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
> [249509.676385] sr 8:0:0:1: Attached scsi CD-ROM sr2
> [249509.676514] sr 8:0:0:1: Attached scsi generic sg6 type 5
> [249509.678677] firewire_sbp2: fw1.0: logged in to LUN 0002 (0 retries)
> [249509.683634] scsi 8:0:0:2: Medium Changer    Escient  Powerfile C200   04A  PQ: 0 ANSI: 3
>
> OK.
>
> [249509.685951] ch0: reading element address assigment page failed!
>
> Don't know if this is bad or not.
>
> [249509.685962] ch0: INITIALIZE ELEMENT STATUS, may take some time ...
> [249509.686719] ch0: ... finished
> [249509.686729] ch 8:0:0:2: Attached scsi changer ch0
> [249509.686948] ch 8:0:0:2: Attached scsi generic sg7 type 8
>
> OK.
>
> [249539.712075] firewire_sbp2: fw1.0: sbp2_scsi_abort
> [249549.712062] firewire_sbp2: fw1.0: sbp2_scsi_abort
> [249549.712287] sr 8:0:0:0: Device offlined - not ready after error recovery
> [249549.712393] sr 8:0:0:0: rejecting I/O to offline device
> [249583.704061] firewire_sbp2: fw1.0: sbp2_scsi_abort
> [249593.704070] firewire_sbp2: fw1.0: sbp2_scsi_abort
> [249593.704307] sr 8:0:0:1: Device offlined - not ready after error recovery
> [249593.704423] sr 8:0:0:1: rejecting I/O to offline device
> [249593.706254] sr 8:0:0:0: rejecting I/O to offline device
> [249593.706276] sr 8:0:0:0: rejecting I/O to offline device
> [249593.706948] sr 8:0:0:0: rejecting I/O to offline device
> [249593.706976] sr 8:0:0:0: rejecting I/O to offline device
> [249593.709258] sr 8:0:0:1: rejecting I/O to offline device
> [...repeated almost 2000 times...]
> [250542.004258] sr 8:0:0:0: rejecting I/O to offline device
> [250542.004269] sr 8:0:0:0: rejecting I/O to offline device
> [250542.004340] sr 8:0:0:1: rejecting I/O to offline device
> [250542.004350] sr 8:0:0:1: rejecting I/O to offline device
>
> All three SCSI units were probed and attached successfully.  This involves
> successful execution of a few basic SCSI commands.
>
> 30 seconds after that, and again after additional 10 seconds and further
> 34 seconds + additional 10 seconds, firewire-sbp2 logs that in total four
> SCSI commands timed out.  The kernel's SCSI subsystem decides to take the
> two DVD-ROM logical units offline.
>
> Why the time-outs happened is is not clear.  Also, I have no idea what
> could be done with the kernel's SCSI subsystem so that it logs *which*
> commands timed out.
>
> Was the 2.6.39 kernel update the only change that you did on your system,
> or were there userland updates too?  If yes, maybe you have a program now
> that sends weird commands that crash the Powerfile's firmware.

I have done some updates. Been messing around trying to get it
working. I'm getting
the same problem with 2.6.38.2.  At one point I got a drive to work
under 2.6.39, but not
the other drive and the changer failed to show.  I got an older
firewire mac I'll try messing
with it later to see if there is a failure in the Powerfile.

Thanks for the input.

Jonathan


> --
> Stefan Richter
> -=====-==-== -=-= ===--
> http://arcgraph.de/sr/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.39 and Powerfile c200

[Jonathan Isom]

On Sat, May 28, 2011 at 3:32 PM, Jonathan Isom <jeisom@gmail.com> wrote:
> On Sat, May 28, 2011 at 1:26 PM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>> (Cc: lsml)
>>
>> On May 27 Jonathan Isom wrote to linux1394-user:
>>> After upgrading to 2.6.39,  I'm getting "rejecting I/O to offline
>>> device" repeatedly in dmesg.  Full log is attached.
>>> I can load disks into the DVD drives, however the drives a not usable.
>>>  The Powerfile C200 is a 200 Disk DVD
>>> Changer with 2 drives. I didn't turn on the Changer till 249508.718311.
>>
>> Which is:
>>
>> [249508.718311] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
>> [249509.320382] firewire_core: created device fw1: GUID 003060f200002759, S400
>> [249509.458787] scsi8 : SBP-2 IEEE-1394
>> [249509.659575] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
>> [249509.661749] scsi 8:0:0:0: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
>> [249509.666218] sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
>> [249509.666479] sr 8:0:0:0: Attached scsi CD-ROM sr1
>> [249509.666611] sr 8:0:0:0: Attached scsi generic sg5 type 5
>> [249509.668791] firewire_sbp2: fw1.0: logged in to LUN 0001 (0 retries)
>> [249509.671056] scsi 8:0:0:1: CD-ROM            TOSHIBA  DVD-ROM SD-M1212 1032 PQ: 0 ANSI: 0 CCS
>> [249509.676162] sr2: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
>> [249509.676385] sr 8:0:0:1: Attached scsi CD-ROM sr2
>> [249509.676514] sr 8:0:0:1: Attached scsi generic sg6 type 5
>> [249509.678677] firewire_sbp2: fw1.0: logged in to LUN 0002 (0 retries)
>> [249509.683634] scsi 8:0:0:2: Medium Changer    Escient  Powerfile C200   04A  PQ: 0 ANSI: 3
>>
>> OK.
>>
>> [249509.685951] ch0: reading element address assigment page failed!
>>
>> Don't know if this is bad or not.
>>
>> [249509.685962] ch0: INITIALIZE ELEMENT STATUS, may take some time ...
>> [249509.686719] ch0: ... finished
>> [249509.686729] ch 8:0:0:2: Attached scsi changer ch0
>> [249509.686948] ch 8:0:0:2: Attached scsi generic sg7 type 8
>>
>> OK.
>>
>> [249539.712075] firewire_sbp2: fw1.0: sbp2_scsi_abort
>> [249549.712062] firewire_sbp2: fw1.0: sbp2_scsi_abort
>> [249549.712287] sr 8:0:0:0: Device offlined - not ready after error recovery
>> [249549.712393] sr 8:0:0:0: rejecting I/O to offline device
>> [249583.704061] firewire_sbp2: fw1.0: sbp2_scsi_abort
>> [249593.704070] firewire_sbp2: fw1.0: sbp2_scsi_abort
>> [249593.704307] sr 8:0:0:1: Device offlined - not ready after error recovery
>> [249593.704423] sr 8:0:0:1: rejecting I/O to offline device
>> [249593.706254] sr 8:0:0:0: rejecting I/O to offline device
>> [249593.706276] sr 8:0:0:0: rejecting I/O to offline device
>> [249593.706948] sr 8:0:0:0: rejecting I/O to offline device
>> [249593.706976] sr 8:0:0:0: rejecting I/O to offline device
>> [249593.709258] sr 8:0:0:1: rejecting I/O to offline device
>> [...repeated almost 2000 times...]
>> [250542.004258] sr 8:0:0:0: rejecting I/O to offline device
>> [250542.004269] sr 8:0:0:0: rejecting I/O to offline device
>> [250542.004340] sr 8:0:0:1: rejecting I/O to offline device
>> [250542.004350] sr 8:0:0:1: rejecting I/O to offline device
>>
>> All three SCSI units were probed and attached successfully.  This involves
>> successful execution of a few basic SCSI commands.
>>
>> 30 seconds after that, and again after additional 10 seconds and further
>> 34 seconds + additional 10 seconds, firewire-sbp2 logs that in total four
>> SCSI commands timed out.  The kernel's SCSI subsystem decides to take the
>> two DVD-ROM logical units offline.
>>
>> Why the time-outs happened is is not clear.  Also, I have no idea what
>> could be done with the kernel's SCSI subsystem so that it logs *which*
>> commands timed out.
>>
>> Was the 2.6.39 kernel update the only change that you did on your system,
>> or were there userland updates too?  If yes, maybe you have a program now
>> that sends weird commands that crash the Powerfile's firmware.
>
> I have done some updates. Been messing around trying to get it
> working. I'm getting
> the same problem with 2.6.38.2.  At one point I got a drive to work
> under 2.6.39, but not
> the other drive and the changer failed to show.  I got an older
> firewire mac I'll try messing
> with it later to see if there is a failure in the Powerfile.

Hi
   Well I messed around with it on the mac.  It works fine with it.  Could
this be a firewire board failure or is it more indicative of a software bug?
You mentioned updates to software.  What packages would you suggest
I look besides udev?

Thanks

Jonathan

> Thanks for the input.
>
> Jonathan
>
>
>> --
>> Stefan Richter
>> -=====-==-== -=-= ===--
>> http://arcgraph.de/sr/
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.39 and Powerfile c200

[Stefan Richter]

On May 30 Jonathan Isom wrote:
> > On Sat, May 28, 2011 at 1:26 PM, Stefan Richter
> >> Was the 2.6.39 kernel update the only change that you did on your system,
> >> or were there userland updates too?  If yes, maybe you have a program now
> >> that sends weird commands that crash the Powerfile's firmware.
[...]
> 
>    Well I messed around with it on the mac.  It works fine with it.  Could
> this be a firewire board failure or is it more indicative of a software bug?

FireWire board failures usually cause some more pronounced I/O errors than
mere SCSI request time-outs; so while it is a possible cause, it is a
rather unlikely one.

> You mentioned updates to software.  What packages would you suggest
> I look besides udev?

If there is hal(d) on your system, shut this service down and retry.

Another thought:  Which FireWire controller do you have according to
lspci -nn?
-- 
Stefan Richter
-=====-==-== -=-= ====-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.39 and Powerfile c200

[Jonathan Isom]

On Mon, May 30, 2011 at 4:24 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> On May 30 Jonathan Isom wrote:
>> > On Sat, May 28, 2011 at 1:26 PM, Stefan Richter
>> >> Was the 2.6.39 kernel update the only change that you did on your system,
>> >> or were there userland updates too?  If yes, maybe you have a program now
>> >> that sends weird commands that crash the Powerfile's firmware.
> [...]
>>
>>    Well I messed around with it on the mac.  It works fine with it.  Could
>> this be a firewire board failure or is it more indicative of a software bug?
>
> FireWire board failures usually cause some more pronounced I/O errors than
> mere SCSI request time-outs; so while it is a possible cause, it is a
> rather unlikely one.
>
>> You mentioned updates to software.  What packages would you suggest
>> I look besides udev?
>
> If there is hal(d) on your system, shut this service down and retry.
No hald.

> Another thought:  Which FireWire controller do you have according to
> lspci -nn?


02:00.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW643 PCI
Express1394b Controller (PHY/Link) [11c1:5901] (rev 06)


> --
> Stefan Richter
> -=====-==-== -=-= ====-
> http://arcgraph.de/sr/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.39 and Powerfile c200

[Stefan Richter]

On May 30 Jonathan Isom wrote:
> 02:00.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW643 PCI
> Express1394b Controller (PHY/Link) [11c1:5901] (rev 06)

Ah right; you were the one who reported that FW643 rev 06 issue against
kernel 2.6.36 which we fixed in 2.6.37.  Another dead end idea.
-- 
Stefan Richter
-=====-==-== -=-= ====-
http://arcgraph.de/sr/

Re: 2.6.39 and Powerfile c200

[Jonathan Isom]

On Mon, May 30, 2011 at 4:38 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> On May 30 Jonathan Isom wrote:
>> 02:00.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW643 PCI
>> Express1394b Controller (PHY/Link) [11c1:5901] (rev 06)
>
> Ah right; you were the one who reported that FW643 rev 06 issue against
> kernel 2.6.36 which we fixed in 2.6.37.  Another dead end idea.

Well I did some further testing.  If I boot with /bin/sh as init and
manually load the firewire
modules the C200 works.  I moved out all kernel modules but firewire
and loaded init and
it start giving the offline messages.  So it appears to be a userspace
problem.  Just  not
sure where to start. I already did some digging in udev but no luck so
far. I'm running gentoo
which probably make tracking it down just a little harder as there are
few identical installs in the
world.  Below is a listing of init scripts loaded at boot.

Any Ideas?

Jonathan


> --
> Stefan Richter
> -=====-==-== -=-= ====-
> http://arcgraph.de/sr/
>
 init scripts
  apache2                   default
  atd                       default
  avahi-daemon              default
  avahi-dnsconfd            default
  bluetooth                 default
  bootmisc                  boot
  callerid                  default
  cgroups                   boot
  consolefont               boot
    cpufrequtils              default
  cupsd                     default
  dbus                      default
  devfs                     sysinit
  device-mapper             boot
  dmesg                     sysinit
  fsck                      boot
  hdparm                    default
  hostname                  boot
  hwclock                   boot
  irexec                    default
  keymaps                   boot
  killprocs                 shutdown
  lircd                     default
  local                     default
  localmount                boot
  modules                   boot
  mount-ro                  shutdown
  mpd                       default
  mtab                      boot
  mysql                     default
  mythbackend               default
  net.eth2
  net.lo                    boot
  netmount                  default
  network
  nfs                       default
  ntp-client                default
  ntpd                      default
  procfs                    boot
  qpsmtpd                   default
  root                      boot
  samba                     default
  savecache                 shutdown
  smartd                    default
  sshd                      default
  swap                      boot
  sysctl                    boot
  syslog-ng                 default
  termencoding              boot
  udev                      sysinit
  udev-postmount            default
  urandom                   boot
  vixie-cron                default
  xdm                       default
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.39 and Powerfile c200

[Stefan Richter]

On May 31 Jonathan Isom wrote:
> Well I did some further testing.  If I boot with /bin/sh as init and
> manually load the firewire modules the C200 works.  I moved out all
> kernel modules but firewire and loaded init and it start giving the
> offline messages.  So it appears to be a userspace problem.

(Or a firmware problem actually, provoked by Linux userspace that does not
behave like a Windows system.)

> Just  not sure where to start. I already did some digging in udev but
> no luck so far. I'm running gentoo which probably make tracking it
> down just a little harder as there are few identical installs in the
> world.  Below is a listing of init scripts loaded at boot.
> 
> Any Ideas?
[...]

Nothing obvious as far as I can tell.  The mythbackend perhaps?  Or a GUI
desktop component that is started after login into xdm?

I don't know if there is a logging facility in the kernel's SCSI layer
that could expose the process name of SCSI ioctl issuers, but you can add
one:

--- a/drivers/scsi/sr.c
+++ b/drivers/scsi/sr.c
@@ -479,6 +479,9 @@ static int sr_block_open(struct block_de
 		ret = cdrom_open(&cd->cdi, bdev, mode);
 		if (ret)
 			scsi_cd_put(cd);
+		else
+			printk(KERN_INFO "***** %s opened by %s *****\n",
+			       cd->cdi.name, current->comm);
 	}
 	mutex_unlock(&sr_mutex);
 	return ret;

-- 
Stefan Richter
-=====-==-== -=-= =====
http://arcgraph.de/sr/

Re: 2.6.39 and Powerfile c200

[Jonathan Isom]

On Tue, May 31, 2011 at 2:26 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> On May 31 Jonathan Isom wrote:
>> Well I did some further testing.  If I boot with /bin/sh as init and
>> manually load the firewire modules the C200 works.  I moved out all
>> kernel modules but firewire and loaded init and it start giving the
>> offline messages.  So it appears to be a userspace problem.
>
> (Or a firmware problem actually, provoked by Linux userspace that does not
> behave like a Windows system.)
>
>> Just  not sure where to start. I already did some digging in udev but
>> no luck so far. I'm running gentoo which probably make tracking it
>> down just a little harder as there are few identical installs in the
>> world.  Below is a listing of init scripts loaded at boot.
>>
>> Any Ideas?
> [...]
>
> Nothing obvious as far as I can tell.  The mythbackend perhaps?  Or a GUI
> desktop component that is started after login into xdm?

Neither those are it. Was logging in via console and disabled mythbackend.
tried the code,  However they only tell about the dvd drives themselves and
I suspect it has more to do with the changer side of the device.  I
get 3 /dev/sg?
a /dev/sch0, a couple nodes in  /dev/bsg/, a /dev/fw1 , and the 2 dvd
drive nodes.
I'm kinda sure it is udev but am not sure where to patch to do similar
to the below
patch for the others.  In other testing, when I tried booting with
init as /bin/sh and
loaded the modules manually the device loads fine and no errors. However once
I start init and get a login it has disabled errors on parts.

> I don't know if there is a logging facility in the kernel's SCSI layer
> that could expose the process name of SCSI ioctl issuers, but you can add
> one:
>
> --- a/drivers/scsi/sr.c
> +++ b/drivers/scsi/sr.c
> @@ -479,6 +479,9 @@ static int sr_block_open(struct block_de
>                ret = cdrom_open(&cd->cdi, bdev, mode);
>                if (ret)
>                        scsi_cd_put(cd);
> +               else
> +                       printk(KERN_INFO "***** %s opened by %s *****\n",
> +                              cd->cdi.name, current->comm);
>        }
>        mutex_unlock(&sr_mutex);
>        return ret;
>
> --
> Stefan Richter
> -=====-==-== -=-= =====
> http://arcgraph.de/sr/
>

dmesg log after C200 poweron

[48028.951220] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[48029.549845] firewire_core: created device fw1: GUID 003060f200002759, S400
[48029.609450] scsi8 : SBP-2 IEEE-1394
[48029.810579] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
[48029.812794] scsi 8:0:0:0: CD-ROM            TOSHIBA  DVD-ROM
SD-M1212 1032 PQ: 0 ANSI: 0 CCS
[48029.817707] sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
[48029.817962] sr 8:0:0:0: Attached scsi CD-ROM sr1
[48029.818159] sr 8:0:0:0: Attached scsi generic sg5 type 5
[48029.820363] firewire_sbp2: fw1.0: logged in to LUN 0001 (0 retries)
[48029.822509] scsi 8:0:0:1: CD-ROM            TOSHIBA  DVD-ROM
SD-M1212 1032 PQ: 0 ANSI: 0 CCS
[48029.827662] sr2: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
[48029.827907] sr 8:0:0:1: Attached scsi CD-ROM sr2
[48029.828073] sr 8:0:0:1: Attached scsi generic sg6 type 5
[48029.830277] firewire_sbp2: fw1.0: logged in to LUN 0002 (0 retries)
[48029.835850] scsi 8:0:0:2: Medium Changer    Escient  Powerfile C200
  04A  PQ: 0 ANSI: 3
[48060.704057] firewire_sbp2: fw1.0: sbp2_scsi_abort
[48070.704061] firewire_sbp2: fw1.0: sbp2_scsi_abort
[48070.704292] sr 8:0:0:1: Device offlined - not ready after error recovery
[48070.704387] sr 8:0:0:1: rejecting I/O to offline device
[48071.031118] ch0: type #1 (mt): 0x0+1 [medium transport]
[48071.031126] ch0: type #2 (st): 0x4+200 [storage]
[48071.031132] ch0: type #3 (ie): 0x1+1 [import/export]
[48071.031136] ch0: type #4 (dt): 0x2+2 [data transfer]
[48071.364376] ch0: dt 0x2: READ ELEMENT STATUS failed
[48101.728068] firewire_sbp2: fw1.0: sbp2_scsi_abort
[48111.728057] firewire_sbp2: fw1.0: sbp2_scsi_abort
[48111.728268] sr 8:0:0:0: Device offlined - not ready after error recovery
[48111.728394] sr 8:0:0:0: rejecting I/O to offline device
[48111.730902] ***** sr0 opened by udisks-daemon *****
[48111.730980] sr 8:0:0:1: rejecting I/O to offline device
[48111.731035] sr 8:0:0:1: rejecting I/O to offline device
[48111.731157] sr 8:0:0:1: rejecting I/O to offline device
[48111.731167] sr 8:0:0:1: rejecting I/O to offline device
[48111.731625] sr 8:0:0:0: rejecting I/O to offline device
[48111.731652] sr 8:0:0:0: rejecting I/O to offline device
[48111.732300] sr 8:0:0:0: rejecting I/O to offline device
[48111.732326] sr 8:0:0:0: rejecting I/O to offline device
[48111.734325] ***** sr0 opened by udisks-daemon *****
[48111.757569] sr 8:0:0:1: rejecting I/O to offline device
[48111.757590] sr 8:0:0:1: rejecting I/O to offline device
[48111.757729] sr 8:0:0:0: rejecting I/O to offline device
[48111.757753] sr 8:0:0:0: rejecting I/O to offline device
[48111.762602] sr 8:0:0:1: rejecting I/O to offline device
[48111.762626] sr 8:0:0:1: rejecting I/O to offline device
[48111.762684] sr 8:0:0:1: rejecting I/O to offline device
[48111.762694] sr 8:0:0:1: rejecting I/O to offline device
[48111.765711] sr 8:0:0:0: rejecting I/O to offline device
[48111.765736] sr 8:0:0:0: rejecting I/O to offline device
[48111.765796] sr 8:0:0:0: rejecting I/O to offline device
[48111.765806] sr 8:0:0:0: rejecting I/O to offline device
[48112.062578] ch0: dt 0x3: READ ELEMENT STATUS failed
[48112.062586] ch0: INITIALIZE ELEMENT STATUS, may take some time ...
[48112.105512] ch0: ... finished
[48112.105522] ch 8:0:0:2: Attached scsi changer ch0
[48112.105690] ch 8:0:0:2: Attached scsi generic sg7 type 8
[48114.003984] ***** sr0 opened by udisks-daemon *****
[48114.004952] sr 8:0:0:0: rejecting I/O to offline device
[48114.004970] sr 8:0:0:0: rejecting I/O to offline device
[48114.005145] sr 8:0:0:1: rejecting I/O to offline device
[48114.005168] sr 8:0:0:1: rejecting I/O to offline device
[48116.003804] ***** sr0 opened by udisks-daemon *****
[48116.004466] sr 8:0:0:0: rejecting I/O to offline device
[48116.004483] sr 8:0:0:0: rejecting I/O to offline device
[48116.004616] sr 8:0:0:1: rejecting I/O to offline device
[48116.004638] sr 8:0:0:1: rejecting I/O to offline device
[48118.004164] ***** sr0 opened by udisks-daemon *****
[48118.004855] sr 8:0:0:0: rejecting I/O to offline device
[48118.004880] sr 8:0:0:0: rejecting I/O to offline device
[48118.005057] sr 8:0:0:1: rejecting I/O to offline device
[48118.005079] sr 8:0:0:1: rejecting I/O to offline device

Last 5 lines repeated until C200 shutdown.


Thanks

Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html