[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200906100119.37479.rjw@sisk.pl>
Date: Wed, 10 Jun 2009 01:19:36 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: Avi Kivity <avi@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13116] Can't boot with nosmp
On Tuesday 09 June 2009, Stephen Hemminger wrote:
> On Tue, 09 Jun 2009 21:42:55 +0300
> Avi Kivity <avi@...hat.com> wrote:
>
> > Stephen Hemminger wrote:
> >
> >
> >
> > >> This only affects reboots. But yes, the cpumask code has bugs. Does
> > >> the .config involved select MAXSMP?
> > >>
> > >>
> > >
> > > Patch does not fix the problem. Not sure if it is KVM only problem.
> > > Look like possible cpumask always equals what ACPI / SMP tables report.
> > > So currently looking into alloc_percpu which may not handle the possible
> > > but never used cpus.
> > >
> > >
> >
> > Right, it shouldn't have.
> >
> > > It is x86-64 config and does not have MAXSMP set. It does have NR_CPUS set.
> > >
> >
> > So it's not cpumask. Dare I suggest a bisect?
> >
>
> I did some testing of different versions.
>
> * Problem does not exist with 2.6.30-rc8 (so regression should be closed).
Done.
Thanks,
Rafael
--
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