Re: [Xen-devel] pci-passthrough not working on 4.0.1-rc1-pre: mm.c:3847:d10 Bad page 00000000001beab4: ed=ffff830151210000(10), sd=ffff830151210000, caf=8000000000000002, taf=7400000000000001

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Hi Konrad,

Only tested it today, but the 2.6.33 kernel i used from your tree a couple of 
weeks ago also gives the bad page in xm dmesg.
The domU doesn't even boot, on console it reports the things below in this case 
it seems to go wrong on domain creation allready.
I think port 5 refers to pci device 5 i'm trying to passthrough, without the 
pci=['0000:05:00.0'] line the domain boots fine.

  Booting 'Debian GNU/Linux, vmlinuz-2.6.33'

lock
root            (hd1)
 Filesystem type is ext2fs, using whole disk
kernel          /boot/vmlinuz-2.6.33 root=/dev/xvda2 ro iommu=soft swiotlb=forc
e
initrd          /boot/initrd.img-2.6.33

close blk: backend=/local/domain/0/backend/vbd/21/51713 node=device/vbd/51713
close blk: backend=/local/domain/0/backend/vbd/21/51714 node=device/vbd/51714
port 5 still bound!


in xm dmesg:
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001
(XEN) mm.c:3847:d21 Bad page 000000000013ea83: ed=ffff8301f3a70000(21), 
sd=ffff8301f3a70000, caf=8000000000000002, taf=7400000000000001


i don't see anything in /var/log/xen/xend.log

dmesg shows the same again:
[68726.450116] pciback pci-21-0: allocated pdev @ 0xffff880026b08a40
[68726.452092] pciback pci-21-0: getting be setup
[68726.452784] pciback pci-21-0: exporting dom 0 bus 5 slot 0 func 0
[68726.455053] pciback 0000:05:00.0: registering for 21
[68726.455058] pciback 0000:05:00.0: device has been assigned to another 
domain! Over-writting the ownership, but beware.
[68726.456673] pciback pci-21-0: Publishing pci roots
[68726.457946] pciback pci-21-0: writing root 0 at 0000:05
[68726.478801] pciback pci-21-0: fe state changed 1
[68726.792308] blkback: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
[68726.807456] pciback pci-21-0: fe state changed 3
[68726.807735] pciback pci-21-0: Reading frontend config
[68726.808290] pciback pci-21-0: Attaching to frontend resources - gnt_ref=2046 
evtchn=5
[68726.808356] pciback pci-21-0: Attached!
[68726.808359] pciback pci-21-0: Connecting...
[68726.810435] pciback pci-21-0: Connected? 0
[68726.813098] pciback pci-21-0: fe state changed 4
[68726.816756] blkback: ring-ref 2045, event-channel 6, protocol 1 (x86_64-abi)
[68732.652963] frontend_changed: backend/vbd/21/51713: prepare for reconnect
[68732.660035] frontend_changed: backend/vbd/21/51714: prepare for reconnect


--

Sander




Monday, April 19, 2010, 8:28:39 PM, you wrote:

> On Mon, Apr 19, 2010 at 07:23:19PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>> 
>> Think i have found it, these domains where running old debian 2.6.26 
>> kernels, based on 2.6.18.
>> Perhaps something recently on pciback has broken compatibility with that ?

> I tested it at some point with SLES10 (which is XenLinux based), but I
> haven't done the testing recently. Let me try that and see if there was
> something new that got introduced.

> You did of course use 'iommu=soft' in the guest?



-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


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