From: Kay Sievers <kay.sievers@vrfy.org>
To: Brandon Philips <brandon@ifup.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: Fixing gave up waiting for init of module libcrc32c.
Date: Tue, 30 Mar 2010 19:47:23 +0200 [thread overview]
Message-ID: <ac3eb2511003301047v60bf37fdh141ffc6960c67903@mail.gmail.com> (raw)
In-Reply-To: <20100330165009.GP21087@jenkins.home.ifup.org>
On Tue, Mar 30, 2010 at 18:50, Brandon Philips <brandon@ifup.org> wrote:
> Side note: Intially I thought that modprobe was forking for each
> module dependency but that was incorrect after looking at the
> code. udev is forking off two modprobes almost at the same time for
> each bnx2x device alias when udevadm trigger is called during the boot
> sequence.
Right, that's the standard behavior, and applies to all usual systems.
> FWIW, I don't think this is a SUSE thing as our udev is pretty lightly
> patched.
Yes, there is no SUSE patch at all. All usual systems ship the same stuff here.
Kay
prev parent reply other threads:[~2010-03-30 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 23:40 Fixing gave up waiting for init of module libcrc32c Brandon Philips
2010-03-20 1:01 ` Herbert Xu
2010-03-20 1:08 ` Herbert Xu
2010-03-20 2:46 ` David Miller
2010-03-20 3:45 ` Herbert Xu
2010-03-20 4:21 ` Brandon Philips
2010-03-20 4:24 ` Herbert Xu
2010-03-20 5:23 ` David Miller
2010-03-20 12:29 ` Herbert Xu
2010-03-20 13:16 ` Neil Horman
2010-03-29 23:06 ` Rusty Russell
2010-03-31 19:03 ` Brandon Philips
2010-03-31 23:25 ` Rusty Russell
2010-03-30 16:50 ` Brandon Philips
2010-03-30 17:47 ` Kay Sievers [this message]
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=ac3eb2511003301047v60bf37fdh141ffc6960c67903@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=brandon@ifup.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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