https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com, | |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |jbottomley@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c2 James Bottomley changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low --- Comment #2 from James Bottomley 2011-03-14 19:50:50 UTC --- Downgrade to P4 because it's a single setup, not a generic driver problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c4 --- Comment #4 from James Bottomley 2011-03-15 13:39:23 UTC --- (In reply to comment #3)

For a log I have to have access to the system (: ... maybe I should try to add an error shell to initrd to be able to make a coppy of the boot messages.

OK, that's what I need to take this forwards.

IMHO the problems seems to be coldplug/udevd used in initrd of the 11.4. The rescue option of the DVD of the 11.3 does not show the problem whereas the kernel of the 11.3 installed in `rescue mode' shows also the same misbehaviour after udev is started.

Yesterday evening I've tried some patches from

https://bugzilla.kernel.org/show_bug.cgi?id=5921

but it seems that only the bus reset works a bit faster and I've seen that now the driver indeed wait 15 seconds after its own scan of the plugged hardware. The question is how I can prevent coldplug/udev from scanning all 16 slots of the SCSI bus of the AHA-2940U2W. It makes no sence to scan upto scsi0:A:0:0 as there is nothing, also the zip drive on scsi0:5:0:0 does not understand all SCSI commands. Cleary all is well terminated, that is every plugged hardware and also activ termination in the BIOS of the AHA-2940U2W.

It's not really that appropriate to use a bug to ask general SCSI questions. However, SPI isn't a hotplug bus, it has to be scanned and the driver has no way of knowing where devices will be on the bus. If you have a device on the BUS that's not SCSI compliant, then either take it off or work out what the problem is and see if it can be properly blacklisted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c6 --- Comment #6 from Dr. Werner Fink 2011-03-17 08:50:03 UTC --- Created an attachment (id=419889) --> (http://bugzilla.novell.com/attachment.cgi?id=419889) kernel command line -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c8 --- Comment #8 from Dr. Werner Fink 2011-03-17 08:51:44 UTC --- Created an attachment (id=419891) --> (http://bugzilla.novell.com/attachment.cgi?id=419891) /proc/scsi/scsi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c10 --- Comment #10 from Dr. Werner Fink 2011-03-17 09:11:30 UTC --- Just to be noted, the Traxdata is AFAICS from its BIOS seems to be a TEAC CD-R55S, but in comparision with linux/drivers/scsi/scsi_devinfo.c the first one is not black listed, also the most old ZIP drives are missed. I suggest to add {"Traxdata", "CDR4120", NULL, BLIST_NOLUN}, /* locks up */ {"IOMEGA", "ZIP", NULL, BLIST_NOLUN}, /* locks up */ in linux/drivers/scsi/scsi_devinfo.c. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c12 --- Comment #12 from Dr. Werner Fink 2011-03-17 13:21:17 UTC --- (In reply to comment #11)

{"iomega", "jaz 1GB", "J.86", BLIST_NOTQ | BLIST_NOLUN},

IMHO jaz or even JAZ is not identical to ZIP. It seems to make a difference at least in scsi_get_device_flags() of drivers/scsi/scsi_devinfo.c And indeed I'm using BLIST_NOTQ aka 0x20 for the ZIP on the kernels command line in attachment #419889 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c14 --- Comment #14 from Dr. Werner Fink 2011-03-18 09:30:24 UTC --- Created an attachment (id=420152) --> (http://bugzilla.novell.com/attachment.cgi?id=420152) Patch for scsi_devinfo.c Now with Traxdata and Iomega ZIP -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c16 --- Comment #16 from Dr. Werner Fink 2011-03-18 18:26:32 UTC --- Just found in the log in attachment #420156: [ 221.840736] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 221.841006] sd 0:0:1:0: Attached scsi generic sg1 type 0 [ 221.841248] scsi 0:0:3:0: Attached scsi generic sg2 type 5 ^^^^^^ [ 221.841482] scsi 0:0:4:0: Attached scsi generic sg3 type 5 ^^^^^^ [ 221.841730] sd 0:0:5:0: Attached scsi generic sg4 type 0 [ 221.841969] scsi 0:0:6:0: Attached scsi generic sg5 type 1 [ 221.842226] sd 1:0:0:0: Attached scsi generic sg6 type 0 [ 221.842467] scsi 1:0:1:0: Attached scsi generic sg7 type 5 that is the CDROM and the CDwriter are from type 5 and now I've found in /lib/udev/rules.d/60-persistent-storage.rules [...] # ATA devices using the "scsi" subsystem KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", \ ATTRS{vendor}=="ATA", IMPORT{program}="ata_id --export $tempnode" # ATA/ATAPI devices using the "scsi" subsystem KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", \ ATTRS{type}=="5", IMPORT{program}="ata_id --export $tempnode" ^^^^^^^^^^^^^^^^ # scsi devices KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id \ --export --whitelisted -d $tempnode", ENV{ID_BUS}="scsi" KERNEL=="cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", \ IMPORT{program}="scsi_id --export --whitelisted -d $tempnode", \ ENV{ID_BUS}="cciss" KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", \ SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}" KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", \ SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n" [...] that with this rule ata_id is applied to real SCSI devices. IMHO are rule like KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", \ ATTRS{vendor}!="ATA", IMPORT{program}="scsi_id --export --whitelisted -d \ $tempnode" could be used. And indeed I've seen a log entry (not in the dmesg output found in the attachment) where ata_id scolded that HDIO_GET_IDENTITY has failed on some devices belonging to the aic7xxx. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c18 --- Comment #18 from Dr. Werner Fink 2011-03-18 19:07:06 UTC --- Created an attachment (id=420283) --> (http://bugzilla.novell.com/attachment.cgi?id=420283) aic7xxx-errorrecover.diff And this is patch #2 also found at https://bugzilla.kernel.org/show_bug.cgi?id=5921 to better error handling -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c20 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |jbottomley@novell.com Component|Kernel |Basesystem Resolution|UPSTREAM | AssignedTo|jbottomley@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #20 from Dr. Werner Fink 2011-03-21 08:56:04 UTC --- First: I've the syste mup and running. (In reply to comment #19): The error handling of the aic7xxx should fixed upstream yes. Nevertheless, I've the system up and running as I've fixed the bug in udev as reported by me in comment #16. It is not a good idea to root the ATA HDIO_GET_IDENTITY to as SCSI 2 device, like CDROMs or CD-writes. And this is done in /lib/udev/rules.d/60-persistent-storage.rules at line 31ff: # ATA/ATAPI devices using the "scsi" subsystem KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", IMPORT{program}="ata_id --export $tempnode" I've changed this on my local system to: # ATA/ATAPI devices using the "scsi" subsystem KERNEL=="sd*[!0-9]", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", IMPORT{program}="ata_id --export $tempnode" KERNEL=="sr2", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", IMPORT{program}="ata_id --export $tempnode" KERNEL=="sr[01]", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", IMPORT{program}="scsi_id --export --whitelisted -d $tempnode" and now the systems boot in a perfect way. The major problem from the side of udev is that it is not possible to distinguish a SCSI 2 CDROM from a ATAPI CDROM: both are of type 5 and *both* show a vendor not equal to ATA! The only difference is the scsi_level found in the sysfs entry. Maybe there is an other trick to avoid this. IMHO these are two bugs: first of all udev or better its rules should not fire an ATA HDIO_GET_IDENTITY to an device with SCSI level < 6. Next bug is a new one: the SCSI or ATAPI layer of the kernel should not route such inquires to devices not supporting such queries. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c21 --- Comment #21 from Dr. Werner Fink 2011-03-21 09:01:06 UTC --- Created an attachment (id=420409) --> (http://bugzilla.novell.com/attachment.cgi?id=420409) 60-persistent-storage.rules.patch Suggest following patch for 60-persistent-storage.rules to avoid executing ata_id on older SCSI devices. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c22 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |werner@novell.com --- Comment #22 from Kay Sievers 2011-03-21 13:43:14 UTC --- Care to test if just adding: # ATA/ATAPI devices SPC-3 or later using the "scsi" subsystem ... ATTRS{scsi_level}=="[6-9]*", ... The second line calling scsi_id should not be there, I think, because the next one will also match? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c24 --- Comment #24 from Dr. Werner Fink 2011-03-23 08:10:52 UTC --- The code ATTRS{scsi_level}=="[6-9]*" does work flawless. I can boot the system *without* trigger a reset on the SCSI bus. Btw: Does udev something like modifiers for the content of the attribute `scsi_level', let's say: ATTRS{scsi_level:d} to be able to use ATTRS{scsi_level:d}>=6 For file names including the colon this may require to escape the colon. On the other hand instead of a colon also the percent sign `%' could be used to set a modifier for the key of an attribute. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c25 --- Comment #25 from Kay Sievers 2011-03-23 11:16:19 UTC --- (In reply to comment #24)

The code

ATTRS{scsi_level}=="[6-9]*"

does work flawless. I can boot the system *without* trigger a reset on the SCSI bus.

Great. I will add that. Thanks!

Btw: Does udev something like modifiers for the content of the attribute `scsi_level', let's say:

ATTRS{scsi_level:d}

to be able to use

ATTRS{scsi_level:d}>=6

For file names including the colon this may require to escape the colon. On the other hand instead of a colon also the percent sign `%' could be used to set a modifier for the key of an attribute.

It's all just simple string and fnmatch(). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c27 --- Comment #27 from Kay Sievers 2011-04-26 20:04:35 UTC --- Package submitted to openSUSE:11.4:Update:Test/udev: https://build.opensuse.org/request/show/68450 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c29 --- Comment #29 from Matthias Andree 2011-05-26 19:36:34 UTC --- (In reply to comment #28)

i guess you want this released as opensuse update?

That depends if you want to scare the remaining openSUSE users with older SCSI CD-ROMs away or not. Of course you want to have that fix backported to affected and supported distros (AFAIR 11.3 and 11.4). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c30 --- Comment #30 from Marcus Meissner 2011-05-27 09:18:20 UTC --- lets do then +1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c32 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:41232:moderat | |e --- Comment #32 from Swamp Workflow Management 2011-05-31 14:45:44 UTC --- The SWAMPID for this issue is 41232. This issue was rated as moderate. Please submit fixed packages until 2011-06-14. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/41232 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679277 https://bugzilla.novell.com/show_bug.cgi?id=679277#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41232:moderat |. |e maint:released:11.4:41283 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.