On Wed, 2008-06-11 at 21:29 +0200, Stefan Richter wrote: > James Bottomley wrote: > > On Wed, 2008-06-11 at 12:15 -0700, Greg KH wrote: > >> On Wed, Jun 11, 2008 at 06:58:05PM +0000, Chris Clayton wrote: > >>> Jun 11 17:48:13 upstairs udevd-event[1457]: wait_for_sysfs: wait for '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:0a.2/usb11/11-2/11-2:1.0/host4/ioerr_cnt' for 20 mseconds > >>> Jun 11 17:48:18 upstairs last message repeated 236 times > >> This doesn't look good. It looks like a udev rule in your system is > >> looking for a file that will never show up. That's a short way to a > >> long delay time :) > >> > >> Try commenting out the rule that does this and see if things are fixed. > > > > Actually, there's something seriously wrong here: ioerr_cnt is a > > property of the device, not of the host (as in it will never appear > > under .../host4 but under .../host4/targetX:X:X/4:X:X:X/ioerr_cnt). > > Perhaps an investigation of why udevd-event is looking under host4/ is > > in order. > > So the change which commit b0ed43360fdca227048d88a08290365cb681c1a8 > "[SCSI] add scsi_host and scsi_target to scsi_bus" introduced is leading > the udev scripts onto a wrong trail? Yes, I think so ... what it does is make us get bus events for the target as well as the lun, whereas without it we only get them for the lun. I think something is misparsing the new target event and this is where the trouble is coming from. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
