From: Eric Paris <eparis@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: kernel panic - not syncing: out of memory and no killable processes
Date: Thu, 17 Sep 2009 17:31:59 -0400 [thread overview]
Message-ID: <1253223119.5213.359.camel@dhcp231-106.rdu.redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0909171417020.19006@chino.kir.corp.google.com>
On Thu, 2009-09-17 at 14:24 -0700, David Rientjes wrote:
> On Thu, 17 Sep 2009, Eric Paris wrote:
> Looks udevd related, and you mentioned that this is the point where it
> always panics in your initial report. It doesn't appear to be a VM issue.
> Finding that change between next-20090911 and next-20090914 may be time
> consuming.
Absolutely 100% udevd related. It always pops right when udev starts.
Every time. I don't know how to get that to come out on the serial
port, you only get to see the kernel messages (although there is nothing
on the screen other than "Starting udev"
Reverting 3f2aa307c4d26b4ed6509d0a79e8254c9e07e921 causes the problem to
go away. I now am running a 79b520e87e kernel + your patch (adding
console_verbose()) + reverting 3f2aa307c4d2 and it seems to be working.
-Eric
next prev parent reply other threads:[~2009-09-17 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 3:36 Eric Paris
2009-09-17 12:43 ` Eric Paris
2009-09-17 20:29 ` David Rientjes
2009-09-17 20:35 ` Eric Paris
2009-09-17 21:01 ` Eric Paris
2009-09-17 21:15 ` Eric Paris
2009-09-17 21:24 ` David Rientjes
2009-09-17 21:31 ` Eric Paris [this message]
2009-09-17 21:59 ` David Rientjes
2009-09-18 14:58 ` Eric Paris
2009-09-18 19:58 ` David Rientjes
2009-09-17 21:27 ` Eric Paris
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=1253223119.5213.359.camel@dhcp231-106.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.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
all inboxes | Powered by JetHome®