Re: [2.6.37-rc1] udevd-event prints errors.

[Tetsuo Handa]

Greg KH wrote:
> On Sat, Nov 06, 2010 at 03:07:55AM +0900, Tetsuo Handa wrote:
> > Hello.
> > 
> > I noticed that udevd-event started to print error messages.
> > 
> >   Starting udev: udevd-event[1682]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:10.0/host0/ioerr_cnt' failed
> >   udevd-event[2103]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:10.0/host0/target0:0:1/ioerr_cnt' failed
> >   udevd-event[2102]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:10.0/host0/target0:0:0/ioerr_cnt' failed
> 
> That's wierd, what version of udev is this?
> 

# rpm -qf /sbin/udevd
udev-095-14.21.el5_5.1
# /usr/bin/udevinfo -V
udevinfo, version 095

> > These error messages are caused by one or more of below commits.
> > (Sorry, I can't find exact one because I can't boot as of below commits.)
> > 
> > 5cfc64ce "base/platform: Safe handling for NULL platform data and resources"
> > 807508c8 "base/platform: Simplifications for NULL platform data/resources handling"
> > 39aba963 "driver core: remove CONFIG_SYSFS_DEPRECATED_V2 but keep it for block devices"
> > 
> > Is this a regression? (Is this an intended change?)
> 
> Do you still have CONFIG_SYSFS_DEPRECATED enabled?
> 
Oh, around above commits, CONFIG_SYSFS_DEPRECATED has changed to "n"
by some reason. I changed to

  # grep CONFIG_SYSFS .config
  CONFIG_SYSFS_DEPRECATED=y
  CONFIG_SYSFS_DEPRECATED_V2=y
  CONFIG_SYSFS=y

and re-bisected. Now it turned out that

  39aba963 "driver core: remove CONFIG_SYSFS_DEPRECATED_V2 but keep it for block devices"

is the commit which caused these error messages.

Guessing from error messages, changes in drivers/scsi/hosts.c and
drivers/scsi/scsi_scan.c might be involved.

> Other than that, everything works ok, right?
Right.

Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/