Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Oct 2003 13:40:36 +0200
From:      "Terrence Koeman" <root@mediamonks.net>
To:        <freebsd-current@freebsd.org>
Subject:   Re: Intel 1000/PRO (em) problem
Message-ID:  <200310201340.AA1966394@mediamonks.com>

next in thread | raw e-mail | index | archive | help
Well, I tried the drivers from intel.com, but they are indeed for 4.x kernels and don't work on 5.1. An odd thing I noticed is that the driver in 5.1 has the same versionnumber as the driver on intel.com, but obviously isn't the same.

Sysctl hw.em0.rx_int_delay was already on 0, so that didn't help either. I think I'll write to Intel support.

-- 
Regards,
Terrence Koeman

MediaMonks B.V. (www.mediamonks.com)
Please quote all replies in correspondence.

---------- Original Message ----------------------------------
From: "Will Froning" <wfroning@angui.sh>
Date:  Sat, 18 Oct 2003 20:27:28 -0700 (PDT)

>Not sure if anyone has helped you on this, but I've been having this
>problem for a while on 4.x with select chipsets.  My solution is newer
>drivers from intel.com.
>
>Sadly I don't think the drivers on intel.com will work for 5.1, but they
>work great for 4.X.  I just copy them to /usr/src/sys/drv/em and rebuild. 
>I wish I had more help, but I haven't moved my production boxes to 5.1
>yet.
>
>HTH,
>Will
>
>
>> Hi,
>>
>> I'm experiencing a problem with the em driver in 5.1-CURRENT for my Intel
>> 1000/Pro fiber Gbit adapter.
>>
>> The following is recorded in the syslog:
>>
>> Oct 15 18:17:49 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 15 18:30:25 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 15 18:30:27 shaolin kernel: em0: Link is Down
>> Oct 15 18:30:27 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 15 18:31:14 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 15 18:44:35 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 15 18:44:37 shaolin kernel: em0: Link is Down
>> Oct 15 18:44:37 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 15 22:13:54 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 02:18:10 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 02:28:33 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 04:51:46 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 05:58:20 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 05:58:22 shaolin kernel: em0: Link is Down
>> Oct 16 05:58:22 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 08:06:26 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 12:10:01 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 12:10:03 shaolin kernel: em0: Link is Down
>> Oct 16 12:10:04 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 13:44:00 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 13:44:02 shaolin kernel: em0: Link is Down
>> Oct 16 13:44:02 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 14:25:31 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:27:01 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:28:41 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:28:43 shaolin kernel: em0: Link is Down
>> Oct 16 14:28:44 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 14:43:30 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:46:57 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:46:59 shaolin kernel: em0: Link is Down
>> Oct 16 14:46:59 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 14:51:17 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:51:43 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 14:51:45 shaolin kernel: em0: Link is Down
>> Oct 16 14:51:45 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
>> Oct 16 14:53:32 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 15:15:44 shaolin kernel: em0: watchdog timeout -- resetting
>> Oct 16 15:28:33 shaolin kernel: em0: watchdog timeout -- resetting
>>
>> Everytime it does that connectivity is lost for 2-3 minutes.
>>
>> I have found a similar problem at
>> http://lists.freebsd.org/pipermail/freebsd-stable/2003-April/000539.html
>> but that problem seems to be solved long ago, and the fix described in the
>> thread doesn't help me.
>>
>> I have tried to use some older drivers, but none would solve the problem.
>>
>> Does anyone have an idea how to solve this?
>>
>> Thanks in advance!
>>
>> dmesg:
>>
>> FreeBSD 5.1-CURRENT #12: Mon Oct 13 23:34:55 CEST 2003
>>     root@shaolin.mediamonks.net:/usr/obj/usr/src/sys/SHAOLIN
>> Preloaded elf kernel "/boot/kernel/kernel" at 0xc040d000.
>> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc040d1cc.
>> Timecounter "i8254" frequency 1193182 Hz quality 0
>> CPU: Intel Pentium III (601.37-MHz 686-class CPU)
>>   Origin = "GenuineIntel"  Id = 0x681  Stepping = 1
>>   Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
>> real memory  = 1073725440 (1023 MB)
>> avail memory = 1038782464 (990 MB)
>> Pentium Pro MTRR support enabled
>> npx0: [FAST]
>> npx0: <math processor> on motherboard
>> npx0: INT 16 interface
>> acpi0: <ASUS   P3B_F   > on motherboard
>> pcibios: BIOS version 2.10
>> Using $PIR table, 8 entries at 0xc00f0e80
>> acpi0: Power Button (fixed)
>> Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
>> acpi_cpu0: <CPU> on acpi0
>> acpi_button0: <Power Button> on acpi0
>> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
>> pci0: <ACPI PCI bus> on pcib0
>> pcib0: slot 9 INTA is routed to irq 12
>> pcib1: <PCI-PCI bridge> at device 1.0 on pci0
>> pci1: <PCI bus> on pcib1
>> isab0: <PCI-ISA bridge> at device 4.0 on pci0
>> isa0: <ISA bus> on isab0
>> atapci0: <Intel PIIX4 UDMA33 controller> port 0xd800-0xd80f at device 4.1
>> on pci0
>> ata0: at 0x1f0 irq 14 on atapci0
>> ata0: [MPSAFE]
>> ata1: at 0x170 irq 15 on atapci0
>> ata1: [MPSAFE]
>> pci0: <serial bus, USB> at device 4.2 (no driver attached)
>> pci0: <bridge, PCI-unknown> at device 4.3 (no driver attached)
>> pci0: <display, VGA> at device 9.0 (no driver attached)
>> xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem
>> 0xe5800000-0xe580007f at device 10.0 on pci0
>> pcib0: slot 10 INTA is routed to irq 9
>> xl0: Ethernet address: 00:04:76:9b:e7:b4
>> miibus0: <MII bus> on xl0
>> xlphy0: <3Com internal media interface> on miibus0
>> xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.16> mem
>> 0xe5000000-0xe501ffff at device 12.0 on pci0
>> pcib0: slot 12 INTA is routed to irq 11
>> em0:  Speed:1000 Mbps  Duplex:Full
>> fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port
>> 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
>> fdc0: FIFO enabled, 8 bytes threshold
>> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>> sio0 port 0x3f8-0x3ff irq 4 on acpi0
>> sio0: type 16550A
>> atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
>> orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
>> sc0: <System console> on isa0
>> sc0: VGA <16 virtual consoles, flags=0x200>
>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
>> sio1: configured irq 3 not in bitmap of probed irqs 0
>> sio1: port may not be enabled
>> Timecounter "TSC" frequency 601366241 Hz quality 800
>> Timecounters tick every 1.000 msec
>> ipfw2 initialized, divert enabled, rule-based forwarding enabled, default
>> to accept, logging limited to 20 packets/entry by default
>> acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%
>> GEOM: create disk ad0 dp=0xc628d770
>> ad0: 14324MB <QUANTUM FIREBALLP LM15> [29104/16/63] at ata0-master UDMA33
>> acd0: CDROM <IDE/ATAPI CD-ROM 50XS> at ata1-master PIO4
>> Mounting root from ufs:/dev/ad0s1a
>>
>> --
>> Regards,
>> Terrence Koeman
>>
>> MediaMonks B.V. (www.mediamonks.com)
>> Please quote all replies in correspondence.
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>>
>
>
>-- 
>Will Froning
>Sys Admin, Lt. Pimp
>wfroning@angui.sh
>
 
                 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310201340.AA1966394>