linux-kernel - Re: 2.6.29-rc2 dies on startup

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87eiyok9vc.fsf@tac.ki.iif.hu>
Date:	Tue, 27 Jan 2009 17:10:47 +0100
From:	Ferenc Wagner <wferi@...f.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, arve@...roid.com
Subject: Re: 2.6.29-rc2 dies on startup

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Mon, 19 Jan 2009 13:53:31 +0100 Ferenc Wagner <wferi@...f.hu> wrote:
>
>> I'm running 2.6.28 without problems.  I decided to give 2.6.29-rc2 a
>> try.  It crashes very early during boot, see screenshot, config and lspci
>> under http://apt.niif.hu/2.6.29-rc2/.  CPU is AMD Athlon(tm) XP 1800+,
>> kernel command line: root=/dev/hda1 ro.  I fixed the pcf50663 compile
>> error by hand, and have a small patch on /drivers/acpi/battery.c, but
>> that module isn't loaded on this system.  I can hook up a serial
>> console for further info if needed.
>
> What a ghastly backtrace.
>
> At a guess I'd say that drivers/staging/android/ram_console.c is calling
> the reed-solomon code earlier than it's expecting.  But that might be
> totally wrong.
>
> Please set CONFIG_STAGING=n and retest.

Indeed, with CONFIG_STAGING unset the kernel boots up fine!  Before
testing I pulled again, set CONFIG_CLASSIC_RCU=y and
CONFIG_FRAME_POINTER=y, but the resulting kernel still crashed (serial
log attached).  Then I unset CONFIG_STAGING and that worked.

Should I also test Arve's patch?

Regards,
Feri.


View attachment "crash.log" of type "text/plain" (10371 bytes)