Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi, On Fri, Mar 11, 2011 at 9:57 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hi again, I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs. How high is `nmbclusters' ? Thanks, - Arnaud ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi Arnaud, # sysctl kern.ipc.nmbclusters kern.ipc.nmbclusters: 262144 On Mon, Mar 14, 2011 at 4:02 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, On Fri, Mar 11, 2011 at 9:57 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hi again, I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs. How high is `nmbclusters' ? Thanks, - Arnaud ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi, On Mon, Mar 14, 2011 at 10:17 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hi Arnaud, # sysctl kern.ipc.nmbclusters kern.ipc.nmbclusters: 262144 Well, then this is not surprising em(4) behave well, knowing that it is unable to handle resource shortage, give it plenty of it and it will be happy. 200MBps is about 18000 1500bytes packet by seconds. I will not trust the quality of any code which need 10x more resources available than needed to do the job. Even 1Gbps should be attainable with only 128k clusters. - Arnaud On Mon, Mar 14, 2011 at 4:02 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, On Fri, Mar 11, 2011 at 9:57 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hi again, I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs. How high is `nmbclusters' ? Thanks, - Arnaud ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi again,
I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs.
Altough em0 has about 200Mbps traffic, cpu usage of em0 is too high.
Should I try -DEM_MULTIQUEUE option ?
Regards,
Ozkan KIRIK
# uptime
4:36PM up 7 days, 8:30, 1 user, load averages: 4.19, 3.73, 3.71
# uname -srp
FreeBSD 8.2-RELEASE amd64
# bwm-ng
input: getifaddrs type: rate
| iface Rx TxTotal
em0: 149356.24 Kb/s30202.86 Kb/s 179559.10 Kb/s
em1:1896.86 Kb/s 225.53 Kb/s 2122.39 Kb/s
bce0:8201.30 Kb/s42895.40 Kb/s51096.70 Kb/s
em2: 22524.07 Kb/s42751.14 Kb/s65275.21 Kb/s
em3:3767.80 Kb/s51521.05 Kb/s55288.85 Kb/s
# top -SHn
last pid: 38924; load averages: 2.97, 3.32, 3.51 up 7+08:35:2916:41:59
693 processes: 13 running, 656 sleeping, 24 waiting
Mem: 4393M Active, 8060M Inact, 2761M Wired, 255M Cache, 1647M Buf, 402M Free
Swap: 4096M Total, 4096M Free
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
0 root -680 0K 176K CPU22 45.9H 83.30% {em0 taskq}
11 root 171 ki31 0K 128K RUN 3 154.7H 82.28% {idle: cpu3}
11 root 171 ki31 0K 128K CPU77 152.4H 74.85% {idle: cpu7}
11 root 171 ki31 0K 128K CPU11 143.4H 71.53% {idle: cpu1}
11 root 171 ki31 0K 128K RUN 6 150.2H 70.90% {idle: cpu6}
11 root 171 ki31 0K 128K CPU00 135.0H 67.53% {idle: cpu0}
11 root 171 ki31 0K 128K RUN 5 142.3H 56.49% {idle: cpu5}
11 root 171 ki31 0K 128K CPU44 133.7H 56.45% {idle: cpu4}
12 root -68- 0K 384K WAIT4 992:45 35.25% {irq258: bce0}
0 root -680 0K 176K - 5 18.8H 33.84% {em2 taskq}
11 root 171 ki31 0K 128K RUN 2 124.5H 19.24% {idle: cpu2}
0 root -680 0K 176K CPU66 898:40 17.68% {em3 taskq}
# sysctl dev.em. | grep miss
dev.em.0.mac_stats.missed_packets: 910
dev.em.1.mac_stats.missed_packets: 0
dev.em.2.mac_stats.missed_packets: 5886
dev.em.3.mac_stats.missed_packets: 5518
# sysctl dev.em.
dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.2.2
dev.em.0.%driver: em
dev.em.0.%location: slot=0 function=0 handle=\_SB_.PCI0.NPE2.SPE4.P8PC.LAN0
dev.em.0.%pnpinfo: vendor=0x8086 device=0x1096 subvendor=0x108e
subdevice=0x4843 class=0x02
dev.em.0.%parent: pci4
dev.em.0.nvm: -1
dev.em.0.debug: -1
dev.em.0.rx_int_delay: 0
dev.em.0.tx_int_delay: 66
dev.em.0.rx_abs_int_delay: 66
dev.em.0.tx_abs_int_delay: 66
dev.em.0.rx_processing_limit: 100
dev.em.0.flow_control: 3
dev.em.0.eee_control: 0
dev.em.0.link_irq: 0
dev.em.0.mbuf_alloc_fail: 0
dev.em.0.cluster_alloc_fail: 0
dev.em.0.dropped: 0
dev.em.0.tx_dma_fail: 0
dev.em.0.rx_overruns: 1
dev.em.0.watchdog_timeouts: 0
dev.em.0.device_control: 1075593793
dev.em.0.rx_control: 67141634
dev.em.0.fc_high_water: 30720
dev.em.0.fc_low_water: 29220
dev.em.0.queue0.txd_head: 311
dev.em.0.queue0.txd_tail: 311
dev.em.0.queue0.tx_irq: 0
dev.em.0.queue0.no_desc_avail: 0
dev.em.0.queue0.rxd_head: 1144
dev.em.0.queue0.rxd_tail: 1120
dev.em.0.queue0.rx_irq: 0
dev.em.0.mac_stats.excess_coll: 0
dev.em.0.mac_stats.single_coll: 0
dev.em.0.mac_stats.multiple_coll: 0
dev.em.0.mac_stats.late_coll: 0
dev.em.0.mac_stats.collision_count: 0
dev.em.0.mac_stats.symbol_errors: 0
dev.em.0.mac_stats.sequence_errors: 0
dev.em.0.mac_stats.defer_count: 0
dev.em.0.mac_stats.missed_packets: 910
dev.em.0.mac_stats.recv_no_buff: 7050
dev.em.0.mac_stats.recv_undersize: 0
dev.em.0.mac_stats.recv_fragmented: 0
dev.em.0.mac_stats.recv_oversize: 0
dev.em.0.mac_stats.recv_jabber: 0
dev.em.0.mac_stats.recv_errs: 0
dev.em.0.mac_stats.crc_errs: 0
dev.em.0.mac_stats.alignment_errs: 0
dev.em.0.mac_stats.coll_ext_errs: 0
dev.em.0.mac_stats.xon_recvd: 0
dev.em.0.mac_stats.xon_txd: 0
dev.em.0.mac_stats.xoff_recvd: 0
dev.em.0.mac_stats.xoff_txd: 0
dev.em.0.mac_stats.total_pkts_recvd: 3324123116
dev.em.0.mac_stats.good_pkts_recvd: 3324122206
dev.em.0.mac_stats.bcast_pkts_recvd: 159692
dev.em.0.mac_stats.mcast_pkts_recvd: 0
dev.em.0.mac_stats.rx_frames_64: 314397503
dev.em.0.mac_stats.rx_frames_65_127: 511431761
dev.em.0.mac_stats.rx_frames_128_255: 62445780
dev.em.0.mac_stats.rx_frames_256_511: 76542752
dev.em.0.mac_stats.rx_frames_512_1023: 111888998
dev.em.0.mac_stats.rx_frames_1024_1522: 2247415412
dev.em.0.mac_stats.good_octets_recvd: 3546201196566
dev.em.0.mac_stats.good_octets_txd: 1361437676103
dev.em.0.mac_stats.total_pkts_txd: 2931605576
dev.em.0.mac_stats.good_pkts_txd: 2931605576
dev.em.0.mac_stats.bcast_pkts_txd: 27621
dev.em.0.mac_stats.mcast_pkts_txd: 8
dev.em.0.mac_stats.tx_frames_64: 532709844
dev.em.0.mac_stats.tx_frames_65_127: 1405874859
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
MULTIQUEUE won't help on that hardware, only the 82574 has the ability to
use multiple queues in the em driver. Its the advanced server adapters
supported
by the igb driver that are the best choice in that regard.
So, now the driver does not hang but cpu is too high... Anyone else find
this to
be the case that is testing this driver?
Jack
On Fri, Mar 11, 2011 at 6:57 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote:
Hi again,
I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs.
Altough em0 has about 200Mbps traffic, cpu usage of em0 is too high.
Should I try -DEM_MULTIQUEUE option ?
Regards,
Ozkan KIRIK
# uptime
4:36PM up 7 days, 8:30, 1 user, load averages: 4.19, 3.73, 3.71
# uname -srp
FreeBSD 8.2-RELEASE amd64
# bwm-ng
input: getifaddrs type: rate
| iface Rx Tx
Total
em0: 149356.24 Kb/s30202.86 Kb/s 179559.10
Kb/s
em1:1896.86 Kb/s 225.53 Kb/s 2122.39
Kb/s
bce0:8201.30 Kb/s42895.40 Kb/s51096.70
Kb/s
em2: 22524.07 Kb/s42751.14 Kb/s65275.21
Kb/s
em3:3767.80 Kb/s51521.05 Kb/s55288.85
Kb/s
# top -SHn
last pid: 38924; load averages: 2.97, 3.32, 3.51 up 7+08:35:29
16:41:59
693 processes: 13 running, 656 sleeping, 24 waiting
Mem: 4393M Active, 8060M Inact, 2761M Wired, 255M Cache, 1647M Buf, 402M
Free
Swap: 4096M Total, 4096M Free
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
0 root -680 0K 176K CPU22 45.9H 83.30% {em0 taskq}
11 root 171 ki31 0K 128K RUN 3 154.7H 82.28% {idle: cpu3}
11 root 171 ki31 0K 128K CPU77 152.4H 74.85% {idle: cpu7}
11 root 171 ki31 0K 128K CPU11 143.4H 71.53% {idle: cpu1}
11 root 171 ki31 0K 128K RUN 6 150.2H 70.90% {idle: cpu6}
11 root 171 ki31 0K 128K CPU00 135.0H 67.53% {idle: cpu0}
11 root 171 ki31 0K 128K RUN 5 142.3H 56.49% {idle: cpu5}
11 root 171 ki31 0K 128K CPU44 133.7H 56.45% {idle: cpu4}
12 root -68- 0K 384K WAIT4 992:45 35.25% {irq258:
bce0}
0 root -680 0K 176K - 5 18.8H 33.84% {em2 taskq}
11 root 171 ki31 0K 128K RUN 2 124.5H 19.24% {idle: cpu2}
0 root -680 0K 176K CPU66 898:40 17.68% {em3 taskq}
# sysctl dev.em. | grep miss
dev.em.0.mac_stats.missed_packets: 910
dev.em.1.mac_stats.missed_packets: 0
dev.em.2.mac_stats.missed_packets: 5886
dev.em.3.mac_stats.missed_packets: 5518
# sysctl dev.em.
dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.2.2
dev.em.0.%driver: em
dev.em.0.%location: slot=0 function=0 handle=\_SB_.PCI0.NPE2.SPE4.P8PC.LAN0
dev.em.0.%pnpinfo: vendor=0x8086 device=0x1096 subvendor=0x108e
subdevice=0x4843 class=0x02
dev.em.0.%parent: pci4
dev.em.0.nvm: -1
dev.em.0.debug: -1
dev.em.0.rx_int_delay: 0
dev.em.0.tx_int_delay: 66
dev.em.0.rx_abs_int_delay: 66
dev.em.0.tx_abs_int_delay: 66
dev.em.0.rx_processing_limit: 100
dev.em.0.flow_control: 3
dev.em.0.eee_control: 0
dev.em.0.link_irq: 0
dev.em.0.mbuf_alloc_fail: 0
dev.em.0.cluster_alloc_fail: 0
dev.em.0.dropped: 0
dev.em.0.tx_dma_fail: 0
dev.em.0.rx_overruns: 1
dev.em.0.watchdog_timeouts: 0
dev.em.0.device_control: 1075593793
dev.em.0.rx_control: 67141634
dev.em.0.fc_high_water: 30720
dev.em.0.fc_low_water: 29220
dev.em.0.queue0.txd_head: 311
dev.em.0.queue0.txd_tail: 311
dev.em.0.queue0.tx_irq: 0
dev.em.0.queue0.no_desc_avail: 0
dev.em.0.queue0.rxd_head: 1144
dev.em.0.queue0.rxd_tail: 1120
dev.em.0.queue0.rx_irq: 0
dev.em.0.mac_stats.excess_coll: 0
dev.em.0.mac_stats.single_coll: 0
dev.em.0.mac_stats.multiple_coll: 0
dev.em.0.mac_stats.late_coll: 0
dev.em.0.mac_stats.collision_count: 0
dev.em.0.mac_stats.symbol_errors: 0
dev.em.0.mac_stats.sequence_errors: 0
dev.em.0.mac_stats.defer_count: 0
dev.em.0.mac_stats.missed_packets: 910
dev.em.0.mac_stats.recv_no_buff: 7050
dev.em.0.mac_stats.recv_undersize: 0
dev.em.0.mac_stats.recv_fragmented: 0
dev.em.0.mac_stats.recv_oversize: 0
dev.em.0.mac_stats.recv_jabber: 0
dev.em.0.mac_stats.recv_errs: 0
dev.em.0.mac_stats.crc_errs: 0
dev.em.0.mac_stats.alignment_errs: 0
dev.em.0.mac_stats.coll_ext_errs: 0
dev.em.0.mac_stats.xon_recvd: 0
dev.em.0.mac_stats.xon_txd: 0
dev.em.0.mac_stats.xoff_recvd: 0
dev.em.0.mac_stats.xoff_txd: 0
dev.em.0.mac_stats.total_pkts_recvd: 3324123116
dev.em.0.mac_stats.good_pkts_recvd: 3324122206
dev.em.0.mac_stats.bcast_pkts_recvd: 159692
dev.em.0.mac_stats.mcast_pkts_recvd: 0
dev.em.0.mac_stats.rx_frames_64: 314397503
dev.em.0.mac_stats.rx_frames_65_127: 511431761
dev.em.0.mac_stats.rx_frames_128_255: 62445780
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
On 3/11/2011 12:23 PM, Jack Vogel wrote: So, now the driver does not hang but cpu is too high... Anyone else find this to be the case that is testing this driver? Just eyeballing the load avg graphs on the 2 boxes where I am testing, I dont see any glaring differences. But I have not set out to do any specific measurements / tests in that regard. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hello, I've been testing the em.7.2.2 driver as kld. The system is up about 2 days 6 hours. System has 4 em interfaces, Throughput is about 200Mbit/s. System didn't hang, but em2 has Input Errors. I saw that, dev.em.2.mac_stats.missed_packets is not zero? What could be the problem? # uname -r 8.2-RELEASE # sysctl dev.em.| grep miss dev.em.0.mac_stats.missed_packets: 0 dev.em.1.mac_stats.missed_packets: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.3.mac_stats.missed_packets: 0 # netstat -nWI em2 | grep Link Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em2 1500 Link#4 00:23:8b:89:e4:9e 267256324 5886 0 273081628 0 0 # sysctl dev.em.2. dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 7.2.2 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P4.BR1E dev.em.2.%pnpinfo: vendor=0x8086 device=0x105e subvendor=0x108e subdevice=0x125e class=0x02 dev.em.2.%parent: pci12 dev.em.2.nvm: -1 dev.em.2.debug: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 3 dev.em.2.eee_control: 0 dev.em.2.link_irq: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.rx_overruns: 7 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1075577409 dev.em.2.rx_control: 67141634 dev.em.2.fc_high_water: 30720 dev.em.2.fc_low_water: 29220 dev.em.2.queue0.txd_head: 3025 dev.em.2.queue0.txd_tail: 3025 dev.em.2.queue0.tx_irq: 0 dev.em.2.queue0.no_desc_avail: 0 dev.em.2.queue0.rxd_head: 1826 dev.em.2.queue0.rxd_tail: 1825 dev.em.2.queue0.rx_irq: 0 dev.em.2.mac_stats.excess_coll: 0 dev.em.2.mac_stats.single_coll: 0 dev.em.2.mac_stats.multiple_coll: 0 dev.em.2.mac_stats.late_coll: 0 dev.em.2.mac_stats.collision_count: 0 dev.em.2.mac_stats.symbol_errors: 0 dev.em.2.mac_stats.sequence_errors: 0 dev.em.2.mac_stats.defer_count: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.2.mac_stats.recv_no_buff: 3407 dev.em.2.mac_stats.recv_undersize: 0 dev.em.2.mac_stats.recv_fragmented: 0 dev.em.2.mac_stats.recv_oversize: 0 dev.em.2.mac_stats.recv_jabber: 0 dev.em.2.mac_stats.recv_errs: 0 dev.em.2.mac_stats.crc_errs: 0 dev.em.2.mac_stats.alignment_errs: 0 dev.em.2.mac_stats.coll_ext_errs: 0 dev.em.2.mac_stats.xon_recvd: 0 dev.em.2.mac_stats.xon_txd: 0 dev.em.2.mac_stats.xoff_recvd: 0 dev.em.2.mac_stats.xoff_txd: 0 dev.em.2.mac_stats.total_pkts_recvd: 265358324 dev.em.2.mac_stats.good_pkts_recvd: 265352438 dev.em.2.mac_stats.bcast_pkts_recvd: 701728 dev.em.2.mac_stats.mcast_pkts_recvd: 4076 dev.em.2.mac_stats.rx_frames_64: 0 dev.em.2.mac_stats.rx_frames_65_127: 140801982 dev.em.2.mac_stats.rx_frames_128_255: 3553397 dev.em.2.mac_stats.rx_frames_256_511: 3418754 dev.em.2.mac_stats.rx_frames_512_1023: 8096866 dev.em.2.mac_stats.rx_frames_1024_1522: 109481439 dev.em.2.mac_stats.good_octets_recvd: 177455051448 dev.em.2.mac_stats.good_octets_txd: 274861571704 dev.em.2.mac_stats.total_pkts_txd: 270439410 dev.em.2.mac_stats.good_pkts_txd: 270439410 dev.em.2.mac_stats.bcast_pkts_txd: 194927 dev.em.2.mac_stats.mcast_pkts_txd: 48 dev.em.2.mac_stats.tx_frames_64: 23050855 dev.em.2.mac_stats.tx_frames_65_127: 54156414 dev.em.2.mac_stats.tx_frames_128_255: 4299280 dev.em.2.mac_stats.tx_frames_256_511: 7837146 dev.em.2.mac_stats.tx_frames_512_1023: 8272014 dev.em.2.mac_stats.tx_frames_1024_1522: 172823701 dev.em.2.mac_stats.tso_txd: 0 dev.em.2.mac_stats.tso_ctx_fail: 0 dev.em.2.interrupts.asserts: 283674059 dev.em.2.interrupts.rx_pkt_timer: 33585 dev.em.2.interrupts.rx_abs_timer: 0 dev.em.2.interrupts.tx_pkt_timer: 11022 dev.em.2.interrupts.tx_abs_timer: 22449 dev.em.2.interrupts.tx_queue_empty: 0 dev.em.2.interrupts.tx_queue_min_thresh: 0 dev.em.2.interrupts.rx_desc_min_thresh: 0 dev.em.2.interrupts.rx_overrun: 0 Regards, Ozkan KIRIK ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Missed packets just mean that some temporary resource shortage or error caused the packet to be dropped. I don't believe this is indicative of a problem, just let it keep running, 2 days is good but 2 weeks is better :) Thanks for testing it! Jack On Sun, Mar 6, 2011 at 4:37 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hello, I've been testing the em.7.2.2 driver as kld. The system is up about 2 days 6 hours. System has 4 em interfaces, Throughput is about 200Mbit/s. System didn't hang, but em2 has Input Errors. I saw that, dev.em.2.mac_stats.missed_packets is not zero? What could be the problem? # uname -r 8.2-RELEASE # sysctl dev.em.| grep miss dev.em.0.mac_stats.missed_packets: 0 dev.em.1.mac_stats.missed_packets: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.3.mac_stats.missed_packets: 0 # netstat -nWI em2 | grep Link Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em2 1500 Link#4 00:23:8b:89:e4:9e 267256324 5886 0 273081628 0 0 # sysctl dev.em.2. dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 7.2.2 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P4.BR1E dev.em.2.%pnpinfo: vendor=0x8086 device=0x105e subvendor=0x108e subdevice=0x125e class=0x02 dev.em.2.%parent: pci12 dev.em.2.nvm: -1 dev.em.2.debug: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 3 dev.em.2.eee_control: 0 dev.em.2.link_irq: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.rx_overruns: 7 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1075577409 dev.em.2.rx_control: 67141634 dev.em.2.fc_high_water: 30720 dev.em.2.fc_low_water: 29220 dev.em.2.queue0.txd_head: 3025 dev.em.2.queue0.txd_tail: 3025 dev.em.2.queue0.tx_irq: 0 dev.em.2.queue0.no_desc_avail: 0 dev.em.2.queue0.rxd_head: 1826 dev.em.2.queue0.rxd_tail: 1825 dev.em.2.queue0.rx_irq: 0 dev.em.2.mac_stats.excess_coll: 0 dev.em.2.mac_stats.single_coll: 0 dev.em.2.mac_stats.multiple_coll: 0 dev.em.2.mac_stats.late_coll: 0 dev.em.2.mac_stats.collision_count: 0 dev.em.2.mac_stats.symbol_errors: 0 dev.em.2.mac_stats.sequence_errors: 0 dev.em.2.mac_stats.defer_count: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.2.mac_stats.recv_no_buff: 3407 dev.em.2.mac_stats.recv_undersize: 0 dev.em.2.mac_stats.recv_fragmented: 0 dev.em.2.mac_stats.recv_oversize: 0 dev.em.2.mac_stats.recv_jabber: 0 dev.em.2.mac_stats.recv_errs: 0 dev.em.2.mac_stats.crc_errs: 0 dev.em.2.mac_stats.alignment_errs: 0 dev.em.2.mac_stats.coll_ext_errs: 0 dev.em.2.mac_stats.xon_recvd: 0 dev.em.2.mac_stats.xon_txd: 0 dev.em.2.mac_stats.xoff_recvd: 0 dev.em.2.mac_stats.xoff_txd: 0 dev.em.2.mac_stats.total_pkts_recvd: 265358324 dev.em.2.mac_stats.good_pkts_recvd: 265352438 dev.em.2.mac_stats.bcast_pkts_recvd: 701728 dev.em.2.mac_stats.mcast_pkts_recvd: 4076 dev.em.2.mac_stats.rx_frames_64: 0 dev.em.2.mac_stats.rx_frames_65_127: 140801982 dev.em.2.mac_stats.rx_frames_128_255: 3553397 dev.em.2.mac_stats.rx_frames_256_511: 3418754 dev.em.2.mac_stats.rx_frames_512_1023: 8096866 dev.em.2.mac_stats.rx_frames_1024_1522: 109481439 dev.em.2.mac_stats.good_octets_recvd: 177455051448 dev.em.2.mac_stats.good_octets_txd: 274861571704 dev.em.2.mac_stats.total_pkts_txd: 270439410 dev.em.2.mac_stats.good_pkts_txd: 270439410 dev.em.2.mac_stats.bcast_pkts_txd: 194927 dev.em.2.mac_stats.mcast_pkts_txd: 48 dev.em.2.mac_stats.tx_frames_64: 23050855 dev.em.2.mac_stats.tx_frames_65_127: 54156414 dev.em.2.mac_stats.tx_frames_128_255: 4299280 dev.em.2.mac_stats.tx_frames_256_511: 7837146 dev.em.2.mac_stats.tx_frames_512_1023: 8272014 dev.em.2.mac_stats.tx_frames_1024_1522: 172823701 dev.em.2.mac_stats.tso_txd: 0 dev.em.2.mac_stats.tso_ctx_fail: 0 dev.em.2.interrupts.asserts: 283674059 dev.em.2.interrupts.rx_pkt_timer: 33585 dev.em.2.interrupts.rx_abs_timer: 0 dev.em.2.interrupts.tx_pkt_timer: 11022 dev.em.2.interrupts.tx_abs_timer: 22449 dev.em.2.interrupts.tx_queue_empty: 0 dev.em.2.interrupts.tx_queue_min_thresh: 0 dev.em.2.interrupts.rx_desc_min_thresh: 0 dev.em.2.interrupts.rx_overrun: 0 Regards, Ozkan KIRIK ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi Jack, On Sun, Mar 6, 2011 at 2:48 PM, Jack Vogel jfvo...@gmail.com wrote: Missed packets just mean that some temporary resource shortage or error caused the packet to be dropped. I don't believe this is indicative of a problem, just let it keep running, 2 days is good but 2 weeks is better :) Thanks for testing it! I still did not get any feedback from you about the patch I sent the list about not ignoring the RX overrun interrupt triggered by the card. Thanks, - Arnaud Jack On Sun, Mar 6, 2011 at 4:37 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hello, I've been testing the em.7.2.2 driver as kld. The system is up about 2 days 6 hours. System has 4 em interfaces, Throughput is about 200Mbit/s. System didn't hang, but em2 has Input Errors. I saw that, dev.em.2.mac_stats.missed_packets is not zero? What could be the problem? # uname -r 8.2-RELEASE # sysctl dev.em.| grep miss dev.em.0.mac_stats.missed_packets: 0 dev.em.1.mac_stats.missed_packets: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.3.mac_stats.missed_packets: 0 # netstat -nWI em2 | grep Link Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em2 1500 Link#4 00:23:8b:89:e4:9e 267256324 5886 0 273081628 0 0 # sysctl dev.em.2. dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 7.2.2 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P4.BR1E dev.em.2.%pnpinfo: vendor=0x8086 device=0x105e subvendor=0x108e subdevice=0x125e class=0x02 dev.em.2.%parent: pci12 dev.em.2.nvm: -1 dev.em.2.debug: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 3 dev.em.2.eee_control: 0 dev.em.2.link_irq: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.rx_overruns: 7 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1075577409 dev.em.2.rx_control: 67141634 dev.em.2.fc_high_water: 30720 dev.em.2.fc_low_water: 29220 dev.em.2.queue0.txd_head: 3025 dev.em.2.queue0.txd_tail: 3025 dev.em.2.queue0.tx_irq: 0 dev.em.2.queue0.no_desc_avail: 0 dev.em.2.queue0.rxd_head: 1826 dev.em.2.queue0.rxd_tail: 1825 dev.em.2.queue0.rx_irq: 0 dev.em.2.mac_stats.excess_coll: 0 dev.em.2.mac_stats.single_coll: 0 dev.em.2.mac_stats.multiple_coll: 0 dev.em.2.mac_stats.late_coll: 0 dev.em.2.mac_stats.collision_count: 0 dev.em.2.mac_stats.symbol_errors: 0 dev.em.2.mac_stats.sequence_errors: 0 dev.em.2.mac_stats.defer_count: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.2.mac_stats.recv_no_buff: 3407 dev.em.2.mac_stats.recv_undersize: 0 dev.em.2.mac_stats.recv_fragmented: 0 dev.em.2.mac_stats.recv_oversize: 0 dev.em.2.mac_stats.recv_jabber: 0 dev.em.2.mac_stats.recv_errs: 0 dev.em.2.mac_stats.crc_errs: 0 dev.em.2.mac_stats.alignment_errs: 0 dev.em.2.mac_stats.coll_ext_errs: 0 dev.em.2.mac_stats.xon_recvd: 0 dev.em.2.mac_stats.xon_txd: 0 dev.em.2.mac_stats.xoff_recvd: 0 dev.em.2.mac_stats.xoff_txd: 0 dev.em.2.mac_stats.total_pkts_recvd: 265358324 dev.em.2.mac_stats.good_pkts_recvd: 265352438 dev.em.2.mac_stats.bcast_pkts_recvd: 701728 dev.em.2.mac_stats.mcast_pkts_recvd: 4076 dev.em.2.mac_stats.rx_frames_64: 0 dev.em.2.mac_stats.rx_frames_65_127: 140801982 dev.em.2.mac_stats.rx_frames_128_255: 3553397 dev.em.2.mac_stats.rx_frames_256_511: 3418754 dev.em.2.mac_stats.rx_frames_512_1023: 8096866 dev.em.2.mac_stats.rx_frames_1024_1522: 109481439 dev.em.2.mac_stats.good_octets_recvd: 177455051448 dev.em.2.mac_stats.good_octets_txd: 274861571704 dev.em.2.mac_stats.total_pkts_txd: 270439410 dev.em.2.mac_stats.good_pkts_txd: 270439410 dev.em.2.mac_stats.bcast_pkts_txd: 194927 dev.em.2.mac_stats.mcast_pkts_txd: 48 dev.em.2.mac_stats.tx_frames_64: 23050855 dev.em.2.mac_stats.tx_frames_65_127: 54156414 dev.em.2.mac_stats.tx_frames_128_255: 4299280 dev.em.2.mac_stats.tx_frames_256_511: 7837146 dev.em.2.mac_stats.tx_frames_512_1023: 8272014 dev.em.2.mac_stats.tx_frames_1024_1522: 172823701 dev.em.2.mac_stats.tso_txd: 0 dev.em.2.mac_stats.tso_ctx_fail: 0 dev.em.2.interrupts.asserts: 283674059 dev.em.2.interrupts.rx_pkt_timer: 33585 dev.em.2.interrupts.rx_abs_timer: 0 dev.em.2.interrupts.tx_pkt_timer: 11022 dev.em.2.interrupts.tx_abs_timer: 22449 dev.em.2.interrupts.tx_queue_empty: 0 dev.em.2.interrupts.tx_queue_min_thresh: 0 dev.em.2.interrupts.rx_desc_min_thresh: 0 dev.em.2.interrupts.rx_overrun: 0 Regards, Ozkan KIRIK ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
On Sun, Mar 6, 2011 at 1:48 PM, Jack Vogel jfvo...@gmail.com wrote: Missed packets just mean that some temporary resource shortage or error caused the packet to be dropped. I don't believe this is indicative of a problem, just let it keep running, 2 days is good but 2 weeks is better :) Thanks for testing it! Jack Jack, I found several production machines I can test 7.2.2 on, if you'd be so kind to provide me with a link or an attachment :) I don't know exactly what chips they are, but I figure that testing is still testing... -Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hi, On Sun, Mar 6, 2011 at 4:23 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi Jack, On Sun, Mar 6, 2011 at 2:48 PM, Jack Vogel jfvo...@gmail.com wrote: Missed packets just mean that some temporary resource shortage or error caused the packet to be dropped. I don't believe this is indicative of a problem, just let it keep running, 2 days is good but 2 weeks is better :) Thanks for testing it! I still did not get any feedback from you about the patch I sent the list about not ignoring the RX overrun interrupt triggered by the card. Just to precise. For what I understood of Beezar Lui fix, all the work is done in the RX interrupt context, ie. you rely on the card to trigger RX interrupt to refresh mbufs. If the resource shortage is too long, the card stops triggering RX interrupt and hang, but it _still_ trigger RX overrun to warn the OS about the situation. Currently this interrupt is just ignored. Your original fix works for igb(4) as a single handler is used per queue; igb_rxeof() get called in both RX and TX context. This is not the case with em(4) as RX and TX interrupt are independent from each other. So if the hardware empties the ring and you cannot replenish it while you still get RX interrupt, you have no other choice than using the RX overrun interrupt to hope to recover. - Arnaud Thanks, - Arnaud Jack On Sun, Mar 6, 2011 at 4:37 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: Hello, I've been testing the em.7.2.2 driver as kld. The system is up about 2 days 6 hours. System has 4 em interfaces, Throughput is about 200Mbit/s. System didn't hang, but em2 has Input Errors. I saw that, dev.em.2.mac_stats.missed_packets is not zero? What could be the problem? # uname -r 8.2-RELEASE # sysctl dev.em.| grep miss dev.em.0.mac_stats.missed_packets: 0 dev.em.1.mac_stats.missed_packets: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.3.mac_stats.missed_packets: 0 # netstat -nWI em2 | grep Link Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em2 1500 Link#4 00:23:8b:89:e4:9e 267256324 5886 0 273081628 0 0 # sysctl dev.em.2. dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 7.2.2 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P4.BR1E dev.em.2.%pnpinfo: vendor=0x8086 device=0x105e subvendor=0x108e subdevice=0x125e class=0x02 dev.em.2.%parent: pci12 dev.em.2.nvm: -1 dev.em.2.debug: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 3 dev.em.2.eee_control: 0 dev.em.2.link_irq: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.rx_overruns: 7 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1075577409 dev.em.2.rx_control: 67141634 dev.em.2.fc_high_water: 30720 dev.em.2.fc_low_water: 29220 dev.em.2.queue0.txd_head: 3025 dev.em.2.queue0.txd_tail: 3025 dev.em.2.queue0.tx_irq: 0 dev.em.2.queue0.no_desc_avail: 0 dev.em.2.queue0.rxd_head: 1826 dev.em.2.queue0.rxd_tail: 1825 dev.em.2.queue0.rx_irq: 0 dev.em.2.mac_stats.excess_coll: 0 dev.em.2.mac_stats.single_coll: 0 dev.em.2.mac_stats.multiple_coll: 0 dev.em.2.mac_stats.late_coll: 0 dev.em.2.mac_stats.collision_count: 0 dev.em.2.mac_stats.symbol_errors: 0 dev.em.2.mac_stats.sequence_errors: 0 dev.em.2.mac_stats.defer_count: 0 dev.em.2.mac_stats.missed_packets: 5886 dev.em.2.mac_stats.recv_no_buff: 3407 dev.em.2.mac_stats.recv_undersize: 0 dev.em.2.mac_stats.recv_fragmented: 0 dev.em.2.mac_stats.recv_oversize: 0 dev.em.2.mac_stats.recv_jabber: 0 dev.em.2.mac_stats.recv_errs: 0 dev.em.2.mac_stats.crc_errs: 0 dev.em.2.mac_stats.alignment_errs: 0 dev.em.2.mac_stats.coll_ext_errs: 0 dev.em.2.mac_stats.xon_recvd: 0 dev.em.2.mac_stats.xon_txd: 0 dev.em.2.mac_stats.xoff_recvd: 0 dev.em.2.mac_stats.xoff_txd: 0 dev.em.2.mac_stats.total_pkts_recvd: 265358324 dev.em.2.mac_stats.good_pkts_recvd: 265352438 dev.em.2.mac_stats.bcast_pkts_recvd: 701728 dev.em.2.mac_stats.mcast_pkts_recvd: 4076 dev.em.2.mac_stats.rx_frames_64: 0 dev.em.2.mac_stats.rx_frames_65_127: 140801982 dev.em.2.mac_stats.rx_frames_128_255: 3553397 dev.em.2.mac_stats.rx_frames_256_511: 3418754 dev.em.2.mac_stats.rx_frames_512_1023: 8096866 dev.em.2.mac_stats.rx_frames_1024_1522: 109481439 dev.em.2.mac_stats.good_octets_recvd: 177455051448 dev.em.2.mac_stats.good_octets_txd: 274861571704 dev.em.2.mac_stats.total_pkts_txd: 270439410 dev.em.2.mac_stats.good_pkts_txd: 270439410 dev.em.2.mac_stats.bcast_pkts_txd: 194927 dev.em.2.mac_stats.mcast_pkts_txd: 48 dev.em.2.mac_stats.tx_frames_64: 23050855 dev.em.2.mac_stats.tx_frames_65_127: 54156414 dev.em.2.mac_stats.tx_frames_128_255: 4299280 dev.em.2.mac_stats.tx_frames_256_511: 7837146 dev.em.2.mac_stats.tx_frames_512_1023: 8272014
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Hello, Steven. You wrote 5 марта 2011 г., 3:06:32: Silly question but have you checked your ram for issues, we had a machine with seemingly unexplained problems and hangs and it turned out to be a duff stick of ram which wasn't being chip killed. Yes, two full days (48h) of memtest86+ -- no problems... -- // Black Lion AKA Lev Serebryakov l...@serebryakov.spb.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!)
Silly question but have you checked your ram for issues, we had a machine with seemingly unexplained problems and hangs and it turned out to be a duff stick of ram which wasn't being chip killed. - Original Message - From: Lev Serebryakov l...@serebryakov.spb.ru To: Brandon Gooch jamesbrandongo...@gmail.com Cc: Arnaud Lacombe lacom...@gmail.com; freebsd-...@freebsd.org; freebsd-stable@freebsd.org; Jack Vogel jfvo...@gmail.com; Jan Koum j...@whatsapp.com Sent: Thursday, March 03, 2011 10:25 PM Subject: Re: em0 with latest driver hangs again and again (without Watchdogtimeout message!) Hello, Brandon. You wrote 3 марта 2011 г., 17:08:26: I see that you have CRC errors: dev.em.0.mac_stats.crc_errs: 156 and receive errors: dev.em.0.mac_stats.recv_errs: 147 It (almost) doesn't change. And it hangs again. It seems, that 7.2.2 hangs more often than 7.1.9 on my hardware :( -- // Black Lion AKA Lev Serebryakov l...@serebryakov.spb.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
