From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org, rgooch@atnf.csiro.au, viro@math.psu.edu
Subject: Re: 2.5.51 + devfs root + SMP = lockup
Date: Thu, 12 Dec 2002 16:14:36 -0800 [thread overview]
Message-ID: <200212130014.QAA00316@baldur.yggdrasil.com> (raw)
I'm embarrassed to say that I wrote:
> Linux 2.5.51 with SMP and devfs hangs at boot time when trying
>to find the initial root device (/dev/ram0 in my case). [...]
This was self-inflicted. When I removed the spontaneous
partition table rereading code from devfs, I did not notice that
get_removal_partition does a read_unlock(&parent->u.dir.lock), so I
was leaving a read lock in place where I deleted the call to this
routine. Sorry for wasting anyone else's time with it.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2002-12-13 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 0:14 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 5:41 2.5.51 + devfs root + SMP = lockup Adam J. Richter
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=200212130014.QAA00316@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
--cc=viro@math.psu.edu \
/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.