public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Christoph Hellwig <hch@infradead.org>,
	Michael Guntsche <mike@it-loops.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]]
Date: Thu, 21 Apr 2011 11:30:07 -0700	[thread overview]
Message-ID: <4DB077AF.7020909@nerdbynature.de> (raw)
In-Reply-To: <BANLkTim7SLt6TMqJQw35=tnACax0mE1URA@mail.gmail.com>

Linus Torvalds wrote on 2011-04-21 10:59 :
> As of right now, all _known_ block bugs should be fixed in the stuff I
> just pushed out, with the current top-of-tree being the merge of the
> IDE CD endless loop issue and the NULL ptr oops at elevator change
> time:

OK, thanks.

> That said, that udevd message of yours would imply a full root
> filesystem, which can cause any amount of issues at boot time..

My /dev is mounted as udev and is 10MB in size, which is more than
enough for kernels < 2.6.39. But with 2.6.39 something changed and
/dev/.udev/queue.bin is growing to 7 MB and more, udevd is spinning like
crazy and the OOM is reaping processes.

I'm currently in the middle of a bisect, with 11 steps to go on this
PowerBook G4 :-\

Thanks,
Christian.
-- 
make bzImage, not war

  reply	other threads:[~2011-04-21 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  2:06 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]] Michael Guntsche
2011-04-15  3:25 ` Linus Torvalds
2011-04-15  4:22   ` Christoph Hellwig
2011-04-15  6:13     ` Jens Axboe
2011-04-21 17:53       ` Christian Kujau
2011-04-21 17:59         ` Linus Torvalds
2011-04-21 18:30           ` Christian Kujau [this message]
2011-04-21 18:36             ` Jens Axboe
2011-04-21 20:53               ` Christian Kujau

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=4DB077AF.7020909@nerdbynature.de \
    --to=lists@nerdbynature.de \
    --cc=hch@infradead.org \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@it-loops.com \
    --cc=torvalds@linux-foundation.org \
    /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