linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <mflt1@micrologica.com.hk>
Cc: <akpm@digeo.com>, <ldl@aros.net>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.73-mm1 nbd: boot hang in add_disk at first call from nbd_init
Date: Sat, 28 Jun 2003 10:20:26 -0700 (PDT)	[thread overview]
Message-ID: <33004.4.4.25.4.1056820826.squirrel@www.osdl.org> (raw)
In-Reply-To: <200306281346.53609.mflt1@micrologica.com.hk>

> On Saturday 28 June 2003 12:55, Michael Frank wrote:
>> On Saturday 28 June 2003 10:41, Andrew Morton wrote:
>> > Michael Frank <mflt1@micrologica.com.hk> wrote:
>> > > Changes were recently made to the nbd.c in 2.5.73-mm1
>> >
>> > And tons more will be in -mm2, which I shall prepare right now. Please
>> retest on that and if it still hangs, capture the output from pressing
>> alt-sysrq-T.
>>
>> Legacy free, no serial port.
>>
>>
>>
>> Sorry, -mm2 hang at booting kernel on 2 machines.
>>
>
> Oh Murphy! Bug: 250K log buffer causes a hang on boot.
>
> Sorry for the shock. I configured the log buffer bigger - 250K and it hangs
> on boot.
>
> Default 14K log buffer all OK, the NBD hang is fixed too.

Default value of 14 is a shift count (2 << 14), which gives a
16 KB buffer.
Did you enter '250' for the shift value?
Yes, that wouldn't boot.
Maybe consult the help text??

> This was my only config change besides that driver which didn't compile ;)
>
> I want a bigger log buffer in preparation for testing swsusp on 2.5. On 2.4,
>  the test io load prevent the big swsusp logs from making it to disk...

Andrew, do you want a min/max limit on the LOG_BUF_SHIFT value,
now that Roman has added that feature for Kconfig?

~Randy




  reply	other threads:[~2003-06-28 17:06 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 [this message]
2003-06-29  7:32         ` Michael Frank
2003-06-30 15:51     ` Lou Langholtz
2003-06-30 15:24 ` Lou Langholtz

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=33004.4.4.25.4.1056820826.squirrel@www.osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@digeo.com \
    --cc=ldl@aros.net \
    --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).