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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Jul 2009 08:09:16 -0700
From:	Greg KH <gregkh@...e.de>
To:	Wolfgang Walter <wolfgang.walter@...m.de>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: Linux 2.6.30.2: does not boot

On Mon, Jul 20, 2009 at 04:13:22PM +0200, Wolfgang Walter wrote:
> Am Montag, 20. Juli 2009 schrieb Greg KH:
> > I'm announcing the release of the 2.6.30.2 kernel.  All users of the
> > 2.6.30 kernel series are very strongly encouraged to upgrade.
> >
> > I'll also be replying to this message with a copy of the patch between
> > 2.6.30.1 and 2.6.30.2
> >
> > The updated 2.6.30.y git tree can be found at:
> >        
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.30.y.git and
> > can be browsed at the normal kernel.org git web browser:
> >        
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=summa
> >ry
> >
> > thanks,
> >
> > greg k-h
> >
> 
> Built 2.6.30.2 but it hangs when booting immediately after the message:
> 
> Booting the kernel.
> 
> I built it with gcc version 4.3.3 on debian/sid and used exactly the 
> same .config as I used with 2.6.32.1  (ok, + "DEFAULT_MMAP_MIN_ADDR 4096" 
> which didn't exist before).

Can you do 'git bisect' to see which patch caused the problem?  It might
be the one, "Don't use '-fwrapv' compiler option: it's buggy in
gcc-4.1.x", but it would be good to figure it out for sure.

thanks,

greg k-h
--
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/