linux-kernel - Re: 3.1+ kernels unbootable

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAErSpo6qx1mt+E8NB+qkMvvcc0_1XFY=kZkcwS3bAyXDajB3_g@mail.gmail.com>
Date:	Mon, 21 May 2012 15:40:23 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Chris Jones <chrisjones@...n.net.au>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NeilBrown <neilb@...e.de>
Subject: Re: 3.1+ kernels unbootable

On Sat, Apr 28, 2012 at 8:21 PM, Chris Jones <chrisjones@...n.net.au> wrote:
> On Wed, 25 Apr 2012 14:44:52 +1000
> NeilBrown <neilb@...e.de> wrote:
>
>>
>> You have a couple of options here.
>>
>> One is to use git-bisect to narrow down where the breakage is.  This
>> means building about a dozen or a score of kernels and testing each
>> one and then trying again.  If you are happy building your own
>> kernels and have an afternoon to spare this is probably a good idea.
>> There should be plenty of instruction on the web about how to do this
>> but if you cannot find any feel free to ask.
>>
>> The other is to try turning features off and debugging on.
>> Many distros have some sort of "fail-safe" boot option which disables
>> things like ACPI and known-problematic drivers... though with it
>> failing so early most drives won't have even tried to run.  I'd guess
>> an ACPI problem, but that is largely because I know almost nothing
>> about ACPI so it is easy to blame it.  So try adding "acpi=off" to
>> the boot args.
>>
>> Linux has a thing called 'early_printk' which allows messages to be
>> displayed even before the normal drivers are loaded.  I don't know
>> much about enabling that on an x86 system (I use it a lot on ARM
>> though).  You need it enabled when the kernel is compiled, and you
>> need a boot arg to enable it too.  Maybe if you manage to enable
>> that you might get some message printed.
>>
>> Or maybe there is some other much more useful thing you can try and
>> someone else will chime in soon and tell me I don't know what I'm
>> talking about and explain in detail the right way so solve this
>> problem - that would be awesome.
>>
>> NeilBrown
>
> I have tried all ACPI disabled options and also all safe-mode options,
> among many other modes. Nothing has worked.
>
> Now that Ubuntu 12.04 has gone gold, I might try the latest kernel in
> that and see if anything has changed.

Any luck on this?

Bjorn
--
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/