From owner-freebsd-i386@FreeBSD.ORG Wed Jul 2 19:30:07 2008 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F00D1065779 for ; Wed, 2 Jul 2008 19:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5A8A68FC1C for ; Wed, 2 Jul 2008 19:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m62JU2wU076731 for ; Wed, 2 Jul 2008 19:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m62JU2Oa076728; Wed, 2 Jul 2008 19:30:02 GMT (envelope-from gnats) Resent-Date: Wed, 2 Jul 2008 19:30:02 GMT Resent-Message-Id: <200807021930.m62JU2Oa076728@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Francis Gendreau Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 835021065671 for ; Wed, 2 Jul 2008 19:25:10 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 70A748FC1D for ; Wed, 2 Jul 2008 19:25:10 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m62JPAnq094426 for ; Wed, 2 Jul 2008 19:25:10 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m62JPAlC094414; Wed, 2 Jul 2008 19:25:10 GMT (envelope-from nobody) Message-Id: <200807021925.m62JPAlC094414@www.freebsd.org> Date: Wed, 2 Jul 2008 19:25:10 GMT From: Francis Gendreau To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: i386/125195: fxp(4) driver failed to initialize device Intel 82801DB X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 19:30:07 -0000 >Number: 125195 >Category: i386 >Synopsis: fxp(4) driver failed to initialize device Intel 82801DB >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 02 19:30:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Francis Gendreau >Release: RELENG_&_) >Organization: >Environment: FreeBSD laptop 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:53 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/src/sys/GENERIC i386 >Description: Hi everyone. During the setup of my network's latest addition, an Asus M3000N M3N laptop, I encountered a severe problem regarding the fxp(4) driver. The system comes with an Intel 82801DB chipset that includes the 82801DB (ICH4) PRO/100 VM Network Connection. To enable the different devices, I load the ipw(4) and snd_ich(4). The devices work fine but I keep having the following message: ipw0: mem 0xff7fd000-0xff7fdfff irq4 at device 4.0 pci1 ipw0: Ethernet address: 00:04:23:71:77:46 ipw0: [ITHREAD] fxp0: port 0xcc00-0xcc3f mem 0xff7ff000-0xff7fffff irq 11 at device 8.0 on pci1 fxp0: fxp_miibus_readreg: timed out .. 31 times more ... fxp0: MII without any PHY! device_attach: fxp0 attach returned 6 pcm0: port 0xe000-0xe0ff,0xe100-0xe13f at device 31.5 on pci0 pcm0: [ITHREAD] pcm0: fxp0: port 0xcc00-0xcc3f mem 0xff7ff000-0xff7fffff irq 11 at device 8.0 on pci1 fxp0: fxp_miibus_readreg: timed out .. 31 times more ... fxp0: MII without any PHY! device_attach: fxp0 attach returned 6 I booted the system using the RELENG_6_3 disc1 and was having the same messages regarding the fxp(4) driver. Might it be possible that the driver is having trouble with this chipset or the device is broken on the system. Anyway, if anyone have a clue about how to fix this, I would really appreciate any information. Sincerely Francis Gendreau >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: