Walter Venable
2009-Jan-07 15:10 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
FreeBSD 7.1 upgrade broke my network access, machine is totally offline (powered-on and I can play inside it at the terminal, but absolutely 0 network access): This happened AFTER make kernel but BEFORE make installworld. I think this implies it's a kernel driver issue. http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing thread on the issue, the rl driver has also been reported broken).
Gavin Atkinson
2009-Jan-07 16:47 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
On Wed, 2009-01-07 at 09:39 -0500, Walter Venable wrote:> FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. > > http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > thread on the issue, the rl driver has also been reported broken).What version of FreeBSD did you upgrade from? Gavin
Walter Venable
2009-Jan-07 18:45 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
On Wed, Jan 7, 2009 at 1:34 PM, Brian Duke <brian@box201.com> wrote:> Walter, > I too have these two interfaces and was forced to disconnect my rl0 in order > for my static ip on re0 to route correctly. If both interfaces are up on the > same network even if both are different IPs all routing stopped. I was > planning on doing a little load balancing project. I didn't due to lack of > time. > > #ifconfig rl0 down > > left my interface up and active. The interface would not change its IP > through sysinstalls' enable networking interfaces. I could do this: > > #ifconfig rl0 inet 192.168.1.150 > > But my routing was messed up at that point and was confirmed via: > > #netstat -r > > The return information looked like it was stuck or lost and the command > never finished. > I had to disconnect one or the other but both simply showed no routes. I > disconnected rl0 because it was a 10/100m interface and left my re0 gig > interface connected rebooted and the routes and networking is again stable. > In the interest of full disclosure rl0 is on the motherboard re0 is a pci > card.Brian, was this happening to you on 7.0 also or just 7.1?
Walter Venable
2009-Jan-07 23:50 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all problems. I believe this roundly confirms that this is a bug in the 7.1-RELEASE re kernel drivers. On Wed, Jan 7, 2009 at 9:39 AM, Walter Venable <walt@relnor.com> wrote:> FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. > > http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > thread on the issue, the rl driver has also been reported broken). >
Pyun YongHyeon
2009-Jan-08 01:55 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
On Wed, Jan 07, 2009 at 09:39:32AM -0500, Walter Venable wrote: > FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. > > http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > thread on the issue, the rl driver has also been reported broken). Please start new thread for rl(4) issues. -- Regards, Pyun YongHyeon
Pyun YongHyeon
2009-Jan-08 02:35 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
On Wed, Jan 07, 2009 at 09:20:05PM -0500, Walter Venable wrote: > On Wed, Jan 7, 2009 at 8:50 PM, Pyun YongHyeon <pyunyh@gmail.com> wrote: > > Please show me full dmesg output. > > > > Hi Pyun, > I have attached the full dmesg output. Walter, I need dmesg output of 7.1-RELEASE. -- Regards, Pyun YongHyeon
Sascha Holzleiter
2009-Jan-12 09:20 UTC
FreeBSD 7.1 Breaks re and rl Network Interface Drivers
Walter Venable wrote:> FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue.Hi, i see similar problems with a re card: re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't seem to receive any frames. I can see the DHCP Requests on the DHCP Server but the DHCPOFFERS are never seen by the client with the re0 device. After setting promiscious mode on the interface (i.e. by tcpdump -ni re0) the interface begins to work fine. I've attached a complete dmesg output, but i think the detection works fine, here the short version: re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on pci4 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1a:92:35:29:fa re0: [FILTER] -------------- next part -------------- Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Mon Jan 12 14:18:26 CET 2009 root@dreamland.office.local:/usr/obj/usr/src/sys/DREAMLAND Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1863.87-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> AMD Features=0x20100000<NX,LM> AMD Features2=0x1<LAHF> Cores per package: 2 real memory = 2146304000 (2046 MB) avail memory = 2086531072 (1989 MB) ACPI APIC Table: <AWARD ASUSACPI> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 <Version 0.3> irqs 0-23 on motherboard ioapic1 <Version 0.3> irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: <AWARD ASUSACPI> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 100000, 7fde0000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: <High Precision Event Timer> iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: <Power Button> on acpi0 acpi_button1: <Sleep Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <PCI-PCI bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> irq 27 at device 2.0 on pci0 pci2: <ACPI PCI bus> on pcib2 vgapci0: <VGA-compatible display> port 0xac00-0xac7f mem 0xdc000000-0xdcffffff,0xc0000000-0xcfffffff,0xdd000000-0xddffffff irq 24 at device 0.0 on pci2 nvidia0: <GeForce 7300 GT> on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcib3: <ACPI PCI-PCI bridge> irq 31 at device 3.0 on pci0 pci3: <ACPI PCI bus> on pcib3 atapci0: <JMicron JMB363 SATA300 controller> port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f mem 0xdfefe000-0xdfefffff irq 28 at device 0.0 on pci3 atapci0: [ITHREAD] atapci0: AHCI called from vendor specific driver atapci0: AHCI Version 01.00 controller with 2 ports detected ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci0 ata3: [ITHREAD] ata4: <ATA channel 2> on atapci0 ata4: [ITHREAD] atapci1: <VIA 8237A SATA150 controller> port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f,0xe800-0xe8ff irq 21 at device 15.0 on pci0 atapci1: [ITHREAD] ata5: <ATA channel 0> on atapci1 ata5: [ITHREAD] ata6: <ATA channel 1> on atapci1 ata6: [ITHREAD] atapci2: <VIA 8237A UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 15.1 on pci0 ata0: <ATA channel 0> on atapci2 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci2 ata1: [ITHREAD] uhci0: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 20 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: <VIA 83C572 USB controller> on uhci0 usb0: USB revision 1.0 uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 22 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: <VIA 83C572 USB controller> on uhci1 usb1: USB revision 1.0 uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: <VIA 83C572 USB controller> on uhci2 usb2: USB revision 1.0 uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 23 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: <VIA 83C572 USB controller> on uhci3 usb3: USB revision 1.0 uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: <VIA VT6202 USB 2.0 controller> mem 0xdffff000-0xdffff0ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: <VIA VT6202 USB 2.0 controller> on ehci0 usb4: USB revision 2.0 uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 uhub4: 8 ports with 8 removable, self powered isab0: <PCI-ISA bridge> at device 17.0 on pci0 isa0: <ISA bus> on isab0 pcib4: <ACPI PCI-PCI bridge> at device 19.1 on pci0 pci4: <ACPI PCI bus> on pcib4 re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on pci4 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1a:92:35:29:fa re0: [FILTER] pcib5: <ACPI Host-PCI bridge> on acpi0 pci128: <ACPI PCI bus> on pcib5 pci128: <multimedia, HDA> at device 1.0 (no driver attached) acpi_tz0: <Thermal Zone> on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] cpu0: <ACPI CPU> on acpi0 est0: <Enhanced SpeedStep Frequency Control> on cpu0 p4tcc0: <CPU Frequency Thermal Control> on cpu0 cpu1: <ACPI CPU> on acpi0 est1: <Enhanced SpeedStep Frequency Control> on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est1 attach returned 6 p4tcc1: <CPU Frequency Thermal Control> on cpu1 acpi_hpet0: <High Precision Event Timer> iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 pmtimer0 on isa0 orm0: <ISA Option ROM> at iomem 0xd0000-0xd2fff pnpid ORM0000 on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ugen0: <vendor 0x046d product 0x08dd, class 0/0, rev 1.10/1.00, addr 2> on uhub0 ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/43.01, addr 2> on uhub1 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec acd0: DVDR <HL-DT-ST DVDRAM GSA-H44N/RB00> at ata0-master UDMA66 ad10: 76319MB <Seagate ST380215AS 3.AAC> at ata5-master SATA150 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad10s1a
I'm on 7.1-RELEASE/amd64 with the following card:
re0@pci0:2:0:0: class=0x020000 card=0x368c1462 chip=0x816810ec rev=0x01 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class = network
subclass = ethernet
And luckey me does not experience any network problems at all.
But I have to say that I was suffering an interrupt storm, and some
smart people told me just to remove USB and Firewire support from the
kernel which has fixed the problem.
Dunno if this helps you.
--
Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174
"If it feels good, you're doing something wrong."
-- Coach McTavish
Walter Venable pisze:> FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. > > http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > thread on the issue, the rl driver has also been reported broken). > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >I can confirm issues with re and 7.1-R dmesg: re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0xbc00-0xbcff mem 0xfbfff000-0xfbfff0ff irq 17 at device 7.0 on pci1 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 In my case this NIC works, but lags like hell after upgrade! Working on console gives me pauses every 3-4 second, and second server which connect to this one with re0 is reporting that communication is lost every couple of minutes -- Bartosz Stec