On Wed, 2007-10-31 at 18:00 +0900, Simon Horman wrote:
> I've been unable to reproduce this problem on my RX2620 with the default
> config (which includes the E1000 driver), so unfortunately I think you
> will have to do some testing for me. Hopefully this won't take too many
> round trips.
>
> Below is a rather long patch which does two things:
[snip]
>
> (XEN) EFI memory fault addr=0xe00000407fff0010 kr2=0x020202020c020202
>
> If you could send me the boot log, or at the very least the lines that
> look like the one above, that should tell me something interesting.
> Your kernel config may also be interesting if it deviates from the
> default config significantly.
Hi Simon,
Well, unfortunately, I didn't see any of those and it fails the same
way with the patch. I am using the default build config. I also tried
testing on an rx2600 to see if I could figure out how to make it fail,
(un)fortunately it failed right away. Something seems wrong with SAL
calls on that system, so it never even finds any I/O devices. I'm
attaching the broken boot log and a good boot log without this series
applied for comparison. The rx2600 is running system firmware 2.31 (the
latest available) in cause you have one sitting around to test with.
On the rx6600, the failing address falls within a memory mapped I/O
range with runtime mappings in the EFI MDT. As a test, I used the old
uncached offset for these mappings, and that does allow the rx6600 to
boot to dom0. BTW, there are a lot of build warnings introduced by the
header changes that need to get cleaned up. Let me know if you can
reproduce either of these or send me more test cases to try. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
good.txt
Description: Text document
bad.txt
Description: Text document
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home