Date: Wed, 3 Dec 2014 20:55:45 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: "David P. Discher" <dpd@dpdtech.com> Cc: freebsd-xen@freebsd.org Subject: Re: Attempting to Get Xen FreeBSD Dom0 working Message-ID: <547F6AC1.9060709@citrix.com> In-Reply-To: <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <DCB954B5-0E45-4DE6-AAC4-C5ACF7FD90A7@dpdtech.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
El 03/12/14 a les 20.35, David P. Discher ha escrit: > > > > On Dec 3, 2014, at 10:43 AM, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Thanks for being able to test this so quickly, AFAICT this is a fallout >> from failing to initialize ACPI. I don't have a system with this >> specific ACPI configuration to trigger this, but I have the following >> patch, which _might_ solve your problem: >> >> https://people.freebsd.org/~royger/xen_acpi.patch >> >> Again, it should be applied on top of your already patched pvh_dom0_v8 >> branch (don't remove the previous patch). If this doesn't solve your >> problem I will try to find a similar box so I can reproduce the issue. >> >> Roger. > > > Well - that made it hang hard. > > > (XEN) PCI add device 0000:00:1a.0 > found-> vendor=0x8086, dev=0x3a38, revid=0x00 > domain=0, bus=0, slot=26, func=1 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=7 > map[20]: type I/O Port, range 32, base 0xc880, size 5, enabled > pcib0: allocated type 4 (0xc880-0xc89f) for rid 20 of pci0:0:26:1 > pcib0: matched entry for 0.26.INTB > pcib0: slot 26 INTB hardwired to IRQ 21 > xen: register IRQ#21 > (XEN) PCI add device 0000:00:1a.1 > found-> vendor=0x8086, dev=0x3a39, revid=0x00 > domain=0, bus=0, slot=26, func=2 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=d, irq=11 > map[20]: type I/O Port, range 32, base 0xc800, size 5, enabled > pcib0: allocated type 4 (0xc800-0xc81f) for rid 20 of pci0:0:26:2 > pcib0: matched entry for 0.26.INTD > pcib0: slot 26 INTD hardwired to IRQ 19 > (XEN) PCI add device 0000:00:1a.2 > found-> vendor=0x8086, dev=0x3a3c, > > > I’m between gigs right now, taking time off, so have some cycles to work on this. I’d love to dig into myself, but would need some guidance. I can also probably give you remote access to this particular box as well. > > I’m assuming there is one particular device that is throwing off the ACPI code - is it possible to black lists those address temporary ? It’s not clear to me what hardware it is stumbling over. Not sure what's going on now, could you post the full boot log with the provided patch applied and when it hangs switch to the Xen console (Ctrl+A 3 times), then press "i" and "Q" and also post the output? Also, add the following to your Xen command line: iommu=debug And if you can try to play with the iommu options, I would recommend also trying: iommu=debug,no-intremap Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?547F6AC1.9060709>