RE: Problems with EDAC coexisting with BIOS
- From: "Gross, Mark" <mark.gross@xxxxxxxxx>
- Date: Mon, 24 Apr 2006 11:14:04 -0700
-----Original Message-----Ong,
From: Alan Cox [mailto:alan@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, April 24, 2006 10:50 AM
To: Gross, Mark
Cc: bluesmoke-devel@xxxxxxxxxxxxxxxxxxxxx; LKML; Carbonari, Steven;
Soo Keong; Wang, Zhenyu Zrelated
Subject: RE: Problems with EDAC coexisting with BIOS
On Llu, 2006-04-24 at 08:57 -0700, Gross, Mark wrote:
I think what I'm saying is pretty clear and I don't think it is
failto whatever workarounds where done earlier.
Ok. I was concerned as I seem to remember an earlier errata fix enabled
the memory controller temporarily to do a workaround on one bridge. We
hit this because it unconditionally disabled it afterwards and Intel
sent fixes for RHEL4. I don't believe the workaround in question is in
the current tree as it was fixed elsewhere.
Just worried that if that is the case an SMI the wrong moment might
to apply the workaround.screwing
Why did Intel bother implementing this functionality and then
it up so that OS vendors can't use it ? It seems so bogus.
It was just a screw up not to have identified this issue sooner.
Ok. So the intention was that the OS should also be able to access this
material.
The E752x Si is made to allow access to the device / Function. However;
when it's integrated onto a MoBo with BIOS there can be implementations
where we get into this coordination issue.
theAt the very least we should print a warning advising the user that
thatBIOS is incompatible and to ask the BIOS vendor for an update so
they can enable error detection and management support.
I would place the warning in the probe or init code.
Agreed, and then bale out. Customer pressure should do the rest if the
BIOS needs updating, or ACPI or similar need to grow a 'shared' API for
this so the BIOS and OS can co-operate.
Yes and yes.
I'm having trouble getting the dev0:fun1 hidden by bios test into the
e752x_init code. It seems to be a shame having to fail the probe1 and
leave the driver loaded in memory. Are there any recommendations on a
good way to do this?
--mgross
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: Re: Van Jacobson's net channels and real-time
- Next by Date: Re: Time to remove LSM (was Re: [RESEND][RFC][PATCH 2/7] implementation of LSM hooks)
- Previous by thread: RE: Problems with EDAC coexisting with BIOS
- Next by thread: RE: Problems with EDAC coexisting with BIOS
- Index(es):
Relevant Pages
|
