On Tue, Mar 08, 2005 at 01:43:58AM +0100, Kay Sievers wrote:
> On Tue, 2005-03-08 at 00:03 +0100, Marco d'Itri wrote:
> > This rule causes udevstart 054 to segfault:
> >
> > BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"
> >
> > ----- Forwarded message from Thomas Breitner <[EMAIL PROTECTED]> -----
> >
> > Subject: Bug#298192: udev: segfault with new rule on startup
> > Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> > From: Thomas Breitner <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> >
> > Thanks, here it is:
> >
> > mala:~/sourcen/udev-0.054# /etc/init.d/udev restart
> > Recreating device nodes.../etc/init.d/udev: line 216: 10361 Segmentation
> > fault udevstart
> > mala:~/sourcen/udev-0.054# gdb /sbin/udevstart
> > GNU gdb 6.3-debian
>
> > Program received signal SIGSEGV, Segmentation fault.
> > strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of
> > bounds>) at namedev.c:50
> > 50 if (s[0] == '\0') {
> > (gdb) where
> > #0 strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of
> > bounds>) at namedev.c:50
>
> Yeah, that's a bad bug in the rule matching. The sysfs_device is NULL,
> and we try to find the name here. I will fix it.
>
> But I don't know why the sysfs_device is NULL in this case, I can't
> reproduce it with the same hardware. Thomas, it would be nice if you can
> send the output of:
> udevinfo -a -p /sys/class/net/eth<N>
I have heard of this error before, from other users. I think it depends
on the version of the driver you are using.
thanks,
greg k-h
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
