Bug 15880

Summary:	Very bad regression from 2.6.33 as of 1600f9def
Product:	Platform Specific/Hardware	Reporter:	Maciej Rutecki (maciej.rutecki)
Component:	x86-64	Assignee:	platform_x86_64 (platform_x86_64)
Status:	RESOLVED INSUFFICIENT_DATA
Severity:	normal	CC:	alan, eternaleye, hpa, maciej.rutecki, rjw
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.33	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	Diff between 2.6.33-zen0 config (working) and 2.6.33 vanilla config (broken) Diff between 2.6.33-zen0 config (working) and 2.6.34-zen0 config (broken)

Description Maciej Rutecki 2010-04-29 17:39:08 UTC

Subject    : Very bad regression from 2.6.33 as of 1600f9def
Submitter  : Alex Elsayed <eternaleye@gmail.com>
Date       : 2010-04-29 2:28
Message-ID : loom.20100429T041908-663@post.gmane.org
References : http://marc.info/?l=linux-kernel&m=127250825306178&w=2

This entry is being used for tracking a regression from 2.6.33.  Please don't
close it until the problem is fixed in the mainline.

Comment 1 Rafael J. Wysocki 2010-06-13 12:29:30 UTC

Apparently, not a regression, but a "different .config" problem.  Removing from the list.

Comment 2 Alex Elsayed 2010-06-13 19:49:30 UTC

Rafael, do you know what .config option is causing this? I've been unable to find it, so I can't build any new kernels. (Currently running 2.6.33, which is less than optimal.)

Comment 3 Rafael J. Wysocki 2010-06-13 23:35:09 UTC

Not at the first sight, but you have some unusual storage-related .config options set.  I'd start from these.

[Also please attach the diff between the working and non-working .config from
2.6.33 to this bug entry.]

Comment 4 Alex Elsayed 2010-06-14 03:15:34 UTC

Created attachment 26756 [details]
Diff between 2.6.33-zen0 config (working) and 2.6.33 vanilla config (broken)

Comment 5 Alex Elsayed 2010-06-14 03:16:52 UTC

Created attachment 26757 [details]
Diff between 2.6.33-zen0 config (working) and 2.6.34-zen0 config (broken)

Comment 6 Alex Elsayed 2010-06-14 03:18:29 UTC

I attached diffs against a more recent version of the same (specialized) kernel as well as against vanilla 2.6.33, both of which have the same failure mode on boot.

Comment 7 H. Peter Anvin 2010-06-14 05:17:06 UTC

A "git bisect" would be more useful.

Comment 8 Alex Elsayed 2010-06-14 06:47:05 UTC

Tried that. Even going back to revisions prior to the one that worked give the problem when I input the working config and 'make oldconfig'