New: 2.6.28.9 causes init to segfault on Debian etch; 2.6.28.8 OK
A message that is not in the archive (sent off-list or not yet received): [email protected]/
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).
-fwrapv killed Barry's gcc-4.1.2-compiled kernel in 2.6.27.x, 2.6.28.x and presumably 2.6.29, 2.6.30.
Quoted 63 lines · On Sun, 5 Apr 2009 13:04:02 GMT [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=13012
Summary: 2.6.28.9 causes init to segfault on Debian etch; 2.6.28.8 OK Product: Other Version: 2.5 Kernel Version: 2.6.28.9 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [email protected] Regression: Yes(I haven't had a chance to collect all that data that I wanted to collect before reporting this bug, but this might be the best I can do for the next few days, so I think it's best for me to submit what I have so far instead of sitting on it.)
The system in question is a Debian etch system which has a static /dev (no udev) and does not use an initrd or initramfs. With 2.6.28.8, it works fine. With 2.6.28.9, init segfaults during boot, so the system fails to finish booting. (Same problem happens on 2.6.27.21 and does not happen on 2.6.27.20, but I have not had time to investigate that version in depth.)
git bisect says "
92db6956ecd01ceb7934be0252b3b184a82ebb64is first bad commit". That's "Add '-fwrapv' to gcc CFLAGS". If I take 2.6.28.9 and I revert "Move cc-option to below arch-specific setup" and "Add '-fwrapv' to gcc CFLAGS" then the resulting kernel works again.I also noticed that the problem only happens with some gcc's:
Problem occurs:
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) gcc-4.1 (GCC) 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)Problem does not occur (i.e. 2.6.28.9 works and I don't have to revert anything):
gcc-4.2 (GCC) 4.2.4 (Debian 4.2.4-6)
gcc (Debian 4.3.2-1.1) 4.3.2(BTW, on 2.6.29, I'm having a problem where if I'm running 2.6.29 then make instantly blows up in a strange way, and the same pattern of working/failing compilers is showing up there too.)
I have not yet had a chance to try vanilla gcc 4.1.2. That's what I intend to try next.
I'll attach my .config within the next 24 hours, and I'll try to post serial console captures by sometime Tuesday or so. If there's any other information which would help, feel free to ask...
My gut feeling is that this is truly a gcc bug rather than a kernel bug, but it's still disconcerting to see this kind of breakage suddenly pop up in a -stable series, so IMO it may be worth considering reverting the -fwrapv changes for 2.6.2[78].y.
Quoted 3 lines · Andrew Morton
-fwrapv killed Barry's gcc-4.1.2-compiled kernel in 2.6.27.x, 2.6.28.x and presumably 2.6.29, 2.6.30.
Auughh. I hate compiler bugs. They're horrible to debug.
I _think_ 'fwrapv' only really matters with gcc-4.3, so maybe we could just enable it for new versions.
HOWEVER, I also wonder if we could instead of "-fwrapv" use "-fno-strict-overflow". They are apparently subtly different, and maybe the bug literally only happens with -fwrapv.
Barry, can you see if that simple "replace -fwrapv with -fno-strict-overflow" works for you?
Or just go with Barry's helpful debugging:
Quoted 10 lines
Quoted 10 lines
I also noticed that the problem only happens with some gcc's:
Problem occurs:
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) gcc-4.1 (GCC) 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)Problem does not occur (i.e. 2.6.28.9 works and I don't have to revert anything):
gcc-4.2 (GCC) 4.2.4 (Debian 4.2.4-6)
gcc (Debian 4.3.2-1.1) 4.3.2
and consider 4.2 to be the point where it's ok.
Do we have some gcc developer who
(a) knows what the rules are
and
(b) might even help us figure out where the bug occurs?
Linus