RE: [KERNEL PANIC] Assigning IP to BCE on CURRENT

*******************************************************************
Click here to view our e-mail legal notice: 
http://www.mxit.co.za/pdfs/mxit_legal.pdf or call: +27 21 888 5000
*******************************************************************


-----Original Message-----
From: Pyun YongHyeon [mailto:pyunyh_at_gmail.com] 
Sent: 05 February 2007 11:36 AM
To: Conrad Burger
Cc: current_at_freebsd.org; dwhite_at_freebsd.org
Subject: Re: [KERNEL PANIC] Assigning IP to BCE on CURRENT

On Mon, Feb 05, 2007 at 11:15:52AM +0200, Conrad Burger wrote:
 > *******************************************************************
 > Click here to view our e-mail legal notice:
 > http://www.mxit.co.za/pdfs/mxit_legal.pdf or call: +27 21 888 5000
 > *******************************************************************
 > > HARDWARE= DELL 1955 BLADE 
 >  > OS Version= CURRENT i386(2007-02-01) 
 >  > 
 >  > When I assign an IP to one of the BCE interfaces on the system the kernel
 >  > PANICS.
 >  > 
 >  > >From KDB:
 >  > ---------------------------------------------------------------
 >  > Panic: invalid ife->ifm_date (0xa) in mii_phy_setmedia 
 >  > 
 > 
 > I guess ukphy(4) was used to serve the PHY.
 > Would you post verbosed boot message?
 > 
 >  > Cpuid = 0 
 >  > KDB: enter:panic 
 >  > [ thread pid 715 tid 100041]
 >  > Stopped at kdb_enter + 0x2b:nop
 >  > ---------------------------------------------------------------
 >  > 
 >  > I then type "panic" and it writes a vmcore dump.  
 >  > 
 >  > But when I analyze the vmcore using kgdb and run a "bt" it only gives me
the 
 >  > backtrace of the kdb and shutdown. 
 >  > 
 >  > Is there a way to write a dump without kdb interfering?
 >  > 
 >  > Another thing, I tried to install CURRENT-snapshot-2007-01(AMD64), but
after
 > it
 >  > boots from the USB DVDROM. Sysinstall cannot access the USB DVDROM. 
 >  > Is this a known problem?
 > 
 > 
 > 
 > Hope this is what your requested.
 > 

[...]

 > bce0: <Broadcom NetXtreme II BCM5708S 1000Base-T (B2), v0.9.6> mem
0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci6
 > bce0: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0xf4000000
 > bce0: attempting to allocate 1 MSI vectors (1 supported)
 > bce0: using IRQ 256 for MSI
 > bce0: ASIC ID 0x57081021; Revision (B2); PCI-X 64-bit 133MHz
 > miibus0: <MII bus> on bce0
 > gentbi0: <Generic ten-bit interface> PHY 2 on miibus0
 > gentbi0: OUI 0x0050ef, model 0x0015, rev. 1
 > gentbi0:  1000baseSX, 1000baseSX-FDX, auto
 > bce0: bpf attached
 > bce0: Ethernet address: 00:15:c5:fc:fa:5f
 > bce0: [MPSAFE]

[...]

You're using generic TBI so I've CCed to dwhite.
Does this hardware really have SERDES PHY?(Device probe message
indicates 1000baseT, copper interface.)

How about disabling MSI/MSI-X?(hw.pci.enable_msi, hw.pci.enable_msix)

-------------------------------------------------------------------------

I have added hw.pci.enable_msi=0 and hw.pci.enable_msix=0 to /boot/loader.conf. 

But the system still panics when I try to assign an IP to the interface. 
The dmesg also shows that MSI is not used. 

Anything else I can try? 

Regards 
Conrad