trap 12: page fault while in kernel mode on 8.0-RELEASE (possibly bge(4) related)

Pyun YongHyeon pyunyh at gmail.com
Fri Feb 19 00:42:52 UTC 2010


On Thu, Feb 18, 2010 at 03:32:54PM -0800, Jeremy Chadwick wrote:
> On Fri, Feb 19, 2010 at 12:50:39AM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Feb 18, 2010 at 01:32:13PM -0800, Pyun YongHyeon wrote:
> > 
> > > > > dmesg output(only bge(4) related one).
> > > > 
> > > > dmesg from boot:
> > > > 
> > > > bge0: <HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100> mem 0xfdf70000-0xfdf7ffff irq 25 at device 2.0 on pci2
> > > > miibus0: <MII bus> on bge0
> > > > brgphy0: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus0
> > > > brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> > > > bge0: Ethernet address: 00:14:c2:3d:e5:52
> > > > bge0: [ITHREAD]
> > > > bge1: <HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100> mem 0xfdf60000-0xfdf6ffff irq 26 at device 2.1 on pci2
> > > > miibus1: <MII bus> on bge1
> > > > brgphy1: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus1
> > > > brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> > > > bge1: Ethernet address: 00:14:c2:3d:e5:51
> > > > bge1: [ITHREAD]
> > > > bge1: link state changed to UP
> > > > bge0: link state changed to UP
> > > > 
> > > > Nothing in dmesg before trap.
> > > > 
> > > 
> > > Is this PCI-X controller? It would be even better if you can post
> > 
> > This integrated controller (HP DL360-G4)
> > 
> > > bge(4) related dmesg output of verbosed boot and the output of
> >
> > ...
> > pci0:2:2:0: bad VPD cksum, remain 19
> > bge0: <HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100> mem 0xfdf70000-0xfdf7ffff irq 25 at device 2.0 on pci2
> > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfdf70000
> > bge0: CHIP ID 0x00002100; ASIC REV 0x02; CHIP REV 0x21; PCI-X
> > ...
> > pci0:2:2:1: bad VPD cksum, remain 19
> > bge1: <HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100> mem 0xfdf60000-0xfdf6ffff irq 26 at device 2.1 on pci2
> > bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfdf60000
> > bge1: CHIP ID 0x00002100; ASIC REV 0x02; CHIP REV 0x21; PCI-X
> 
> Are the "bad VPD checksum" messages somehow responsible for this?
> They're both related to the bge(4) interfaces:
> 
> > bge0 at pci0:2:2:0:        class=0x020000 card=0x00d00e11 chip=0x164814e4 rev=0x10 hdr=0x00
> > bge1 at pci0:2:2:1:        class=0x020000 card=0x00d00e11 chip=0x164814e4 rev=0x10 hdr=0x00
>  

Driver tries to read VPD from controller but it seems it failed to
fully parse the data. But it managed to get PN part so it
successfully extracted device name string from the controller.
I don't think this is related with driver instability though.


More information about the freebsd-stable mailing list