Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 490567

Summary: [RHEL5.3 Xen]: Annoying messages on i686 boot
Product: Red Hat Enterprise Linux 5 Reporter: Chris Lalancette <clalance>
Component: kernel-xenAssignee: Chris Lalancette <clalance>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: dzickus, jburke, llim, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 08:55:16 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:
Attachments:
Description Flags
Backport of linux-2.6.18-xen.hg c/s 214 none

Description Chris Lalancette 2009-03-17 00:44:01 UTC
Created attachment 335467 [details]
Backport of linux-2.6.18-xen.hg c/s 214

Description of problem:
I've noticed for quite a while now that every time you boot a i386 PV guest, you
get a serial console output from the hypervisor along the lines of:

(XEN) mm.c:3335:d1 ptwr_emulate: fixing up invalid PAE PTE 00000000d6d8f025

I finally decided to track this down.  What's happening is that early on in the boot of a guest, it's setting up the fixmaps.  However, the fixmaps are updating the PTE in the wrong order; that is, it is first updating the high half of the PTE, followed by the low half, while the hypervisor expects it the other way around.  Now, the hypervisor actually has code to deal with this, so it's not a huge deal, but we really should do this right.  To that end, I'll attach a patch, which is a backport of upstream linux-2.6.18-xen.hg c/s 214.  This seems to fix the issue for me.

Comment 1 Chris Lalancette 2009-03-24 15:55:12 UTC
*** Bug 289861 has been marked as a duplicate of this bug. ***

Comment 2 Don Zickus 2009-04-16 18:39:42 UTC
in kernel-2.6.18-139.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so.  However feel free
to provide a comment indicating that this fix has been verified.

Comment 8 errata-xmlrpc 2009-09-02 08:55:16 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1243.html