RE: inconsistent renaming of devices

["Surekha.PC" <surekhap@cisco.com>]

Hi all,

 The problem is no longer seen on. It seems like a setup problem, the
installed udev binary size was not matching with that of udev-016. This
could have happened when I installed udev-016 without uninstalling the
old package. The udev binary was not installed properly, so 'udevsend'
and 'udevd' were not started. This was causing problem in device
creation. I cleanly uninstalled the old package and installed udev-016,
now device addition/removal is happening fine.

Thanks much for your inputs.

regds,
surekha

-----Original Message-----
From: Greg KH [mailto:greg@kroah.com] 
Sent: Friday, February 06, 2004 5:22 AM
To: Surekha.PC
Cc: 'Martin Lorenz'; linux-hotplug-devel@lists.sourceforge.net
Subject: Re: inconsistent renaming of devices


On Thu, Feb 05, 2004 at 03:29:41PM +0530, Surekha.PC wrote:
> 
> 
> >What do you see happening in your system?
> >If you build with DEBUG=true USE_LOG=true what does the debug syslog
> show for these
> >devices?
> 
> It seems the user<->kernel race still persists.
> 
> During device addition randomly few device/partition entries are not 
> getting created. If debug is enabled all devices are created. With 
> debug turned off, only few of them are created. So in this case I am 
> not able to capture debug for devices not getting created.
> 
> Again device removal is also having the similar inconsistent 
> behaviour. Irrespective of debug being on/off few stale device entries

> are retained under /udev.
> 
> In this scenario I could see some debug messages as below.
> 
> Looks like the sysfs entries for the device are removed long before 
> udev lookup.

What kind of block device is this?  

> ----------------------------------------------------------------------
> --
> -----------------
> udev_hotplug: looking at '/block/sdc'
> udev_hotplug: looking at '/block/sde/sde2
> udev_hotplug: looking at '/block/sde/sde3
> get_dirs: sysfs_path='/sys'
> udev_hotplug: don't care about 'scsi_device' devices
> .....
> namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
> .....
> udev_hotplug: looking at '/block/sdc/sdc3
> udev_hotplug: don't care about 'scsi_device' devices
> udev_remove_device: name is 'iscsib0t38l0sd3'
> ......
> udev_remove_device: '/class/scsi_device/40:0:38:1' not found in
> database, falling back on default name
>
------------------------------------------------------------------------
> ------------------
> 
> In the above debug messages, I could observe the first few hotplug 
> events for device removal are not getting passed to 
> udev_remove_device(). This results in those device entries not getting

> removed.

How are we dropping events?  Are you using the udevsend/udevd/udev
situation, or just udev?  I don't see how we could drop events just
using udev alone.

> Let me know if you need more information from the debug log, I will 
> send it to you.

Please do.  Along with annotation of what is going on.

thanks,

greg k-h



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel