Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Jul 2010 15:57:29 +0200
From:      Markus Gebert <markus.gebert@hostpoint.ch>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-stable <freebsd-stable@freebsd.org>
Subject:   Re: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?
Message-ID:  <0CF6CF2B-907C-42EF-B57E-DF50F0564455@hostpoint.ch>
In-Reply-To: <201007120851.35529.jhb@freebsd.org>
References:  <6B57591F-9FA2-45EB-825F-1DB025C0635D@hostpoint.ch> <08562D52-02AA-46CF-BFCD-00D0A3C4DC34@hostpoint.ch> <FFB367B2-232D-460D-82B8-C3F03F1B53BE@hostpoint.ch> <201007120851.35529.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On 12.07.2010, at 14:51, John Baldwin wrote:

>> Well, the situation has changed. Machine died over the weekend =
running our=20
>> test load with above kernel configuration. It seems that not having =
ehci in=20
>> the kernel at boot just makes the MCE much more unlikely to occur, =
but it=20
>> occurs. With ehci, I can panic the machine within a minute, without =
ehci it=20
>> seems to take at least hours. Still, I don't get why not having the =
ehci=20
>> driver in the kernel should have any effect, especially because =
nothing is=20
>> attached to it.
>=20
> Ok, so maybe the SMI# interrupts do play a role somehow, at least as =
far as=20
> altering the timing.

Hm, if I've understood your other email correctly, disabling usb legacy =
support should get rid of SMIs just as well as loading the ehci driver. =
What I tested was kernel with ehci (panic within a minute) versus kernel =
without ehci (panic within hours), but both cases with usb legacy =
support disabled in BIOS. So, again, if I understand this correctly, the =
"SMI rate" should have been the same in both cases, because usb legacy =
support was turned off entirely, and therefore loading or not loading =
ehci should not impact the SMI rate. If this should be the case, why =
would there be an altering of timings between these two test cases?

Since SMM is out the the OS' control, I guess there's no good way to =
track SMIs?


Markus=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0CF6CF2B-907C-42EF-B57E-DF50F0564455>