Mark wrote: > Alex Gor wrote: > > Full output is attached. > > > > Thanks you very much. > > > Oh, interesting.... > > > ffffff00100165c0 unix:die+10f () > ffffff00100166d0 unix:trap+1775 () > ffffff00100166e0 unix:cmntrap+12f () > ffffff0010016870 unix:atomic_cas_ulong+3 () > ffffff0010016910 unix:hati_pte_map+123 () > ffffff0010016990 unix:hati_load_common+15d () > ffffff0010016a50 unix:hat_devload+198 () > ffffff0010016aa0 npe:pcitool_map+de () > ffffff0010016b10 npe:pcitool_pciex_cfg_access+e3 () > ffffff0010016bf0 npe:pcitool_dev_reg_ops+185 () > ffffff0010016c70 npe:pci_common_ioctl+ce () > ffffff0010016d00 npe:npe_ioctl+77 () > ffffff0010016d40 genunix:cdev_ioctl+45 () > ffffff0010016d80 specfs:spec_ioctl+83 () > ffffff0010016e00 genunix:fop_ioctl+7b () > ffffff0010016f00 genunix:ioctl+18e () > ffffff0010016f10 unix:brand_sys_syscall+261 () > > I wonder if X has switch from xsvc to pcitool?
AFAIK, yes. I think Xorg 1.5 is using libpciaccess[1], and that library uses pcitool. The scanpci utility uses the same libpciaccess, and there had been quite a few problems [2] [3] [4] with PCIe, memory mapped config space and the switch to libpciaccess. IIRC, a workaround was added to Xorg 1.5 to limit the maximum pci bus that was scanned when searching video hardware, to work around the problem with the kernel's pcitool code accessing pcie configuration space for invalid pci busses. I think it was easier to add a workaround to Xorg, than to get in the kernel fix for pcitool [5]. 6799812 was fixed some months ago, and I think the next Xorg release 1.6 was integrated into b116. Maybe the workarounds for pcitool that had been added to Xorg 1.5 had been removed from Xorg 1.6 and it is now scanning all possible pci busses? [1] http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6752913 [2] http://defect.opensolaris.org/bz/show_bug.cgi?id=6100 [3] CR 6789879 [4] CR 6799812 [5] http://opensolaris.org/jive/thread.jspa?messageID=334459#334459 >It doesn't want to map the physical address fec00000. > pcitool_map+0xde(fec00000 > have a different code path in xsvc to handle memory > vs IO. I'll have to look at that again... Could there be a bios bug? Alex, can you try to dump the bios acpi tables for that machine, using the Intel ACPI table utility "iasl"? Attachment 4 of bug 5693 http://defect.opensolaris.org/bz/show_bug.cgi?id=5693#c9 contains a copy of the iasl utility. One file that gets dumped should have a name like "MCFG*.dat", can you post a hexdump of that file? od -x MCFG*.dat The output from prtconf -pv could also be interesting, especially all properties on the root pci node that have property names starting with "ecfg". -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
