On Mon, Nov 16, 2009 at 03:38:26PM -0500, John Baldwin wrote:
> ...
> > Here's the tail end of diff -u pciconf.{6,7}:
> >
> > ...
> > -i...@pci2:3:0: class=0x028000 card=0x27218086 chip=0x42208086 rev=0x05
> hdr=0x00
> > +i...@pci0:2:3:0: class=0x028000 card=0x27218086 chip=0x42208086
> rev=0x05 hdr=0x00
> > vendor = 'Intel Corporation'
> > - device = 'MPCI3B driverIntel PRO/Wireless 2200BG'
> > + device = 'driverIntel PRO/Wireless 2200BG (MPCI3B)'
> > class = network
> > -pc...@pci2:12:0: class=0x060400 card=0x00000000 chip=0x00221011
> rev=0x04 hdr=0x01
> > +pc...@pci0:2:12:0: class=0x060400 card=0x00000000 chip=0x00221011
> rev=0x04 hdr=0x01
> > vendor = 'Digital Equipment Corporation'
> > - device = '21150-AA PCI to PCI Bridge'
> > + device = 'PCI-PCI Bridge (DC21150-AA)'
> > class = bridge
> > subclass = PCI-PCI
> > -...@pci3:1:0: class=0x020000 card=0x905510b7 chip=0x905510b7 rev=0x30
> hdr=0x00
> > - vendor = '3COM Corp, Networking Division'
> > - device = '3C905-TX Fast Etherlink 10/100 PCI TX NIC'
> > - class = network
> > - subclass = ethernet
> > ...
> > pcib3: memory decode 0xfa000000-0xfbffffff
> > -pcib3: prefetched decode 0xfff00000-0xfffff
> > -ACPI: Found matching pin for 3.5.INTA at func 0: 11
> > -ACPI: Found matching pin for 3.1.INTA at func 0: 11
> > -ACPI: Found matching pin for 3.2.INTA at func 0: 11
> > -ACPI: Found matching pin for 3.7.INTA at func 0: 11
> > -ACPI: Found matching pin for 3.8.INTA at func 0: 11
> > +pcib3: no prefetched decode
>
> In this case, newer message is just more correct. Notice that in the old
> printf the ending address is less than the starting address for the prefetch
> range. 7 is just smart enough to print this out more correctly. I do wonder
> if 7 does better if you disable ACPI? I'm curious if ACPI somehow thinks
> that the PCI device is not enabled. Presumably it would not have made it
> this far though if that were the case.OK; I haven't yet tried disabling ACPI. > Can you do something like 'pciconf -r > pci0:3:1:0 0x0:0x40' under a working (6) and broken (7+) kernel with the > docking station attached? Can do, thanks! So, first, running: FreeBSD g1-108.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #700 r199014: Sat Nov 7 04:28:00 PST 2009 [email protected]:/common/S1/obj/usr/src/sys/CANARY i386 I issued: sudo pciconf -r pci2:12:0 0x0:0x40 sudo pciconf -r pci3:1:0 0x0:0x40 (The first was the address of the PCI-PCI bridge; the second, that of the xl1 NIC.) Result: 00221011 02900107 06040004 00012008 00000000 00000000 20030302 2280f1f1 fbf0fa00 0001fff1 00000000 00000000 00000000 000000dc 00000000 02060000 02000000 905510b7 02100117 02000030 00002008 0000fc81 fafffc00 00000000 00000000 00000000 00000000 00000000 905510b7 fb000000 000000dc 00000000 0a0a010b 00000000 Then, running: FreeBSD g1-110.catwhisker.org 7.2-STABLE FreeBSD 7.2-STABLE #9 r199319: Mon Nov 16 06:04:38 PST 2009 [email protected]:/common/S2/obj/usr/src/sys/CANARY i386 I first tried the same commands as above, and got: 00221011 82900107 06040004 00012008 00000000 00000000 20030302 2280f1f1 fbf0fa00 0001fff1 00000000 00000000 00000000 000000dc 00000000 06060000 02000000 pciconf: ioctl(PCIOCREAD): Operation not supported by device Then I realized that the designation of the PCI-PCI bridge was different under stable/7 than it was under stable/6, so I tried: sudo pciconf -r pci0:2:12:0 0x0:0x40 sudo pciconf -r pci0:3:1:0 0x0:0x40 and got: 00221011 82900107 06040004 00012008 00000000 00000000 20030302 2280f1f1 fbf0fa00 0001fff1 00000000 00000000 00000000 000000dc 00000000 06060000 02000000 pciconf: ioctl(PCIOCREAD): Operation not supported by device Was that useful? It appears that "pci2:12:0 0x0:0x40" looks quite a bit like "pci0:2:12:0 0x0:0x40". Coincidence? Aliases? Peace, david -- David H. Wolfskill [email protected] Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpF8BQnEw99L.pgp
Description: PGP signature
