From: Lou Langholtz <ldl@aros.net>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.73-mm1 nbd: boot hang in add_disk at first call from nbd_init
Date: Mon, 30 Jun 2003 09:24:17 -0600 [thread overview]
Message-ID: <3F005621.1060708@aros.net> (raw)
In-Reply-To: <200306271943.13297.mflt1@micrologica.com.hk>
Michael Frank wrote:
>Changes were recently made to the nbd.c in 2.5.73-mm1
>
>When using nbd.c ex 2.5.73 boot OK.
>acpi=off no effect
>
>----------------------------
>dmesg using nbd.c ex 2.5.73:
>
>loop: loaded (max 8 devices)
>anticipatory scheduling elevator
>
>(Using nbd.c ex 2.5.73-mm1
> nbd: registered device at major 43
> hang) . . .
>
Thank you for reporting this. A few others have also found this same
problem and a patch that fixes this has been submitted to Andrew. I
haven't had the chance yet to figure out what release of mm this fix may
have made it into. The reason for this problem in the first place was
that the patch which caused the problem was tested against 2.5.73 then
applied into Andrew's 2.5.73-mm1 release. Some other changes that made
it into 2.5.73-mm1 (in a non-nbd system that also hadn't been in 2.5.73
yet) interacted with the nbd change in the un-expected way you've seen.
If there are still problems you can track back to nbd please let me know.
prev parent reply other threads:[~2003-06-30 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 1:51 2.5.73-mm1 nbd: boot hang in add_disk at first call from nbd_init Michael Frank
2003-06-28 2:41 ` Andrew Morton
2003-06-28 4:55 ` Michael Frank
2003-06-28 5:51 ` Michael Frank
2003-06-28 17:20 ` Randy.Dunlap
2003-06-29 7:32 ` Michael Frank
2003-06-30 15:51 ` Lou Langholtz
2003-06-30 15:24 ` Lou Langholtz [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=3F005621.1060708@aros.net \
--to=ldl@aros.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
/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;
as well as URLs for NNTP newsgroup(s).