Attempting to Get Xen FreeBSD Dom0 working

David P. Discher dpd at dpdtech.com
Wed Dec 3 19:35:16 UTC 2014




On Dec 3, 2014, at 10:43 AM, Roger Pau Monné <roger.pau at 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.

Thanks !


-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-xen/attachments/20141203/fd515cb6/attachment.sig>


More information about the freebsd-xen mailing list