Date: Tue, 26 Feb 2008 16:40:08 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-amd64@freebsd.org Cc: gavin@freebsd.org, freebsd-i386@freebsd.org, morten@ngdc.net Subject: Re: amd64/88020: cannot boot unless: hint.apic.0.disabled="1" is set on xSeries336 Message-ID: <200802261640.08563.jhb@freebsd.org> In-Reply-To: <200802261123.m1QBN5sD084896@freefall.freebsd.org> References: <200802261123.m1QBN5sD084896@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 26 February 2008 06:23:05 am gavin@freebsd.org wrote: > Synopsis: cannot boot unless: hint.apic.0.disabled="1" is set on xSeries336 > > State-Changed-From-To: suspended->open > State-Changed-By: gavin > State-Changed-When: Tue Feb 26 10:44:43 UTC 2008 > State-Changed-Why: > Unsuspend, I've found other people with the same issue. Both > <mich at freebsd.org> and <avleeuwen at gmail.com> confirm that > disabling the built-in network interface allows the machine to boot > 6.x. Apparently, this is resolved in at least 7.0-RC2 amd64 (according to > http://docs.FreeBSD.org/cgi/mid.cgi?6eb82e0711060722g2a7876ccrd3eaf8912f5e84fa ) > > > Responsible-Changed-From-To: freebsd-i386->freebsd-amd64 > Responsible-Changed-By: gavin > Responsible-Changed-When: Tue Feb 26 10:44:43 UTC 2008 > Responsible-Changed-Why: > This seems to be amd64 specific. FreeBSD/i386 seems to work fine > on this hardware. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=88020 I don't see this being amd64 specific at all. The interrupt code on i386 and amd64 is identical (and the APIC code for that matter). I would be curious what happens with a newer snap (such as 6.3) and for a verbose dmesg from a boot with APIC enabled. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802261640.08563.jhb>