call for testing: MSI for msk(4)

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

call for testing: MSI for msk(4)

Jeremie Courreges-Anglas-2
Hi,

I've been using msk(4) with MSI on my laptop since a few days, with no
apparent problem.

mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13, Yukon-2 FE+ rev. A0 (0x0): msi
msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0

Other systems all seem to use MSI, but it would be cool if people with
different chips could test it.

--
Jérémie Courrèges-Anglas
PGP Key Fingerprint: 61DB D9A0 00A4 67CF 2A90  8961 6191 8FBF 06A1 1494

Index: if_msk.c
===================================================================
RCS file: /cvs/src/sys/dev/pci/if_msk.c,v
retrieving revision 1.98
diff -u -p -r1.98 if_msk.c
--- if_msk.c 17 Mar 2013 10:56:23 -0000 1.98
+++ if_msk.c 13 May 2013 01:53:00 -0000
@@ -1147,7 +1147,7 @@ mskc_attach(struct device *parent, struc
  DPRINTFN(2, ("mskc_attach: allocate interrupt\n"));
 
  /* Allocate interrupt */
- if (pci_intr_map(pa, &ih)) {
+ if (pci_intr_map_msi(pa, &ih) && pci_intr_map(pa, &ih)) {
  printf(": couldn't map interrupt\n");
  goto fail_1;
  }

Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Martin Pieuchot-2
On 16/05/13(Thu) 23:55, Jérémie Courrèges-Anglas wrote:

> Hi,
>
> I've been using msk(4) with MSI on my laptop since a few days, with no
> apparent problem.
>
> mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13, Yukon-2 FE+ rev. A0 (0x0): msi
> msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
>
> Other systems all seem to use MSI, but it would be cool if people with
> different chips could test it.
>
> --
> Jérémie Courrèges-Anglas
> PGP Key Fingerprint: 61DB D9A0 00A4 67CF 2A90  8961 6191 8FBF 06A1 1494
>
> Index: if_msk.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/if_msk.c,v
> retrieving revision 1.98
> diff -u -p -r1.98 if_msk.c
> --- if_msk.c 17 Mar 2013 10:56:23 -0000 1.98
> +++ if_msk.c 13 May 2013 01:53:00 -0000
> @@ -1147,7 +1147,7 @@ mskc_attach(struct device *parent, struc
>   DPRINTFN(2, ("mskc_attach: allocate interrupt\n"));
>  
>   /* Allocate interrupt */
> - if (pci_intr_map(pa, &ih)) {
> + if (pci_intr_map_msi(pa, &ih) && pci_intr_map(pa, &ih)) {
>   printf(": couldn't map interrupt\n");
>   goto fail_1;
>   }
>

Works for me with:

mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
FE rev. A1 (0x1): msi
msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3

I'd like to commit it, any ok?

Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Mark Kettenis
> Date: Tue, 21 May 2013 18:46:23 +0200
> From: Martin Pieuchot <[hidden email]>
>
> On 16/05/13(Thu) 23:55, Jérémie Courrèges-Anglas wrote:
> > Hi,
> >
> > I've been using msk(4) with MSI on my laptop since a few days, with no
> > apparent problem.
> >
> > mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13, Yukon-2 FE+ rev. A0 (0x0): msi
> > msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> > eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
> >
> > Other systems all seem to use MSI, but it would be cool if people with
> > different chips could test it.
> >
> > --
> > Jérémie Courrèges-Anglas
> > PGP Key Fingerprint: 61DB D9A0 00A4 67CF 2A90  8961 6191 8FBF 06A1 1494
> >
> > Index: if_msk.c
> > ===================================================================
> > RCS file: /cvs/src/sys/dev/pci/if_msk.c,v
> > retrieving revision 1.98
> > diff -u -p -r1.98 if_msk.c
> > --- if_msk.c 17 Mar 2013 10:56:23 -0000 1.98
> > +++ if_msk.c 13 May 2013 01:53:00 -0000
> > @@ -1147,7 +1147,7 @@ mskc_attach(struct device *parent, struc
> >   DPRINTFN(2, ("mskc_attach: allocate interrupt\n"));
> >  
> >   /* Allocate interrupt */
> > - if (pci_intr_map(pa, &ih)) {
> > + if (pci_intr_map_msi(pa, &ih) && pci_intr_map(pa, &ih)) {
> >   printf(": couldn't map interrupt\n");
> >   goto fail_1;
> >   }
> >
>
> Works for me with:
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
> FE rev. A1 (0x1): msi
> msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
> eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3
>
> I'd like to commit it, any ok?

Not so quick.  The Marvell Yukon-2 is a strong contender for the
"buggiest Ethernet chipset family ever" award.  I have very little
confidence that MSI actually works on all devices.  So this needs to
be tested on more devices than just the Fast Ethernet chips.  And
perhaps we need to look at the Linux driver to see if/how they support
MSI for these chips.

Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Brad Smith-14
In reply to this post by Jeremie Courreges-Anglas-2
On 16/05/13 5:55 PM, Jérémie Courrèges-Anglas wrote:

> Hi,
>
> I've been using msk(4) with MSI on my laptop since a few days, with no
> apparent problem.
>
> mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13, Yukon-2 FE+ rev. A0 (0x0): msi
> msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
>
> Other systems all seem to use MSI, but it would be cool if people with
> different chips could test it.

Any other msk(4) users? It has also been tested with EC 8052/EC Ultra
8058 controllers and working. I don't see any indication of any issues
or errata regarding MSI operation in either of the FreeBSD or Linux
drivers.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Brad Smith-14
On 31/12/13 12:06 AM, Brad Smith wrote:

> On 16/05/13 5:55 PM, Jérémie Courrèges-Anglas wrote:
>> Hi,
>>
>> I've been using msk(4) with MSI on my laptop since a few days, with no
>> apparent problem.
>>
>> mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13,
>> Yukon-2 FE+ rev. A0 (0x0): msi
>> msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
>> eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
>>
>> Other systems all seem to use MSI, but it would be cool if people with
>> different chips could test it.
>
> Any other msk(4) users? It has also been tested with EC 8052/EC Ultra
> 8058 controllers and working. I don't see any indication of any issues
> or errata regarding MSI operation in either of the FreeBSD or Linux
> drivers.

Fast Ethernet controller..

mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
FE rev. A1 (0x1): msi
msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3

Gigabit controllers..

mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2
EC Ultra rev. B0 (0x3): msi
msk0 at mskc0 port A: address 00:1b:63:ad:0b:ee
eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1

mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x20, Yukon-2
EC rev. A3 (0x2): msi
msk0 at mskc0 port A: address 00:50:43:00:7b:46
eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2

mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8052" rev 0x21, Yukon-2
EC rev. A3 (0x2): msi
msk0 at mskc0 port A: address 00:18:f3:6c:44:da
eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2


At this point I'd like to see this commited for wider spread testng
and if anything does come up as usual it can be reverted.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Martin Pieuchot-2
On 23/09/14(Tue) 13:58, Brad Smith wrote:

> On 31/12/13 12:06 AM, Brad Smith wrote:
> >On 16/05/13 5:55 PM, Jérémie Courrèges-Anglas wrote:
> >>Hi,
> >>
> >>I've been using msk(4) with MSI on my laptop since a few days, with no
> >>apparent problem.
> >>
> >>mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13,
> >>Yukon-2 FE+ rev. A0 (0x0): msi
> >>msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> >>eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
> >>
> >>Other systems all seem to use MSI, but it would be cool if people with
> >>different chips could test it.
> >
> >Any other msk(4) users? It has also been tested with EC 8052/EC Ultra
> >8058 controllers and working. I don't see any indication of any issues
> >or errata regarding MSI operation in either of the FreeBSD or Linux
> >drivers.
>
> Fast Ethernet controller..
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
> FE rev. A1 (0x1): msi
> msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
> eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3
>
> Gigabit controllers..
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2 EC
> Ultra rev. B0 (0x3): msi
> msk0 at mskc0 port A: address 00:1b:63:ad:0b:ee
> eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1
>
> mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x20, Yukon-2 EC
> rev. A3 (0x2): msi
> msk0 at mskc0 port A: address 00:50:43:00:7b:46
> eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8052" rev 0x21, Yukon-2
> EC rev. A3 (0x2): msi
> msk0 at mskc0 port A: address 00:18:f3:6c:44:da
> eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
>
>
> At this point I'd like to see this commited for wider spread testng
> and if anything does come up as usual it can be reverted.

I agree.

Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Ralf Horstmann-2
* Martin Pieuchot <[hidden email]> [2014-09-23 22:20]:

> On 23/09/14(Tue) 13:58, Brad Smith wrote:
> > On 31/12/13 12:06 AM, Brad Smith wrote:
> > >On 16/05/13 5:55 PM, Jérémie Courrèges-Anglas wrote:
> > >>Hi,
> > >>
> > >>I've been using msk(4) with MSI on my laptop since a few days, with no
> > >>apparent problem.
> > >>
> > >>mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13,
> > >>Yukon-2 FE+ rev. A0 (0x0): msi
> > >>msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> > >>eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
> > >>
> > >>Other systems all seem to use MSI, but it would be cool if people with
> > >>different chips could test it.
> > >
> > >Any other msk(4) users? It has also been tested with EC 8052/EC Ultra
> > >8058 controllers and working. I don't see any indication of any issues
> > >or errata regarding MSI operation in either of the FreeBSD or Linux
> > >drivers.
> >
> > Fast Ethernet controller..
> >
> > mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
> > FE rev. A1 (0x1): msi
> > msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
> > eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3
> >
> > Gigabit controllers..
> >
> > mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2 EC
> > Ultra rev. B0 (0x3): msi
> > msk0 at mskc0 port A: address 00:1b:63:ad:0b:ee
> > eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1
> >
> > mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x20, Yukon-2 EC
> > rev. A3 (0x2): msi
> > msk0 at mskc0 port A: address 00:50:43:00:7b:46
> > eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
> >
> > mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8052" rev 0x21, Yukon-2
> > EC rev. A3 (0x2): msi
> > msk0 at mskc0 port A: address 00:18:f3:6c:44:da
> > eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
> >
> >
> > At this point I'd like to see this commited for wider spread testng
> > and if anything does come up as usual it can be reverted.
>
> I agree.

Another Gigabit controller that works so far:

mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8055" rev 0x12, Yukon-2 EC Ultra rev. A1 (0x2): msi
msk0 at mskc0 port A: address 00:17:42:41:a8:2d
eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1

Cheers,
Ralf


Reply | Threaded
Open this post in threaded view
|

Re: call for testing: MSI for msk(4)

Theo Buehler
In reply to this post by Brad Smith-14
On Tue, Sep 23, 2014 at 01:58:59PM -0400, Brad Smith wrote:

> On 31/12/13 12:06 AM, Brad Smith wrote:
> >On 16/05/13 5:55 PM, Jérémie Courrèges-Anglas wrote:
> >>Hi,
> >>
> >>I've been using msk(4) with MSI on my laptop since a few days, with no
> >>apparent problem.
> >>
> >>mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8040" rev 0x13,
> >>Yukon-2 FE+ rev. A0 (0x0): msi
> >>msk0 at mskc0 port A: address 00:24:54:xx:xx:xx
> >>eephy0 at msk0 phy 0: 88E3016 10/100 PHY, rev. 0
> >>
> >>Other systems all seem to use MSI, but it would be cool if people with
> >>different chips could test it.
> >
> >Any other msk(4) users? It has also been tested with EC 8052/EC Ultra
> >8058 controllers and working. I don't see any indication of any issues
> >or errata regarding MSI operation in either of the FreeBSD or Linux
> >drivers.
>
> Fast Ethernet controller..
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8036" rev 0x16, Yukon-2
> FE rev. A1 (0x1): msi
> msk0 at mskc0 port A: address 00:13:a9:fa:5a:52
> eephy0 at msk0 phy 0: 88E3082 10/100 PHY, rev. 3
>
> Gigabit controllers..
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2 EC
> Ultra rev. B0 (0x3): msi
> msk0 at mskc0 port A: address 00:1b:63:ad:0b:ee
> eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1
>
> mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x20, Yukon-2 EC
> rev. A3 (0x2): msi
> msk0 at mskc0 port A: address 00:50:43:00:7b:46
> eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
>
> mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8052" rev 0x21, Yukon-2
> EC rev. A3 (0x2): msi
> msk0 at mskc0 port A: address 00:18:f3:6c:44:da
> eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
>
>
> At this point I'd like to see this commited for wider spread testng
> and if anything does come up as usual it can be reverted.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>


My card

mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22, Yukon-2 EC rev. A3 (0x2): msi
msk0 at mskc0 port A: address 00:19:e3:38:6c:56
eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2

doesn't seem to like this change.  Whenever I try to fetch a large file
with ftp, connectivity is lost after a few moments and I get the
following console message:

Oct  3 07:04:47 miraculix /bsd: msk0: watchdog timeout
Oct  3 07:06:41 miraculix /bsd: msk0: watchdog timeout
Oct  3 07:08:36 miraculix /bsd: msk0: watchdog timeout
Oct  3 07:20:46 miraculix /bsd: msk0: watchdog timeout
Oct  3 07:21:49 miraculix /bsd: msk0: watchdog timeout

This message first appeared when I was using a kernel including this
change and it doesn't show up when I revert if_msk.c to revision 1.106.

Both the GENERIC and GENERIC.MP kernels from the latest snapshot show
this behavior.  The dmesg of GENERIC is attached, as well as a pcidump.

In case this is of importance, I use a trunk failover configuration with
msk as master and athn as fallback.

# pcidump -v
Domain /dev/pci0:
 0:0:0: Intel 82945GM Host
        0x0000: Vendor ID: 8086 Product ID: 27a0
        0x0004: Command: 0006 Status: 2090
        0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 03
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
        0x00e0: Capability 0x09: Vendor Specific
 0:2:0: Intel 82945GM Video
        0x0000: Vendor ID: 8086 Product ID: 27a2
        0x0004: Command: 0007 Status: 0090
        0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 03
        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR mem 32bit addr: 0xb0380000/0x00080000
        0x0014: BAR io addr: 0x000020e0/0x0008
        0x0018: BAR mem prefetchable 32bit addr: 0xa0000000/0x10000000
        0x001c: BAR mem 32bit addr: 0xb0400000/0x00040000
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
        0x0090: Capability 0x05: Message Signaled Interrupts (MSI)
        0x00d0: Capability 0x01: Power Management
 0:2:1: Intel 82945GM Video
        0x0000: Vendor ID: 8086 Product ID: 27a6
        0x0004: Command: 0007 Status: 0090
        0x0008: Class: 03 Subclass: 80 Interface: 00 Revision: 03
        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR mem 32bit addr: 0xb0300000/0x00080000
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
        0x00d0: Capability 0x01: Power Management
 0:7:0: Intel unknown
        0x0000: Vendor ID: 8086 Product ID: 27a3
        0x0004: Command: 0002 Status: 00b0
        0x0008: Class: 11 Subclass: 01 Interface: 00 Revision: 03
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR mem 32bit addr: 0xb0444000/0x00001000
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 0000 Product ID: 0000
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
        0x00dc: Capability 0x01: Power Management
 0:27:0: Intel 82801GB HD Audio
        0x0000: Vendor ID: 8086 Product ID: 27d8
        0x0004: Command: 0006 Status: 0010
        0x0008: Class: 04 Subclass: 03 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 40
        0x0010: BAR mem 64bit addr: 0x00000000b0440000/0x00004000
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8384 Product ID: 7680
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
        0x0050: Capability 0x01: Power Management
        0x0060: Capability 0x05: Message Signaled Interrupts (MSI)
        0x0070: Capability 0x10: PCI Express
 0:28:0: Intel 82801GB PCIE
        0x0000: Vendor ID: 8086 Product ID: 27d0
        0x0004: Command: 0007 Status: 0010
        0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 40
        0x0010: 00000000
        0x0014: 00000000
        0x0018: Primary Bus: 0 Secondary Bus: 1 Subordinate Bus: 1
                Secondary Latency Timer: 00
        0x001c: I/O Base: 10 I/O Limit: 10 Secondary Status: 2000
        0x0020: Memory Base: b020 Memory Limit: b020
        0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
        0x0028: Prefetch Memory Base Upper 32 Bits: ffffffff
        0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
        0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
        0x0038: Expansion ROM Base Address: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Bridge Control: 0000
        0x0040: Capability 0x10: PCI Express
                Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
        0x0080: Capability 0x05: Message Signaled Interrupts (MSI)
        0x0090: Capability 0x0d: PCI-PCI
        0x00a0: Capability 0x01: Power Management
 0:28:1: Intel 82801GB PCIE
        0x0000: Vendor ID: 8086 Product ID: 27d2
        0x0004: Command: 0007 Status: 0010
        0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 40
        0x0010: 00000000
        0x0014: 00000000
        0x0018: Primary Bus: 0 Secondary Bus: 2 Subordinate Bus: 2
                Secondary Latency Timer: 00
        0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 2000
        0x0020: Memory Base: b010 Memory Limit: b010
        0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
        0x0028: Prefetch Memory Base Upper 32 Bits: ffffffff
        0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
        0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
        0x0038: Expansion ROM Base Address: 00000000
        0x003c: Interrupt Pin: 02 Line: 0b Bridge Control: 0000
        0x0040: Capability 0x10: PCI Express
                Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
        0x0080: Capability 0x05: Message Signaled Interrupts (MSI)
        0x0090: Capability 0x0d: PCI-PCI
        0x00a0: Capability 0x01: Power Management
 0:29:0: Intel 82801GB USB
        0x0000: Vendor ID: 8086 Product ID: 27c8
        0x0004: Command: 0005 Status: 0280
        0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR io addr: 0x00002080/0x0020
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
 0:29:1: Intel 82801GB USB
        0x0000: Vendor ID: 8086 Product ID: 27c9
        0x0004: Command: 0005 Status: 0280
        0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR io addr: 0x00002060/0x0020
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 02 Line: 0b Min Gnt: 00 Max Lat: 00
 0:29:2: Intel 82801GB USB
        0x0000: Vendor ID: 8086 Product ID: 27ca
        0x0004: Command: 0005 Status: 0280
        0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR io addr: 0x00002040/0x0020
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 03 Line: 0b Min Gnt: 00 Max Lat: 00
 0:29:3: Intel 82801GB USB
        0x0000: Vendor ID: 8086 Product ID: 27cb
        0x0004: Command: 0005 Status: 0280
        0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR io addr: 0x00002020/0x0020
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 04 Line: 0b Min Gnt: 00 Max Lat: 00
 0:29:7: Intel 82801GB USB
        0x0000: Vendor ID: 8086 Product ID: 27cc
        0x0004: Command: 0006 Status: 0290
        0x0008: Class: 0c Subclass: 03 Interface: 20 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR mem 32bit addr: 0xb0445400/0x00000400
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
        0x0050: Capability 0x01: Power Management
        0x0058: Capability 0x0a: Debug Port
 0:30:0: Intel 82801BAM Hub-to-PCI
        0x0000: Vendor ID: 8086 Product ID: 2448
        0x0004: Command: 0007 Status: 0010
        0x0008: Class: 06 Subclass: 04 Interface: 01 Revision: e2
        0x000c: BIST: 00 Header Type: 01 Latency Timer: 00 Cache Line Size: 00
        0x0010: 00000000
        0x0014: 00000000
        0x0018: Primary Bus: 0 Secondary Bus: 3 Subordinate Bus: 3
                Secondary Latency Timer: 20
        0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 2280
        0x0020: Memory Base: b000 Memory Limit: b000
        0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
        0x0028: Prefetch Memory Base Upper 32 Bits: ffffffff
        0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
        0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
        0x0038: Expansion ROM Base Address: 00000000
        0x003c: Interrupt Pin: 00 Line: 00 Bridge Control: 0000
        0x0050: Capability 0x0d: PCI-PCI
 0:31:0: Intel 82801GBM LPC
        0x0000: Vendor ID: 8086 Product ID: 27b9
        0x0004: Command: 0007 Status: 0210
        0x0008: Class: 06 Subclass: 01 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
        0x00e0: Capability 0x09: Vendor Specific
 0:31:1: Intel 82801GB IDE
        0x0000: Vendor ID: 8086 Product ID: 27df
        0x0004: Command: 0005 Status: 0288
        0x0008: Class: 01 Subclass: 01 Interface: 8a Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR io addr: 0x000020d8/0x0008
        0x0014: BAR io addr: 0x000020f4/0x0004
        0x0018: BAR io addr: 0x000020d0/0x0008
        0x001c: BAR io addr: 0x000020f0/0x0004
        0x0020: BAR io addr: 0x000020b0/0x0010
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
 0:31:2: Intel 82801GBM SATA
        0x0000: Vendor ID: 8086 Product ID: 27c4
        0x0004: Command: 0007 Status: 02b0
        0x0008: Class: 01 Subclass: 01 Interface: 8f Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR io addr: 0x000020c8/0x0008
        0x0014: BAR io addr: 0x000020ec/0x0004
        0x0018: BAR io addr: 0x000020c0/0x0008
        0x001c: BAR io addr: 0x000020e8/0x0004
        0x0020: BAR io addr: 0x000020a0/0x0010
        0x0024: BAR mem 32bit addr: 0xb0445000/0x00000400
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 02 Line: 0b Min Gnt: 00 Max Lat: 00
        0x0070: Capability 0x01: Power Management
 0:31:3: Intel 82801GB SMBus
        0x0000: Vendor ID: 8086 Product ID: 27da
        0x0004: Command: 0001 Status: 0280
        0x0008: Class: 0c Subclass: 05 Interface: 00 Revision: 02
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
        0x0010: BAR empty (00000000)
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR io addr: 0x0000efa0/0x0020
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 8086 Product ID: 7270
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 02 Line: 0b Min Gnt: 00 Max Lat: 00
 1:0:0: Marvell Yukon 88E8053
        0x0000: Vendor ID: 11ab Product ID: 4362
        0x0004: Command: 0007 Status: 4018
        0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 22
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 40
        0x0010: BAR mem 64bit addr: 0x00000000b0200000/0x00004000
        0x0018: BAR io addr: 0x00001000/0x0100
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 1234 Product ID: 5678
        0x0030: Expansion ROM Base Address: fffe0000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
        0x0048: Capability 0x01: Power Management
        0x0050: Capability 0x03: Vital Product Data (VPD)
        0x005c: Capability 0x05: Message Signaled Interrupts (MSI)
        0x00e0: Capability 0x10: PCI Express
                Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
 2:0:0: Atheros AR5418
        0x0000: Vendor ID: 168c Product ID: 0024
        0x0004: Command: 0007 Status: 0010
        0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 01
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 40
        0x0010: BAR mem 64bit addr: 0x00000000b0100000/0x00010000
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 106b Product ID: 0087
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
        0x0040: Capability 0x01: Power Management
        0x0050: Capability 0x05: Message Signaled Interrupts (MSI)
        0x0060: Capability 0x10: PCI Express
                Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
        0x0090: Capability 0x11: Extended Message Signaled Interrupts (MSI-X)
 3:3:0: AT&T/Lucent FW322 1394
        0x0000: Vendor ID: 11c1 Product ID: 5811
        0x0004: Command: 0216 Status: 0290
        0x0008: Class: 0c Subclass: 00 Interface: 10 Revision: 61
        0x000c: BIST: 00 Header Type: 00 Latency Timer: f8 Cache Line Size: 10
        0x0010: BAR mem 32bit addr: 0xb0000000/0x00001000
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000000
        0x002c: Subsystem Vendor ID: 11c1 Product ID: 5811
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 0c Max Lat: 18
        0x0044: Capability 0x01: Power Management
$ dmesg
OpenBSD 5.6-current (GENERIC) #368: Tue Sep 30 13:45:55 MDT 2014
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 2634596352 (2512MB)
avail mem = 2555830272 (2437MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0000 (37 entries)
bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
bios0: Apple Inc. MacBook2,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.30 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf0000000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "15253732082930497" type 15253732284385612 oem "15253732284387396"
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1833, 1667, 1500, 1333, 1000 MHz
memory map conflict 0x9ef00000/0x100000
memory map conflict 0x9f000000/0x1000000
memory map conflict 0xf00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb0000/0x30000
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
intagp0 at vga1
agp0 at intagp0: aperture at 0xa0000000, size 0x10000000
inteldrm0 at vga1
drm0 at inteldrm0
drm: Setting output timings on SDVOB failed
inteldrm0: 1280x800
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and Frequency, rev 0x03) at pci0 dev 7 function 0 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Sigmatel STAC9220/1
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22, Yukon-2 EC rev. A3 (0x2): msi
msk0 at mskc0 port A: address 00:19:e3:38:6c:56
eephy0 at msk0 phy 0: 88E1111 Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
athn0 at pci2 dev 0 function 0 "Atheros AR5418" rev 0x01: apic 1 int 17
athn0: MAC AR5418 rev 2, RF AR5133 (2T3R), ROM rev 4, address 00:1b:63:02:1c:22
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 21
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 21
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci3 at ppb2 bus 3
"AT&T/Lucent FW322 1394" rev 0x61 at pci3 dev 3 function 0 not configured
pcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <MATSHITA, DVD-R UJ-857D, KBVB> ATAPI 5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using apic 1 int 19 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 1: <TOSHIBA MK1234GSX>
wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
wd0(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x02: apic 1 int 19
iic0 at ichiic0
iic0: addr 0x48 00=3d 01=00 02=4b 03=50 words 00=3d00 01=00ff 02=4b00 03=5000 04=ffff 05=ffff 06=ffff 07=ffff
spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
spdmem1 at iic0 addr 0x52: 512MB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000102
error: [drm:pid0:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000102
uhub5 at uhub0 port 1 "Apple, Inc. Keyboard Hub" rev 2.00/94.15 addr 2
uhidev0 at uhub5 port 2 configuration 1 interface 0 "Apple, Inc Apple Keyboard" rev 2.00/0.69 addr 3
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 5 key codes, country code 13
wskbd0 at ukbd0: console keyboard, using wsdisplay0
uhidev1 at uhub5 port 2 configuration 1 interface 1 "Apple, Inc Apple Keyboard" rev 2.00/0.69 addr 3
uhidev1: iclass 3/0
uhid0 at uhidev1: input=1, output=0, feature=0
uhidev2 at uhub5 port 3 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/43.01 addr 4
uhidev2: iclass 3/1
ums0 at uhidev2: 8 buttons, Z dir
wsmouse0 at ums0 mux 0
uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in iSight" rev 2.00/1.84 addr 5
video0 at uvideo0
uhidev3 at uhub1 port 2 configuration 1 interface 0 "Apple Computer Apple Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
uhidev3: iclass 3/1
ukbd1 at uhidev3: 8 variable keys, 5 key codes, country code 13
wskbd1 at ukbd1 mux 1
wskbd1: connecting to wsdisplay0
uhidev4 at uhub1 port 2 configuration 1 interface 1 "Apple Computer Apple Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
uhidev4: iclass 3/1, 5 report ids
ums1 at uhidev4 reportid 2: 3 buttons
wsmouse1 at ums1 mux 0
ums2 at uhidev4 reportid 5
ums2: mouse has no X report
uhidev5 at uhub1 port 2 configuration 1 interface 2 "Apple Computer Apple Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
uhidev5: iclass 3/0
uhid1 at uhidev5: input=1, output=0, feature=0
uhidev6 at uhub3 port 2 configuration 1 interface 0 "Apple Computer, Inc. IR Receiver" rev 2.00/1.10 addr 2
uhidev6: iclass 3/0, 38 report ids
uhid2 at uhidev6 reportid 36: input=4, output=0, feature=0
uhid3 at uhidev6 reportid 37: input=4, output=0, feature=0
uhid4 at uhidev6 reportid 38: input=4, output=0, feature=0
uhidev7 at uhub4 port 1 configuration 1 interface 0 "Apple Computer HID-proxy" rev 2.00/19.65 addr 2
uhidev7: iclass 3/1
ukbd2 at uhidev7: 8 variable keys, 6 key codes
wskbd2 at ukbd2 mux 1
wskbd2: connecting to wsdisplay0
uhidev8 at uhub4 port 1 configuration 1 interface 1 "Apple Computer HID-proxy" rev 2.00/19.65 addr 2
uhidev8: iclass 3/1
ums3 at uhidev8: 5 buttons
wsmouse2 at ums3 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
sd0 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 005> SCSI2 0/direct fixed
sd0: 114470MB, 512 bytes/sector, 234435953 sectors
root on sd0a (aee63bc24d6d3bf5.a) swap on sd0b dump on sd0b