From: Greg KH <greg@kroah.com>
To: "Marco d'Itri" <md@Linux.IT>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: 2.6.14, udev: unknown symbols for ehci_hcd
Date: Mon, 7 Nov 2005 09:31:57 -0800 [thread overview]
Message-ID: <20051107173157.GA16465@kroah.com> (raw)
In-Reply-To: <20051107113329.GA7632@wonderland.linux.it>
On Mon, Nov 07, 2005 at 12:33:29PM +0100, Marco d'Itri wrote:
> On Nov 06, Greg KH <greg@kroah.com> wrote:
>
> > This seems to be a Debian issue for some odd reason, I suggest filing a
> > bug against the udev package (or just tagging onto the existing bug for
> > this problem, I've seen it in there already...)
> The reason this is usually seen only on Debian systems is that I am the
> first one who shipped an udev package which runs many parallel modprobe
> commands, but this is a genuine kernel/modprobe bug.
I'm pretty sure OpenSuSE 10.0 does the same thing, and I don't think
anyone has reported the same kind of bugs there. Makes me wonder what
is really happening here...
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-07 17:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 15:37 2.6.14, udev: unknown symbols for ehci_hcd Harald Dunkel
2005-11-05 16:25 ` Greg KH
2005-11-06 5:59 ` Harald Dunkel
2005-11-06 17:03 ` Gustavo Guillermo Pérez
2005-11-11 0:20 ` Rob Landley
2005-11-06 21:51 ` Greg KH
2005-11-07 11:33 ` Marco d'Itri
2005-11-07 17:31 ` Greg KH [this message]
2005-11-07 19:07 ` Pozsar Balazs
2005-11-07 19:12 ` Greg KH
2005-11-07 19:20 ` Pozsar Balazs
2005-11-07 19:27 ` Greg KH
[not found] ` <1131405438.21610.17.camel@localhost.localdomain>
2005-11-07 23:19 ` Marco d'Itri
2005-11-05 17:31 ` Kay Sievers
2005-11-05 18:48 ` Pozsar Balazs
2005-11-06 3:51 ` Rusty Russell
2005-11-06 6:22 ` Bug#333052: " Harald Dunkel
2005-11-06 14:50 ` Harald Dunkel
2005-11-06 15:29 ` Pozsar Balazs
2005-11-06 17:05 ` Harald Dunkel
2005-11-06 17:21 ` Marco d'Itri
2005-11-07 6:00 ` Harald Dunkel
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=20051107173157.GA16465@kroah.com \
--to=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@Linux.IT \
/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