From: Oliver Neukum <oneukum@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb_id segfaulting on 2.6.23
Date: Tue, 06 Nov 2007 07:42:29 +0000 [thread overview]
Message-ID: <200711060842.29509.oneukum@suse.de> (raw)
In-Reply-To: <47135D33.7080805@gentoo.org>
Am Dienstag 06 November 2007 schrieb Kay Sievers:
> On Tue, 2007-11-06 at 00:42 +0000, Daniel Drake wrote:
> > Kay Sievers wrote:
> > > Strange, seems some attributes are not catched by udev. What does
> > > "udevinfo" print for the working setup? Do you see the missing
> > > attributes there?
> >
> > You're referring to idVendor, idProduct, etc. Actually, those attributes
> > don't even exist in sysfs(!!) which must be the root of the problem.
> >
> > So, I bisected the kernel. Ready for a strange result?
> > First bad commit is 296699de: Introduce CONFIG_SUSPEND for
> > suspend-to-Ram and standby
> >
> > On this system, I always disable suspend/hibernate/etc support, and
> > continued to do so throughout the bisection. This lead me to the above
> > result.
> >
> > On a kernel tree with HEAD as 296699de, I see the bug (no idVendor, etc)
> > when CONFIG_SUSPEND=n (my normal setup). However, if I set
> > CONFIG_SUSPEND=y, the missing USB sysfs attributes show up!
> >
> > On 2.6.24-rc1-git14, the same is true. CONFIG_SUSPEND=n, no idVendor
> > nodes, udev usb_id crashes on boot. CONFIG_SUSPEND=y, idVendor and
> > friends are back, udev behaves as normal.
>
> I fixes usb_id in the meantime not to crash, but that's a different
> story.
>
> > I know you have experience working with sysfs/kobject internals, do you
> > have any suggestions or thoughts before I take this to LKML?
>
> Oh, great, it was a complete mystery what was going wrong, maybe this is
> pointing in the right direction. We got more than one report for this
> bug.
>
> Maybe Oliver or Alan have an idea, what could go wrong with the USB
> attributes depending on CONFIG_SUSPEND, I don't expect a driver core
> issue here.
Is bcdDevice present without CONFIG_SUSPEND? Which attributes are
present?
Regards
Oliver
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
next prev parent reply other threads:[~2007-11-06 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:29 usb_id segfaulting on 2.6.23 Daniel Drake
2007-10-15 12:41 ` Kay Sievers
2007-10-15 12:58 ` Kay Sievers
2007-10-15 13:07 ` Daniel Drake
2007-10-15 21:19 ` Kay Sievers
2007-10-16 18:15 ` Kay Sievers
2007-11-06 0:42 ` Daniel Drake
2007-11-06 2:26 ` Kay Sievers
2007-11-06 7:42 ` Oliver Neukum [this message]
2007-11-06 11:47 ` Daniel Drake
2007-11-06 12:38 ` Oliver Neukum
2007-11-06 14:11 ` Oliver Neukum
2007-11-06 15:03 ` Daniel Drake
2007-11-06 16:11 ` Alan Stern
2007-11-06 16:05 ` Alan Stern
2007-11-06 17:51 ` Daniel Drake
2007-11-06 17:54 ` Daniel Drake
2007-11-06 22:18 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711060842.29509.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).