On Thu, Apr 15, 2004 at 09:32:04AM +0300, Ruslan Ermilov wrote: > On Wed, Apr 14, 2004 at 11:11:22PM -0700, Crist J. Clark wrote: > > Ah, dc(4), everyone's favorite buggy NIC. I've got a system with > > a dc(4) that I am trying to move to 5-CURRENT from 5.2.1-R. Here's > > the info on the NIC, > > > > dc0_at_pci0:9:0: class=0x020000 card=0xf0022646 chip=0x000211ad rev=0x20 hdr=0x00 > > vendor = 'Lite-On Communications Inc' > > device = 'NGMC169B 10/100 Ethernet (NetGear FA310TX)' > > class = network > > subclass = ethernet > > > > It has been working alright in 5.2.1-R, but with CURRENT, I end up with, > > > > dc0: failed to force tx and rx to idle state > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > > > The 'failed to force tx and rx to idle state' are not new. I would get > > those at boot time with 5.2.1-R, but the 'watchdog timeout' is new. The > > NIC is no longer working at all. No traffic going in or out. > > > > I noticed that the src/sys/pci/if_dc* files had had some changes since > > 5.2.1-R and tried regressing just those, but it had no effect. Bummer, > > since it looked like 1.138 of if_dc.c was a good candidate for causing > > the trouble. Anyone else have this card and see this? Ideas about what > > may have changed? > > > > Some dmesg(8) output, > > > > dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xde000000-0xde0000ff irq 9 at device 9.0 on pci0 > > dc0: Bus reserved 0x100 bytes for rid 0x10 type 4 at 0xd800 > > dc0: Ethernet address: 00:c0:f0:5a:6c:0a > > miibus0: <MII bus> on dc0 > > ukphy0: <Generic IEEE 802.3u media interface> on miibus0 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > dc0: Ethernet address: 00:c0:f0:5a:6c:0a > > dc0: [GIANT-LOCKED] > > dc0: failed to force tx and rx to idle state > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > dc0: failed to force tx and rx to idle state > > dc0: watchdog timeout > > > My notebook doesn't assign a proper interrupt to dc(4) when I enable > ACPI. Since I don't know what your system is, assuming it's a > notebook, please try without ACPI. The system is not a notebook, and I don't think it is ACPI. ACPI has always refused to load on this system, BIOS 639kB/261120kB available memory acpi: bad RSDP checksum (155) Well, this could be a problem I suppose, but it has always been this way, and it's been running the 5.x branch fine up to 5.2.1-R. Here is the complete dmesg(8) for more info on what else the system has, Copyright (c) 1992-2004 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.2-CURRENT #0: Tue Apr 13 08:13:43 PDT 2004 cjc_at_vegeta.cjclark.org:/var/tmp/obj/usr/src/sys/VEGETA Preloaded elf kernel "/boot/kernel/kernel" at 0xc070b000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX> AMD Features=0x80000800<SYSCALL,3DNow!> real memory = 268435456 (256 MB) avail memory = 257191936 (245 MB) random: <entropy source, Software, Yarrow> K6-family MTRR support enabled (2 registers) cpu0 on motherboard npx0: [FAST] npx0: <math processor> on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Found $PIR table, 5 entries at 0xc00f0d00 pcib0: <AcerLabs M1541 (Aladdin-V) PCI host bridge> at pcibus 0 on motherboard pci0: <PCI bus> on pcib0 $PIR: 0:9 INTA routed to irq 9 $PIR: 0:10 INTA routed to irq 10 pcib1: <PCI-PCI bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 $PIR: 0:1 INTA routed to irq 9 pcib1: slot 0 INTA is routed to irq 9 pci1: <display, VGA> at device 0.0 (no driver attached) pci0: <bridge, PCI-unknown> at device 3.0 (no driver attached) isab0: <PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xde000000-0xde0000ff irq 9 at device 9.0 on pci0 dc0: Bus reserved 0x100 bytes for rid 0x10 type 4 at 0xd800 dc0: Ethernet address: 00:c0:f0:5a:6c:0a miibus0: <MII bus> on dc0 ukphy0: <Generic IEEE 802.3u media interface> on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:c0:f0:5a:6c:0a dc0: [GIANT-LOCKED] pci0: <serial bus, USB> at device 10.0 (no driver attached) atapci0: <AcerLabs Aladdin UDMA33 controller> port 0xd400-0xd40f at device 15.0 on pci0 atapci0: Bus reserved 0x10 bytes for rid 0x20 type 4 at 0xd400 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 orm0: <Option ROM> at iomem 0xc0000-0xc87ff on isa0 atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd0: [GIANT-LOCKED] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold ppbus0: <Parallel port bus> on ppc0 plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sbc0: <Creative SB16/SB32> at port 0x388-0x38b,0x330-0x331,0x220-0x22f irq 5 drq 5,1 on isa0 sbc0: [GIANT-LOCKED] pcm0: <SB16 DSP 4.13> on sbc0 pcm0: [GIANT-LOCKED] unknown: <PNP0401> can't assign resources (port) unknown: <PNP0501> can't assign resources (port) unknown: <PNP0501> can't assign resources (port) unknown: <PNP0700> can't assign resources (port) unknown: <PNP0f13> can't assign resources (irq) unknown: <PNP0303> can't assign resources (port) Timecounter "TSC" frequency 501138175 Hz quality 800 Timecounters tick every 10.000 msec ad0: 6869MB <Maxtor 90720D5> [13957/16/63] at ata0-master PIO4 ad1: 12971MB <WDC WD136AA> [26354/16/63] at ata1-master PIO4 acd0: CDROM <NEC CD-ROM DRIVE:28C> at ata1-slave PIO4 Mounting root from ufs:/dev/ad1s1a dc0: failed to force tx and rx to idle state dc0: failed to force tx and rx to idle state ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to deny, logging limited to 1000 packets/entry by default dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state -- Crist J. Clark | cjclark_at_alum.mit.edu | cjclark_at_jhu.edu http://people.freebsd.org/~cjc/ | cjc_at_freebsd.orgReceived on Thu Apr 15 2004 - 21:08:10 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:51 UTC