mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: kernel panic - not syncing: out of memory and no killable processes
Date: Thu, 17 Sep 2009 08:43:55 -0400	[thread overview]
Message-ID: <1253191435.5213.209.camel@dhcp231-106.rdu.redhat.com> (raw)
In-Reply-To: <1253158603.5213.204.camel@dhcp231-106.rdu.redhat.com>

On Wed, 2009-09-16 at 23:36 -0400, Eric Paris wrote:
> Starting on Sept 14 linux-next became unbootable on my KVM guests.
> Latest I tried was linux-next as of today, Sept 16.  I spent the day
> today bisecting between next-20090911 and next-20090914 which was the
> last and first day linux-next broke.
> 
> My fedora 12 install gets to udev starting and then panics with the
> message:
> 
> Kernel panic - not syncing: Out of memory and no killable processes...

the next-20090916 tree still panic's the same way.  As does Linus'
latest git tree ab86e5765

I'll try bisecting between v2.6.31 and master if it would give better
data than trying to bisect between two -next trees, but I'm sorta stuck
with a machine that won't boot and doesn't tell me much about why.

-Eric


  reply	other threads:[~2009-09-17 12:44 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 [this message]
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
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=1253191435.5213.209.camel@dhcp231-106.rdu.redhat.com \
    --to=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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®