From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Xen-users] 2.6.23 oops Date: Thu, 11 Oct 2007 14:47:14 -0700 Message-ID: <470E99E2.7070300@goop.org> References: <20071011144817.n5x1drwcgug44sg0@whitelist.dk> <200710111629.05457.mark.williamson@cl.cam.ac.uk> <470E5248.1070502@goop.org> <20071011210001.cpd3whfy5ogwkwwc@whitelist.dk> <470E8FE8.6050908@goop.org> <20071011232116.e28c5kuo64o5woow@whitelist.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20071011232116.e28c5kuo64o5woow@whitelist.dk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-15?Q?Morten_B=F8geskov?= Cc: xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org Morten B=F8geskov wrote: > Quoting Jeremy Fitzhardinge : > >> Morten B=F8geskov wrote: >>> I've applied both, and tried with and without SMP, with exactly the >>> same result as before. >>> >>> UP hangs after "installing Xen timer for CPU 0" >> >> Ah, OK. I'd overlooked this one. Hm, I probably haven't tried UP in= a >> while. >> >>> SMP the oops'es the same way except the line no. is now 78. >> >> Oh, that's odd. Could you resend your original bug report? What kind >> of load does it fail under? > > I can't really say what load. It doesn't get that far. Odd. > I've included .config It seems a bit small. Can you send your whole .config so I can rebuild your kernel? J