From owner-freebsd-current@FreeBSD.ORG Mon Feb 5 10:33:24 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A07CB16A400 for ; Mon, 5 Feb 2007 10:33:23 +0000 (UTC) (envelope-from conrad.burger@mxit.com) Received: from smtp.swistgroup.com (smtp.swisttech.com [196.211.145.42]) by mx1.freebsd.org (Postfix) with ESMTP id BE7B113C494 for ; Mon, 5 Feb 2007 10:33:20 +0000 (UTC) (envelope-from conrad.burger@mxit.com) Received: from timon.swistgroup.com (unknown [172.16.1.30]) by smtp.swistgroup.com (Postfix) with ESMTP id E56B180FE4 for ; Mon, 5 Feb 2007 12:53:15 +0200 (SAST) Received: from mailnull by timon.swistgroup.com with local (Exim 4.52 (FreeBSD)) id 1HE1Dk-0003Vz-8p for current@freebsd.org; Mon, 05 Feb 2007 12:37:12 +0200 Received: from mail.swistgroup.com ([172.16.1.6] helo=hermes.swistgroup.com) by timon.swistgroup.com with esmtp (Exim 4.52 (FreeBSD)) id 1HE1Dk-0003VY-4z; Mon, 05 Feb 2007 12:37:12 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 5 Feb 2007 12:33:22 +0200 Message-ID: <45FBF1D2998C93429047415BE8091CC8303CDB@HERMES.swistgroup.com> In-Reply-To: <20070205093626.GA29196@cdnetworks.co.kr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [KERNEL PANIC] Assigning IP to BCE on CURRENT Thread-Index: AcdJCNyNdIWRlFzlTpmDv3mJIKA+pgABXRSg From: "Conrad Burger" To: X-disclaimer: Legalsentry Cc: dwhite@freebsd.org, current@freebsd.org Subject: RE: [KERNEL PANIC] Assigning IP to BCE on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 10:33:24 -0000 ******************************************************************* 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@gmail.com]=20 Sent: 05 February 2007 11:36 AM To: Conrad Burger Cc: current@freebsd.org; dwhite@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=3D DELL 1955 BLADE=20 > > OS Version=3D CURRENT i386(2007-02-01)=20 > >=20 > > When I assign an IP to one of the BCE interfaces on the system the = kernel > > PANICS. > >=20 > > >From KDB: > > --------------------------------------------------------------- > > Panic: invalid ife->ifm_date (0xa) in mii_phy_setmedia=20 > >=20 >=20 > I guess ukphy(4) was used to serve the PHY. > Would you post verbosed boot message? >=20 > > Cpuid =3D 0=20 > > KDB: enter:panic=20 > > [ thread pid 715 tid 100041] > > Stopped at kdb_enter + 0x2b:nop > > --------------------------------------------------------------- > >=20 > > I then type "panic" and it writes a vmcore dump. =20 > >=20 > > But when I analyze the vmcore using kgdb and run a "bt" it only = gives me the=20 > > backtrace of the kdb and shutdown.=20 > >=20 > > Is there a way to write a dump without kdb interfering? > >=20 > > 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.=20 > > Is this a known problem? >=20 >=20 >=20 > Hope this is what your requested. >=20 [...] > bce0: 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: on bce0 > gentbi0: 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=3D0 and hw.pci.enable_msix=3D0 to = /boot/loader.conf.=20 But the system still panics when I try to assign an IP to the interface. = The dmesg also shows that MSI is not used.=20 Anything else I can try?=20 Regards=20 Conrad=20