linux-kernel - Re: 2.6.33.2 does not boot on Atom?

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

Message-ID: <20100413182248.GA8468@linux-m68k.org>
Date:	Tue, 13 Apr 2010 20:22:48 +0200
From:	Richard Zidlicky <rz@...ux-m68k.org>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.33.2 does not boot on Atom?

On Tue, Apr 13, 2010 at 06:28:02AM -0700, Greg KH wrote:
> On Tue, Apr 13, 2010 at 11:09:52AM +0200, Richard Zidlicky wrote:
> > On Sun, Apr 11, 2010 at 11:16:05PM -0700, Greg KH wrote:
> > > On Tue, Apr 06, 2010 at 10:55:09PM +0200, Richard Zidlicky wrote:
> > > > Hi,
> > > > 
> > > > I have been compiling my own kernels since ages and switched from 2.6.32.8 to 
> > > > 2.6.33.2 now.
> > > > Same procedure like allways - copied .config to new buildtree, make menuconfig
> > > > (almost nothing changed in config), installed the new kernel on 2 machines.
> > > 
> > > Oops, that's the problem, you need to do 'make oldconfig' to ensure you
> > > didn't miss anything, and to adjust any new defaults.
> > 
> > I can confirm that "make oldconfig" does not fix the problem.
> > 
> > Grub appears to load the kernel (at least it does not come back with an error as it otherwise
> > would), cursor in the topleft corner and absolutely no activity. 
> > no reaction to ctrl-alt-del or magic keys. For all other kernels I would see at least the
> > "uncompressing kerne.." message, not here.
> 
> Try asking on a Fedora kernel list as this might just be a config issue
> with the way modesetting is set up.

it is a clean kernel.org kernel, with early printk and I tried playing with 
various (no)rhgb noquiet options just to be sure. So this does really appear to
be something that happens in the earliest bootstages before uncompressing and
can not think how it could be Fedora's fault - it does not get anywhere close
to touching the initramd image.
The only way I can proceed is try some kind of bisecting.. real bisect won't
work as the wlan connection is painfully slow with the only working kernel
taht I have installed on that computer.

Btw I have filled a Fedora bug against a 2.6.32.11-fedora kernel with broken
kms but afaics this appears to be totally unrelated.

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