From: Harald Dunkel <harald.dunkel@t-online.de>
To: Pozsar Balazs <pozsy@uhulinux.hu>
Cc: 333052@bugs.debian.org, Kay Sievers <kay.sievers@vrfy.org>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Bug#333052: 2.6.14, udev: unknown symbols for ehci_hcd
Date: Sun, 06 Nov 2005 18:05:44 +0100 [thread overview]
Message-ID: <436E37E8.3070807@t-online.de> (raw)
In-Reply-To: <20051106152924.GB16987@ojjektum.uhulinux.hu>
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
Pozsar Balazs wrote:
>
> Well, that's really wierd, It Should Work(tm) :)
> Did you apply both patches (Rusty's + mine), or only the latter?
>
I hadn't seen Rusty's patch on Debian's bts, until you mentioned
it. I have applied both patches now, and rebooted twice: By now
it worked. But that's what I thought before.
> Could you send me debug output please? The first time I met the problem,
> I used a modprobe wrapper which dumped /proc/modules and modprobe
> stdout/stderr to a temp file.
>
If the problem comes back then I will do.
> I would like to also mention, that my patch leaves a very little time
> window open, but that's only a problem if module unloading is also
> happening: after parsing /proc/modules, but before actually loading the
> module, it is possible that an rmmod unloads (starts to unload) a
> dependant module. But this does not affect booting.
>
>
Are there several modprobe's running in parallel? Or does modprobe
return SUCCESS while the kernel is still busy "making the module
usable somehow"?
Regards
Harri
[-- Attachment #1.2: modprobe.patch.gz --]
[-- Type: application/x-tar, Size: 838 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-11-06 17:06 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
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 [this message]
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=436E37E8.3070807@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=333052@bugs.debian.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@uhulinux.hu \
--cc=rusty@rustcorp.com.au \
/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