Bug 33271
Summary: | MP table in the EBDA can be UNSAFE | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Le Tanou Jerome <jerome.le-tanou> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-27 13:58:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Le Tanou Jerome
2001-03-26 17:37:20 UTC
It is only a debugging message and may be safely ignored. In fact, we have 3 netfinity 5100 with Redhat 6.2 and on only one of them we have the message "MP table in the EBDA can be UNSAFE". The most disturbing is that we have not this message on both other machines, so can we really ignore this message? What is its meaning? Thanks a lot. It's the kernel detecting that the bios has put a critical piece of information in a memory-location that can be trashed by (older versions of) LILO. This is a bios bug (eg it violates a spec), however recent version of LILO are believed to have a workaround for this. If this workaround would fail to work, you would see a lot of crashes in SMP mode. |