[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080708083902.e564face.randy.dunlap@oracle.com>
Date: Tue, 8 Jul 2008 08:39:02 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: lkml <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Bug #10872] x86_64 boot hang when CONFIG_NUMA=n
On Tue, 8 Jul 2008 07:16:29 +0200 Ingo Molnar wrote:
>
> * Randy Dunlap <randy.dunlap@...cle.com> wrote:
>
> > > $ git bisect start
> > > $ git bisect bad v2.6.26-rc1
> > > $ git bisect good v2.6.25
> > >
> > > That's only about 1.29M lines of changes.
> >
> > git bisect and normal rebooting did not find a problem.
> >
> > I'll repeat this using kexec to boot the new kernel and see if that
> > locates any issues... since I normally use kexec to load/test new
> > kernels and that was how the failure occurred (occurs).
>
> ah, so the hang only occurs if you kexec a post-v2.6.25 kernel? (from
> any other kernel, or from a post-v2.6.25 kernel?)
Host (first) kernel is 2.6.25 with NUMA=y.
kexec of 2.6.25 with NUMA=n works, kexec of 2.6.26-rc[123456789] with
NUMA=n fails/hangs. kexec of 2.6.26-rc* with NUMA=y works.
kernel configs will be in next email reply to YH.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
--
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