Comment 68 for bug 24238

Message-ID: <email address hidden>
Date: Sun, 06 Nov 2005 18:05:44 +0100
From: Harald Dunkel <email address hidden>
To: Pozsar Balazs <email address hidden>
CC: <email address hidden>, Kay Sievers <email address hidden>,
 Rusty Russell <email address hidden>, <email address hidden>
Subject: Re: Bug#333052: 2.6.14, udev: unknown symbols for ehci_hcd

--------------enigAFEA4EF0EA532F22C33CAFDC
Content-Type: multipart/mixed;
 boundary="------------050900040809070701040700"

This is a multi-part message in MIME format.
--------------050900040809070701040700
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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

--------------050900040809070701040700
Content-Type: application/x-tar;
 name="modprobe.patch.gz"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="modprobe.patch.gz"

H4sICLEubkMAA21vZHByb2JlLnBhdGNoAJVUbW/TMBD+nP6KWyRY0sZt025sdBSGeJ1U9gk+
ICFFIXE6a6ld2Q5jvPx37uykrHtjWGlSn893z3NvjDFYqbKpORNSWGaVqg2bDidsrfneUGmx
HOH5WquvfFgEk/F4n9FzCOOns+nhbH8yHHcLBmM87w0Gg3tM3rCWjtlkD9LpLEWDT29YOz4G
Nn0yTZ7AgD4HcHzcg+DtyeIN9NFOkXlX5gilxVmuoV8LyXHXGxibaztD+agPH8TyzIJUFr5y
RNdIy0u45HYI8FrJXQtVLuoh9EeoftUszKFSay6jcETiUSsOEwh1GJNTUUG0c/VK7DEfTJN0
gqAP9pJp6lCjstPm0upLePwYjNXFau33CcVM5isew3wO4xh+kjpBP6lAWODfhbEmgcbwguCD
MGDPOP6ELsGZcPBZ4J10emSIZIH3OienVp1Hp58WCyQBXyTRcBobbH4LuBBkdM/FGHbmQIK4
N2gN7Nyr7/WCpbIKVGOPeoOHXgSMxIY78rxuhxjWhnv5VgBcHIOgv7k9h9wq4d3F/wkhZOFt
3v/HBJalbcw9HDBjGxY72zUSLlReCrkMY/j1C64ffpJ1dxx3RoLG1Jyvo9Q1VXzUSivNeUSd
8ldS1MrwaKuSuzOH0bVTK/l9HTt4IYlxP3P7qz7gTg90orlttIT0yLXOYbqXTLD/3de1ji9G
XEhYrLNvXK/ypSiSdo/GUGSEkgkUq5JcZmptyTqCwklAbbRQxTk2f6U0hwsOtVLnCQgJRY4R
F3bXAE0rkdfiB0Zw6PNTlZjJGm9mlah5hI7Yc/rnGpViQTlCpWe+Y5E911rpKHylmrp084am
B+w+MrszeGSwChLS8my2zDky/ja+pYp99LsQO0LIVi5JTKEmUn52lQpenn7++P7k9B0goLzW
PC8vidw515L7uebLSSwlBiCjHPS6Dve5yITMvHok+QUhghczD7GdTIlvdZpPKbH1FVoJbWxm
BQakF2z4f3A2kfEtaFwQgi4IdzjzQ+k29gzZM3z/IzfsWm7Yg3LDHpybO9BdTVkjCV5bhEGh
VqtcEuhKyDJrt9F2hFsplW63/gDRsBheowcAAA==
--------------050900040809070701040700--

--------------enigAFEA4EF0EA532F22C33CAFDC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDbjfuUTlbRTxpHjcRAqBVAJ9E5DM8q/nh2ALJvTZtQefGYk7W+QCeMAYG
GVBCeBsqx+dfONtdV3HatRA=
=I9cB
-----END PGP SIGNATURE-----

--------------enigAFEA4EF0EA532F22C33CAFDC--