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]
Date:	Wed, 11 Jul 2007 16:27:39 +0200
From:	Stefano Rivoir <s.rivoir@....it>
To:	Martin Orr <martin@...tinorr.name>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.22 released

Martin Orr wrote:
> On 11/07/07 06:38, Stefano Rivoir wrote:
>> Linus Torvalds wrote:
>>> On Tue, 10 Jul 2007, Stefano Rivoir wrote:
>>>> 2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
>>>> and a copy of it where it stops on 2.6.22 (I can't attach the original 2.6.22
>>>> dmesg because it's not logged to disk yet); it actually stops right after
>>>> 'init' launches.
>> Ok, the guilty bit is gcc: in my box, compiling kernel with gcc 4.2.x
>> (which is installed on my debian/sid) turns into a hang (in init,
>> seemingly, maybe not even in kernel itself), while gcc-4.1 is allright.
> 
> I have the same problem, also on Debian sid on amd64.  I can report that the
> Debian version 4.2-20070627-1 of gcc works, 4.2-20070707-1 does not.
> 
> Also the hang occurs in udevsettle; if you wait long enough (60 seconds?)
> then udevsettle times out and the boot continues (but doesn't get very far
> with an almost empty /dev).

I suspected it was something about /dev populating, but I hadn't any 
clue on how to make it go on. To be sure, I've left it "hanging" 
(actually, it's not a completely unresponsive hang, SysRq works fine) 
for even 15 minutes, without any luck.

Could you please try to compile 2.6.22-git1 and see if you get an 
internal gcc error? It is in the first kernel-core related files, you 
should hit it too.

This evening I'll be able to be more precise about the exact file, I 
don't have the box here.

Bye.

-- 
Stefano RIVOIR

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ