linux-kernel - Re: 2.6.30-rc1: invalid opcode with call trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 10 Apr 2009 10:15:15 +0200
From:	Heinz Diehl <htd@...cy-poultry.org>
To:	Ingo Molnar <mingo@...e.hu>, Jens Axboe <jens.axboe@...cle.com>,
	Arjan van de Ven <arjan@...radead.org>
Cc:	Justin Madru <jdm64@...ab.com>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 2.6.30-rc1: invalid opcode with call trace

On 08.04.2009, Ingo Molnar wrote: 

One additional bug which is caused by commit 9710794:

> * Ingo Molnar <mingo@...e.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/