Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

[Tristan Gingold <Tristan.Gingold@xxxxxxxx>]

Le Mardi 11 Avril 2006 03:52, Isaku Yamahata a écrit :
> Thank you for testing.
>
> On Mon, Apr 10, 2006 at 03:52:52PM +0100, Tristan Gingold wrote:
> > Le Vendredi 07 Avril 2006 06:16, Isaku Yamahata a écrit :
> > > Hello.
> > > I attached the P2M/VP model patches take 4 for the change set
> > > 9492:2133fb78dba3cf6b6b88d1566fc5cc9de3039f43.
> > > Please comments/request/review.
> >
> > I am testing this on my FAME-C.
> > Currently it doesn't work: this is an infinite loop in an mpt driver.
> > I will check how it does handle DMA.
>
> It seems wrong dma address is used.
> My test environment is Tiger-2. Mpt driver is used.
> I encountered similar case before, but I don't remember clearly.
In fact I think it is due to the bug below.

> > BTW, I got message about bad mp address (on FAME and on Tiger-2).
> > Did you encounter them ?
>
> Is its address in I/O area?
> Some device drivers access I/O port to check its existance.
> (VGA, ATA, serial...) It might cause bad mpa.
> Stack trace will be printed. You get Linux address 0xa00...,
> then you can determine which device driver caused it.
Here is a trace:

(XEN) ACPI: Local APIC address c0000000fee00000
(XEN) ACPI: [APIC:0x07] ignored 120 entries of 128 found
(XEN) assign_domain_mmio_page: domain f000000007ff8a50 mpaddr 0xfec00000 size = 
0x0
(XEN) assign_domain_mmio_page: domain f000000007ff8a50 mpaddr 0xfae00000 size = 
0x0
(XEN) lookup_domain_mpa: bad mpa 0xfae00000 (> 0x20044000)
(XEN) lookup_domain_mpa: d 0xf000000007ff8a50 id 0 current 0xf000000004110000 
id 0
(XEN) 
(XEN) Call Trace:
(XEN)  [<f00000000408b400>] show_stack+0x80/0xa0
(XEN)                                 sp=f000000004117c00 bsp=f000000004110f00
(XEN)  [<f00000000404ddc0>] lookup_domain_mpa+0x170/0x240
(XEN)                                 sp=f000000004117dd0 bsp=f000000004110eb8
(XEN)  [<f000000004063c60>] translate_domain_pte+0xe0/0x210
(XEN)                                 sp=f000000004117dd0 bsp=f000000004110e78
(XEN)  [<f000000004069010>] vcpu_itc_d+0xb0/0x200
(XEN)                                 sp=f000000004117dd0 bsp=f000000004110e38
(XEN)  [<f00000000405c810>] ia64_hyperprivop+0x7b0/0x860
(XEN)                                 sp=f000000004117de0 bsp=f000000004110df0
(XEN)  [<f000000004063a60>] ia64_handle_break+0x190/0x2b0
(XEN)                                 sp=f000000004117e00 bsp=f000000004110da0
(XEN)  [<f000000004089fe0>] ia64_leave_kernel+0x0/0x310
(XEN)                                 sp=f000000004117e00 bsp=f000000004110da0
(XEN)  [<a000000100009090>] ???
(XEN)                                 sp=f000000004118000 bsp=f000000004110d80
(XEN)  [<a0000001000624e0>] ???
(XEN)                                 sp=f000000004118000 bsp=f000000004110d38
(XEN)  [<a0000001000624e0>] ???
(XEN)                                 sp=f000000004118000 bsp=f000000004110cf0
(XEN)  [<a0000001000624e0>] ???
(XEN)                                 sp=f000000004118000 bsp=f000000004110ca8
(XEN)  [<a0000001000624e0>] ???
(XEN)                                 sp=f000000004118000 bsp=f000000004110c60
(XEN) lookup_domain_mpa:1006

There is a problem with IOSAPIC.

Tristan.



_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel