All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: Ingo Molnar <mingo@elte.hu>, Jens Axboe <jens.axboe@oracle.com>,
	Arjan van de Ven <arjan@infradead.org>
Cc: Justin Madru <jdm64@gawab.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.30-rc1: invalid opcode with call trace
Date: Fri, 10 Apr 2009 10:15:15 +0200	[thread overview]
Message-ID: <20090410081515.GA17762@fancy-poultry.org> (raw)
In-Reply-To: <20090408065201.GA6490@elte.hu>

On 08.04.2009, Ingo Molnar wrote: 

One additional bug which is caused by commit 9710794:

> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > I too have an async hang/crash, on an old-style SCSI (aic7xxx) box 
> > - hang log attached below.
> > [...]
> >
> > ( Full bootlog attached below as well - i'm sending the config as a 
> >   reply as this mail is close to lkml size limits already. )
> 
> Config attached.
> 
>  known bad  : v2.6.29-9854-gd508afb
>  known good : v2.6.29
> 
> Suspected commit introducing the regression:
> 
>  9710794: async: remove the temporary (2.6.29) "async is off by default" code
> 
> (i'll now try a revert of this.)
> 
> 	Ingo

When trying to boot 2.6.30-rc1, -git3 on my notebook, which
has an encrypted root partition (LUKS/dmcrypt), the root fs can
not be found any more. 

The bootscreen finally shows:
[....]
Could not find /dev/mapper/root
...exiting to /bin/sh

And the system is dead. Since there's no root fs available, I can't provide
any more information on this.

BUT: Ingo's reversion does fix this.

Regards, 
Heinz.


  parent reply	other threads:[~2009-04-10  8:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  5:30 2.6.30-rc1: invalid opcode with call trace Justin Madru
2009-04-08  6:32 ` Jens Axboe
2009-04-08  6:47   ` Ingo Molnar
2009-04-08  6:52     ` Ingo Molnar
2009-04-08  6:53       ` Jens Axboe
2009-04-08  7:11         ` Ingo Molnar
2009-04-08  7:15           ` Jens Axboe
2009-04-08  7:11         ` Justin Madru
2009-04-08  8:12       ` Ingo Molnar
2009-04-10  8:15       ` Heinz Diehl [this message]
2009-04-08  7:27     ` Vegard Nossum
2009-04-08  7:40       ` Jens Axboe
2009-04-08  7:48         ` Ingo Molnar
2009-04-08  7:56           ` Jens Axboe
2009-04-08 16:15           ` Vegard Nossum
2009-04-09 14:45             ` Cornelia Huck

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=20090410081515.GA17762@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --cc=arjan@infradead.org \
    --cc=jdm64@gawab.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.