Re: em broken on current amd64
> On 13 Sep 2015, at 16:45, Sean Bruno wrote: > Any chance you can turn TSO off if its on and see what your results are? Only TSO4 was on. I turned it off; no difference. M -- Mark R V Murray ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
On 09/12/15 13:45, Mark R V Murray wrote: > >> On 8 Sep 2015, at 19:02, Mark R V Murray wrote: >> >> >>> On 8 Sep 2015, at 17:22, Sean Bruno wrote: >>> >>> >> >> I’m also seeing breakage with the em0 device; this isn’t a kernel >> hang, it is a failure to move data after about 10-15 minutes. The >> symptom is that my WAN ethernet no longer moves traffic, no pings, >> nothing. Booting looks normal: >> >> em0: port >> 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq >> 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet >> address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX >> 1/1024 >> >> Fixing it is as easy as … >> >> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up >> >> :-) >> >> I’m running CURRENT, r287538. This last worked of me a month or so >> ago at my previous build. >> >> M >> > > > Just so I'm clear, the original problem reported was a failure to > attach (you were among several folks reporting breakage). Is that fixed > ? I did not report the failure to attach, and I am not seeing it as I don’t think I built a kernel that had that particular failure. I am having the “failure after 10-15 minutes” problem; this is on an em0 device. M >>> >>> >>> Hrm, that's odd. That sounds like a hole where interrupts aren't being >>> reset for "reasons" that I cannot fathom. >>> >>> What hardware (pciconf -lv) does your system actually have? The em(4) >>> driver doesn't identify components which is frustrating. >> >> pciconf -lv output below: >> >> hostb0@pci0:0:0:0: class=0x06 card=0x514d8086 chip=0x29a08086 rev=0x02 >> hdr=0x00 >>vendor = 'Intel Corporation' >>device = '82P965/G965 Memory Controller Hub' >>class = bridge >>subclass = HOST-PCI > > I just caught this, on today’s build: > > em0: Watchdog timeout Queue[0]-- resetting > Interface is RUNNING and ACTIVE > em0: TX Queue 0 -- > em0: hw tdh = 127, hw tdt = 139 > em0: Tx Queue Status = -2147483648 > em0: TX descriptors avail = 1012 > em0: Tx Descriptors avail failure = 0 > em0: RX Queue 0 -- > em0: hw rdh = 0, hw rdt = 1023 > em0: RX discarded packets = 0 > em0: RX Next to Check = 0 > em0: RX Next to Refresh = 1023 > > [graveyard] /usr/ports 09:42 pm # uname -a > FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287705: > Sat Sep 12 15:07:54 BST 2015 > r...@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 > > M > Any chance you can turn TSO off if its on and see what your results are? sean ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
On Sat, 12 Sep 2015, Mark R V Murray wrote: I just caught this, on today’s build: em0: Watchdog timeout Queue[0]-- resetting Interface is RUNNING and ACTIVE em0: TX Queue 0 -- em0: hw tdh = 127, hw tdt = 139 em0: Tx Queue Status = -2147483648 em0: TX descriptors avail = 1012 em0: Tx Descriptors avail failure = 0 em0: RX Queue 0 -- em0: hw rdh = 0, hw rdt = 1023 em0: RX discarded packets = 0 em0: RX Next to Check = 0 em0: RX Next to Refresh = 1023 [graveyard] /usr/ports 09:42 pm # uname -a FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287705: Sat Sep 12 15:07:54 BST 2015 r...@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 That happened on an amd64 10-STABLE (r287148) system here a couple of days ago. Both I217-V and 82574L cards in that system, but I did not save the message and can't say which had the error. Never seen before, has not happened again. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
> On 8 Sep 2015, at 19:02, Mark R V Murray wrote: > > >> On 8 Sep 2015, at 17:22, Sean Bruno wrote: >> >> > > I’m also seeing breakage with the em0 device; this isn’t a kernel > hang, it is a failure to move data after about 10-15 minutes. The > symptom is that my WAN ethernet no longer moves traffic, no pings, > nothing. Booting looks normal: > > em0: port > 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq > 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet > address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX > 1/1024 > > Fixing it is as easy as … > > # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up > > :-) > > I’m running CURRENT, r287538. This last worked of me a month or so > ago at my previous build. > > M > Just so I'm clear, the original problem reported was a failure to attach (you were among several folks reporting breakage). Is that fixed ? >>> >>> I did not report the failure to attach, and I am not seeing it as I don’t >>> think I built a kernel that had that particular failure. I am having the >>> “failure after 10-15 minutes” problem; this is on an em0 device. >>> >>> M >>> >> >> >> Hrm, that's odd. That sounds like a hole where interrupts aren't being >> reset for "reasons" that I cannot fathom. >> >> What hardware (pciconf -lv) does your system actually have? The em(4) >> driver doesn't identify components which is frustrating. > > pciconf -lv output below: > > hostb0@pci0:0:0:0:class=0x06 card=0x514d8086 chip=0x29a08086 rev=0x02 > hdr=0x00 >vendor = 'Intel Corporation' >device = '82P965/G965 Memory Controller Hub' >class = bridge >subclass = HOST-PCI I just caught this, on today’s build: em0: Watchdog timeout Queue[0]-- resetting Interface is RUNNING and ACTIVE em0: TX Queue 0 -- em0: hw tdh = 127, hw tdt = 139 em0: Tx Queue Status = -2147483648 em0: TX descriptors avail = 1012 em0: Tx Descriptors avail failure = 0 em0: RX Queue 0 -- em0: hw rdh = 0, hw rdt = 1023 em0: RX discarded packets = 0 em0: RX Next to Check = 0 em0: RX Next to Refresh = 1023 [graveyard] /usr/ports 09:42 pm # uname -a FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287705: Sat Sep 12 15:07:54 BST 2015 r...@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 M -- Mark R V Murray ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
> On 8 Sep 2015, at 17:22, Sean Bruno wrote: > > I’m also seeing breakage with the em0 device; this isn’t a kernel hang, it is a failure to move data after about 10-15 minutes. The symptom is that my WAN ethernet no longer moves traffic, no pings, nothing. Booting looks normal: em0: port 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX 1/1024 Fixing it is as easy as … # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up :-) I’m running CURRENT, r287538. This last worked of me a month or so ago at my previous build. M >>> >>> >>> Just so I'm clear, the original problem reported was a failure to >>> attach (you were among several folks reporting breakage). Is that fixed >>> ? >> >> I did not report the failure to attach, and I am not seeing it as I don’t >> think I built a kernel that had that particular failure. I am having the >> “failure after 10-15 minutes” problem; this is on an em0 device. >> >> M >> > > > Hrm, that's odd. That sounds like a hole where interrupts aren't being > reset for "reasons" that I cannot fathom. > > What hardware (pciconf -lv) does your system actually have? The em(4) > driver doesn't identify components which is frustrating. pciconf -lv output below: hostb0@pci0:0:0:0: class=0x06 card=0x514d8086 chip=0x29a08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82P965/G965 Memory Controller Hub' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x514d8086 chip=0x29a28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82G965 Integrated Graphics Controller' class = display subclass = VGA none0@pci0:0:3:0: class=0x078000 card=0x514d8086 chip=0x29a48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82P965/G965 HECI Controller' class = simple comms em0@pci0:0:25:0:class=0x02 card=0x00018086 chip=0x104b8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82566DC Gigabit Network Connection' class = network subclass = ethernet uhci0@pci0:0:26:0: class=0x0c0300 card=0x514d8086 chip=0x28348086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB uhci1@pci0:0:26:1: class=0x0c0300 card=0x514d8086 chip=0x28358086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB ehci0@pci0:0:26:7: class=0x0c0320 card=0x514d8086 chip=0x283a8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB2 EHCI Controller' class = serial bus subclass = USB hdac0@pci0:0:27:0: class=0x040300 card=0x21148086 chip=0x284b8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) HD Audio Controller' class = multimedia subclass = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x283f8086 chip=0x283f8086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) PCI Express Port 1' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x28418086 chip=0x28418086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) PCI Express Port 2' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x28438086 chip=0x28438086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) PCI Express Port 3' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:3: class=0x060400 card=0x28458086 chip=0x28458086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) PCI Express Port 4' class = bridge subclass = PCI-PCI pcib5@pci0:0:28:4: class=0x060400 card=0x28478086 chip=0x28478086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) PCI Express Port 5' class = bridge subclass = PCI-PCI uhci2@pci0:0:29:0: class=0x0c0300 card=0x514d8086 chip=0x28308086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB uhci3@pci0:0:29:1: class=0x0c0300 card=0x514d8086 chip=0x28318086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB uhci4@pci0:0
Re: em broken on current amd64
>>> >>> I’m also seeing breakage with the em0 device; this isn’t a kernel >>> hang, it is a failure to move data after about 10-15 minutes. The >>> symptom is that my WAN ethernet no longer moves traffic, no pings, >>> nothing. Booting looks normal: >>> >>> em0: port >>> 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq >>> 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet >>> address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX >>> 1/1024 >>> >>> Fixing it is as easy as … >>> >>> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up >>> >>> :-) >>> >>> I’m running CURRENT, r287538. This last worked of me a month or so >>> ago at my previous build. >>> >>> M >>> >> >> >> Just so I'm clear, the original problem reported was a failure to >> attach (you were among several folks reporting breakage). Is that fixed >> ? > > I did not report the failure to attach, and I am not seeing it as I don’t > think I built a kernel that had that particular failure. I am having the > “failure after 10-15 minutes” problem; this is on an em0 device. > > M > Hrm, that's odd. That sounds like a hole where interrupts aren't being reset for "reasons" that I cannot fathom. What hardware (pciconf -lv) does your system actually have? The em(4) driver doesn't identify components which is frustrating. sean ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
> On 8 Sep 2015, at 00:44, Sean Bruno wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > On 09/07/15 14:10, Mark R V Murray wrote: >> >>> On 5 Sep 2015, at 17:11, Garrett Cooper >>> wrote: >>> >>> On Sep 5, 2015, at 08:50, Manfred Antar wrote: Recent changes to em have broken current on amd64. Booting kernel will hang when trying to load em0, then will continue booting without the driver loading (No Network) This is on a HP SFF 8000 with em0 embedded on the motherboard. boot messages: em0: port 0x3100-0x311f mem 0xf310-0xf311,0xf3125000-0xf3125fff irq 19 at device 25.0 on pci0 em0: attempting to allocate 1 MSI vectors (1 supported) em0: using IRQ 265 for MSI em0: Using an MSI interrupt em0: The EEPROM Checksum Is Not Valid device_attach: em0 attach returned 5 >>> >>> Tijl said the same. The offending commit's r287467. Cheers, >> >> I’m also seeing breakage with the em0 device; this isn’t a kernel >> hang, it is a failure to move data after about 10-15 minutes. The >> symptom is that my WAN ethernet no longer moves traffic, no pings, >> nothing. Booting looks normal: >> >> em0: port >> 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq >> 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet >> address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX >> 1/1024 >> >> Fixing it is as easy as … >> >> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up >> >> :-) >> >> I’m running CURRENT, r287538. This last worked of me a month or so >> ago at my previous build. >> >> M >> > > > Just so I'm clear, the original problem reported was a failure to > attach (you were among several folks reporting breakage). Is that fixed > ? I did not report the failure to attach, and I am not seeing it as I don’t think I built a kernel that had that particular failure. I am having the “failure after 10-15 minutes” problem; this is on an em0 device. M -- Mark R V Murray ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
On 2015-09-07 23:10, Mark R V Murray wrote: > >> On 5 Sep 2015, at 17:11, Garrett Cooper wrote: >> >> >>> On Sep 5, 2015, at 08:50, Manfred Antar wrote: >>> >>> Recent changes to em have broken current on amd64. >>> Booting kernel will hang when trying to load em0, then will continue >>> booting without the driver loading (No Network) >>> This is on a HP SFF 8000 with em0 embedded on the motherboard. >>> >>> boot messages: >>> >>> em0: port 0x3100-0x311f mem >>> 0xf310-0xf311,0xf3125000-0xf3125fff irq 19 at device 25.0 on pci0 >>> em0: attempting to allocate 1 MSI vectors (1 supported) >>> em0: using IRQ 265 for MSI >>> em0: Using an MSI interrupt >>> em0: The EEPROM Checksum Is Not Valid >>> device_attach: em0 attach returned 5 >> >> Tijl said the same. The offending commit's r287467. >> Cheers, > > I’m also seeing breakage with the em0 device; this isn’t a kernel hang, it is > a failure to move data after about 10-15 minutes. The symptom is that my WAN > ethernet no longer moves traffic, no pings, nothing. Booting looks normal: > > em0: port 0x30c0-0x30df mem > 0x5030-0x5031,0x50324000-0x50324fff irq 20 at device 25.0 on pci0 > em0: Using an MSI interrupt > em0: Ethernet address: 00:16:76:d3:e1:5b > em0: netmap queues/slots: TX 1/1024, RX 1/1024 > > Fixing it is as easy as … > > # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up > > :-) > > I’m running CURRENT, r287538. This last worked of me a month or so ago at my > previous build. > Not sure if this is a current issue. Some days ago I build a 10.2 system with an on-board em0 to test my new assigned IPv6 (only) connectivity and seeing similar symptoms. Haven't measured the time but the system stops forwarding packages on the em0 until I bring it down and up again (sometime additional restart pf) # uname FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=4219b ether f8:b1:56:d7:a9:c4 inet6 fe80::fab1:56ff:fed7:a9c4%em0 prefixlen 64 scopeid 0x1 inet6 2001:9xx:1xxx::2 prefixlen 64 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active # dmesg | grep em0 em0: port 0xf040-0xf05f mem 0xfb30-0xfb31,0xfb328000-0xfb328fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: f8:b1:56:d7:a9:c4 ahciem0: on ahci0 ses0 at ahciem0 bus 0 scbus1 target 0 lun 0 -- olli ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/07/15 14:10, Mark R V Murray wrote: > >> On 5 Sep 2015, at 17:11, Garrett Cooper >> wrote: >> >> >>> On Sep 5, 2015, at 08:50, Manfred Antar wrote: >>> >>> Recent changes to em have broken current on amd64. Booting >>> kernel will hang when trying to load em0, then will continue >>> booting without the driver loading (No Network) This is on a HP >>> SFF 8000 with em0 embedded on the motherboard. >>> >>> boot messages: >>> >>> em0: port >>> 0x3100-0x311f mem 0xf310-0xf311,0xf3125000-0xf3125fff >>> irq 19 at device 25.0 on pci0 em0: attempting to allocate 1 MSI >>> vectors (1 supported) em0: using IRQ 265 for MSI em0: Using an >>> MSI interrupt em0: The EEPROM Checksum Is Not Valid >>> device_attach: em0 attach returned 5 >> >> Tijl said the same. The offending commit's r287467. Cheers, > > I’m also seeing breakage with the em0 device; this isn’t a kernel > hang, it is a failure to move data after about 10-15 minutes. The > symptom is that my WAN ethernet no longer moves traffic, no pings, > nothing. Booting looks normal: > > em0: port > 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq > 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet > address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX > 1/1024 > > Fixing it is as easy as … > > # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up > > :-) > > I’m running CURRENT, r287538. This last worked of me a month or so > ago at my previous build. > > M > Just so I'm clear, the original problem reported was a failure to attach (you were among several folks reporting breakage). Is that fixed ? sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJV7iFPXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kFn4H/Rsjq9GqgTHUZHvw4e7DkM8y nWftg4CM3RCMDnLPHxrFSXIUgq8a7jrtbEcft7YlA0ko56uqJs1SWgbXT2Ug4Mb7 0zNPR/Qy4ihGcwrfDew/JrSKGNG/T7BmNKFY7ANd90fcTeTf6qKIkhUj6bfj+m6/ OfAfQiegI9A5db7xbohhuG4RfXOx2yOz9ONkBpROuwBm7YvYk4hP4yIpGl+ANZ9V YtjhaEw2v7ehu8SpZ6Zg8XbbtfJ9k814WXxdx7FOcfiSeVPxTa4unwavzjhYWhy0 Z33DAyB8tsrzXfPMu9QZaU9XHUV1fROJ88B2MA0CvTnavhSjd+cCPVnTTnFX/bI= =A76q -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
> On 5 Sep 2015, at 17:11, Garrett Cooper wrote: > > >> On Sep 5, 2015, at 08:50, Manfred Antar wrote: >> >> Recent changes to em have broken current on amd64. >> Booting kernel will hang when trying to load em0, then will continue booting >> without the driver loading (No Network) >> This is on a HP SFF 8000 with em0 embedded on the motherboard. >> >> boot messages: >> >> em0: port 0x3100-0x311f mem >> 0xf310-0xf311,0xf3125000-0xf3125fff irq 19 at device 25.0 on pci0 >> em0: attempting to allocate 1 MSI vectors (1 supported) >> em0: using IRQ 265 for MSI >> em0: Using an MSI interrupt >> em0: The EEPROM Checksum Is Not Valid >> device_attach: em0 attach returned 5 > > Tijl said the same. The offending commit's r287467. > Cheers, I’m also seeing breakage with the em0 device; this isn’t a kernel hang, it is a failure to move data after about 10-15 minutes. The symptom is that my WAN ethernet no longer moves traffic, no pings, nothing. Booting looks normal: em0: port 0x30c0-0x30df mem 0x5030-0x5031,0x50324000-0x50324fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX 1/1024 Fixing it is as easy as … # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up :-) I’m running CURRENT, r287538. This last worked of me a month or so ago at my previous build. M -- Mark R V Murray ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em broken on current amd64
> On Sep 5, 2015, at 08:50, Manfred Antar wrote: > > Recent changes to em have broken current on amd64. > Booting kernel will hang when trying to load em0, then will continue booting > without the driver loading (No Network) > This is on a HP SFF 8000 with em0 embedded on the motherboard. > > boot messages: > > em0: port 0x3100-0x311f mem > 0xf310-0xf311,0xf3125000-0xf3125fff irq 19 at device 25.0 on pci0 > em0: attempting to allocate 1 MSI vectors (1 supported) > em0: using IRQ 265 for MSI > em0: Using an MSI interrupt > em0: The EEPROM Checksum Is Not Valid > device_attach: em0 attach returned 5 Tijl said the same. The offending commit's r287467. Cheers, ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
