From: Greg KH <greg@kroah.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-hotplug@vger.kernel.org
Subject: Re: udevd induced deadlock in loading kernel modules?
Date: Sat, 2 Feb 2008 10:55:07 -0800 [thread overview]
Message-ID: <20080202185507.GC13005@kroah.com> (raw)
In-Reply-To: <47A4522C.8090403@vc.cvut.cz>
On Sat, Feb 02, 2008 at 03:21:16AM -0800, Petr Vandrovec wrote:
> Mailer on sf.net says that email address in udev's README is obsolete.
> Oops...
> Petr
>
> -------- Original Message --------
> Subject: udevd induced deadlock in loading kernel modules?
> Date: Sat, 2 Feb 2008 12:07:19 +0100
> From: Petr Vandrovec <petr@vandrovec.name>
> To: linux-kernel@vger.kernel.org
> CC: linux-hotplug-devel@lists.sourceforge.net
>
> Hello,
> today my system hung during boot, while loading ftdi_sio & loop - I have
> two ftdi serial ports,
> and apparently this tricked udevd to start two concurrent modprobes for
> them - so I ended up with
> strance "ftdi_sio: gave up waiting for init of module usbserial." for each
> symbol it tried to
> import, until I kill-9 process 3137 (see below). After that loop got
> loaded, and second ftdi's
> load finished as well.
>
> Unfortunately I do not have stacktraces of hung modprobe processes. Maybe
> next time, but it
> does not look very reproducible.
>
> Kernel is current git (2.6.24, ed50d6cbc394cd0966469d3e249353c9dd1d38b9),
> udev is Debian's 0.114-2,
> and module-init-tools are Debian's 3.3-pre11-4. Kernel is 64bit amd64 with
> almost all debugging
> enabled, userspace is 32bit.
This sounds like a Debian bug in the init process logic. Care to file a
bug in their system for it?
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-02 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 11:21 udevd induced deadlock in loading kernel modules? Petr Vandrovec
2008-02-02 18:55 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-02 11:07 Petr Vandrovec
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=20080202185507.GC13005@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.