Date: Mon, 2 May 2011 23:44:10 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: <mike@karels.net>, <freebsd-amd64@freebsd.org> Cc: mike_karels@mcafee.com Subject: Re: variable hang when starting APs on Westmere processors Message-ID: <67C27574157340E498DE203A8D0FA35E@multiplay.co.uk> References: <201105022113.p42LDLrl051285@mail.karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
We run 8.2 happily on L5640's which are also hex-core CPU's so the issue
could be bios / MB related and not cpu.
Its likely unrelated given your debug info but when we have seem long
hangs on boot in the past its been related to keyboard stuff. You might
want to try the following at the loader to see if it helps:-
set hint.atkbdc.0.disabled=1
set hint.atkbd.0.disabled=1
boot
Regards
Steve
----- Original Message -----
From: "Mike Karels" <mike@karels.net>
To: <freebsd-amd64@freebsd.org>
Cc: <mike_karels@mcafee.com>
Sent: Monday, May 02, 2011 10:13 PM
Subject: variable hang when starting APs on Westmere processors
> Looks like freebsd-smp is gone... not sure of the right target for this.
>
> I just picked up a problem from another developer at work who had the good
> fortune to have scheduled a vacation this week. The short description is
> that the start_ap() routine sometimes hangs, from 10 minutes to 3 hours,
> while starting up CPUs. This is with a much-modified system based on
> FreeBSD 7.2. A stock 8.2 CD hangs at the same spot almost all the time,
> although the code in the two versions appears identical.
>
> More details: This is amd64, using an Intel S5520HCR 2-socket motherboard
> with two XEON X5660 2.8GHz Westmere hex-core CPUs. The problem happens
> somewhat less with two XEON E5620 Quad core 2.4GHz CPUs. The hang seems
> to happen with higher numbered CPUs, so the hex-core with SMT has more
> chances to hit the problem.
>
> We added KTRs to the code, and found that the hang happens in the
> lapic_ipi_wait() call after de-asserting RESET.
>
> Of course, Linux doesn't exhibit the problem.
>
> Has anyone else seen a problem like this? Any ideas how to fix it, or
> debug further?
>
> Please copy me on responses; I'm not subscribed to this list currently.
>
> Mike
> _______________________________________________
> freebsd-amd64@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"
>
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67C27574157340E498DE203A8D0FA35E>