linux-kernel - Re: Linux 2.6.30.2: does not boot

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

Message-ID: <20090720211908.GA31814@superlopez.pirispons.net>
Date:	Mon, 20 Jul 2009 23:19:09 +0200
From:	Kiko Piris <kernel@...ispons.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Damien Wyart <damien.wyart@...e.fr>, Greg KH <gregkh@...e.de>,
	Wolfgang Walter <wolfgang.walter@...m.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.30.2: does not boot

On 20/07/2009 at 12:50 -0700, Linus Torvalds wrote:

> Just to clarify:
> 
>  - you literally have a _working_ 2.6.30.1 that you compiled yourself a 
>    few days ago.

That’s correct.

>  - But when you try to compile that same kernel _now_, it fails with an 
>    immediate reboot? And not just 2.6.30.2, but 2.6.30.1 does that too?

Also correct.

> That certainly implies something else than just the -fwrapv vs 
> -fno-strict-overflow thing.

Yes, as Marcel Beister pointed, it resulted some binutils bug.
Downgrading the package produced a perfectly bootable 2.6.30.2.

> But we may be looking at two different issues, so maybe your "unable to 
> compile a working kernel" issue is different from the other reports.

Totally unrelated to other reports, and not a kernel bug, in fact.

Sorry if caused any confussion.

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