From owner-freebsd-current@FreeBSD.ORG Tue Jun 10 05:09:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6757437B401 for ; Tue, 10 Jun 2003 05:09:13 -0700 (PDT) Received: from yori.schoko.org (yori.schoko.org [62.109.128.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E57B43FBF for ; Tue, 10 Jun 2003 05:09:12 -0700 (PDT) (envelope-from nick@schoko.org) Received: from yori.schoko.org (nick@localhost [127.0.0.1]) by yori.schoko.org (8.12.9/8.12.9) with ESMTP id h5AC8tVF037375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Jun 2003 14:08:55 +0200 (CEST) (envelope-from nick@yori.schoko.org) Received: (from nick@localhost) by yori.schoko.org (8.12.9/8.12.9/Submit) id h5AC8sIr037180; Tue, 10 Jun 2003 14:08:54 +0200 (CEST) Date: Tue, 10 Jun 2003 14:08:54 +0200 From: Markus Wennrich To: Paul Richards Message-ID: <20030610120854.GX21814@yori.schoko.org> References: <20030603210021.GC843@speedy.unibe.ch> <1054591160.1641.17.camel@cf.freebsd-services.com> <20030603221716.GD843@speedy.unibe.ch> <1054594939.1641.52.camel@cf.freebsd-services.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <1054594939.1641.52.camel@cf.freebsd-services.com> User-Agent: Mutt/1.5.4i cc: Tobias Roth cc: current@freebsd.org Subject: Re: fxp0: device timeout with 5.1BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 10 Jun 2003 12:09:16 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 03, 2003 at 12:02:20AM +0100, Paul Richards wrote: > > > > fxp0: device timeout > > > I get these as well. Is it on irq9 by any chance, along with acpi0 ? > > > > No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are > > set to 11 (factory default). ACPI is disabled. > > Ok, well that's a useful data point (for me anyway) since it means > there's a problem with fxp losing interrupts that's not related to some > other ACPI problems I've experienced, suggesting that it's therefore a > fxp driver problem. I have the same problem here with a freshly cvsupped 5.1-CURRENT. The machine has two fxp-NICs and I get device timeouts with both of them (with acpi enabled or disabled, both the same, no change). See attached dmesg. Markus -- Why are they called buildings, when they're already finished? Shouldn't they be called builts? --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.no-acpi" Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #4: Tue Jun 10 12:55:22 CEST 2003 root@freebsd5.schoko.org:/usr/src/sys/i386/compile/MYKERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc04ae000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 547179019 Hz CPU: Pentium III/Pentium III Xeon/Celeron (547.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 1610612736 (1536 MB) avail memory = 1561681920 (1489 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00fdf00 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci_cfgintr: 0:12 INTA BIOS irq 11 pci_cfgintr: 0:12 INTA BIOS irq 11 pci_cfgintr: 0:14 INTA BIOS irq 10 pci_cfgintr: 0:18 INTD BIOS irq 10 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 15.0 on pci1 pci2: on pcib2 pcib3: at device 4.0 on pci2 pci3: on pcib3 pci_cfgintr: 0:1 INTA routed to irq 3 pcib1: slot 15 INTB is routed to irq 3 pcib2: slot 4 INTB is routed to irq 3 pcib3: slot 5 INTA is routed to irq 3 fxp0: port 0x3000-0x303f mem 0xf4200000-0xf42fffff,0xf4300000-0xf4300fff irq 3 at device 5.0 on pci3 fxp0: Ethernet address 00:d0:b7:20:97:72 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0 aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs fxp1: port 0x2800-0x283f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0 fxp1: Ethernet address 00:90:27:6a:51:54 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 18.0 on pci0 isa0: on isab0 atapci0: port 0x2860-0x286f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x2840-0x285f irq 10 at device 18.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 18.3 (no driver attached) pci0: at device 20.0 (no driver attached) orm0: