linux-kernel - 2.6.36 does not boot properly

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

Date:	Mon, 13 Dec 2010 00:19:40 +0100
From:	CSÉCSY László <boobaa@...galware.org>
To:	Don Zickus <dzickus@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>, gorcunov@...il.com,
	aris@...hat.com, peterz@...radead.org, Ingo Molnar <mingo@...e.hu>,
	VAJNA Miklós <vmiklos@...galware.org>,
	linux-kernel@...r.kernel.org
Subject: 2.6.36 does not boot properly

Hi all,

I have recently upgraded from kernel-2.6.35-5-i686.fpm (which is a 2.6.35.7 
speaking upstream's terms) to kernel-2.6.36-1-i686.fpm (which is a 2.6.36) on 
my ASUS K50IJ laptop running Frugalware Linux -current, and it failed to boot 
when I used the usual command line:

kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 ro quiet resume=/dev/sda5

"Failed to boot" means that the thing does not even output even a single 
character after "[Linux-bzImage, setup=0x3000, size=0x3c5380]" but hangs - 
even C-A-Del does not do anything (I do have waited for half an hour). 
Pressing the power button (it does not matter for how long) turns the laptop 
off immediately.

When I used the most-safest-without-any-magic cmdline that our kernel package 
maintainer supposed, it did boot, but failed to start X:

kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 ro showopts ide=nodma apm=off \
acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0

Obviously, this means I had two options: change my way of working (suspending 
to ram all the time, reboot only upon kernel and low-level stuff upgrades) or 
going back to 2.6.35(.7). I took the latter, but I do know I cannot stay 
behind for too much time, so I was supposed to bisect this for myself.

Reproducing steps:

Upgrade to 2.6.36 (or anything newer) and reboot. Given the laptop freezes 
immediately, I cannot really attach logs.

Attached are:

1. the "git bisect log" output - I had to "git bisect skip" several times, 
probably because of staging drivers being enabled;

2. the last "git bisect bad" output;

3. the kernel config I was using all the time;

4. output of "dmesg" while using v2.6.35-rc6-238-g9373662 (which was the last 
"good" kernel while bisecting);

5. output of "dmidecode".

Additional info:

The first "bad" build while bisecting caused the above-mentioned freeze, but 
the latest 4 were all panicking immediately after boot - here is the 
"screenshot" I created with my camera:

http://frugalware.org/~boobaa/shots/DSCF1349.JPG

Feel free to ask for more info if needed and thanks for your help.
-- 
Bye, Boobaa (CSÉCSY László)
http://csecsy.hu

Download attachment "config.i686.gz" of type "application/x-gzip" (31297 bytes)

Download attachment "dmesg.txt.gz" of type "application/x-gzip" (12035 bytes)

View attachment "dmidecode.txt" of type "text/plain" (12047 bytes)

View attachment "git-bisect-bad.txt" of type "text/plain" (1416 bytes)

View attachment "git-bisect-log.txt" of type "text/plain" (3530 bytes)