Date: Mon, 01 Feb 2021 22:10:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253172] Intel e1000 - Interface Stalls After Media Type is Changed Message-ID: <bug-253172-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253172 Bug ID: 253172 Summary: Intel e1000 - Interface Stalls After Media Type is Changed Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jcaplan@blackberry.com # Overview The e1000 interface stalls occasionally after the media type is changed. The only way of recovering it is to flap the interface (ifconfig down then up). # Steps to Reproduce 1. Bring up an e1000 interface on a QNX target. 2. Run a continuous ping to the target e1000 interface from a directly connected neighbor. 3. Change the media type "ifconfig em0 media 100baseTX mediaopt full-duplex= ". 4. Sometimes you need to change the media type more than once e.g. "ifconfig em0 media 1000baseT mediaopt full-duplex" # Actual Results Ping stops reaching target. 64 bytes from 10.242.241.213: icmp_seq=3D1 ttl=3D64 time=3D0.707 ms 64 bytes from 10.242.241.213: icmp_seq=3D2 ttl=3D64 time=3D0.721 ms 64 bytes from 10.242.241.213: icmp_seq=3D3 ttl=3D64 time=3D0.649 ms 64 bytes from 10.242.241.213: icmp_seq=3D4 ttl=3D64 time=3D0.768 ms 64 bytes from 10.242.241.213: icmp_seq=3D1 ttl=3D64 time=3D8268 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D3 ttl=3D64 time=3D6219 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D9 ttl=3D64 time=3D76.1 ms 64 bytes from 10.242.241.213: icmp_seq=3D10 ttl=3D64 time=3D0.541 ms 64 bytes from 10.242.241.213: icmp_seq=3D11 ttl=3D64 time=3D0.604 ms 64 bytes from 10.242.241.213: icmp_seq=3D12 ttl=3D64 time=3D0.754 ms 64 bytes from 10.242.241.213: icmp_seq=3D13 ttl=3D64 time=3D1.02 ms 64 bytes from 10.242.241.213: icmp_seq=3D14 ttl=3D64 time=3D0.676 ms 64 bytes from 10.242.241.213: icmp_seq=3D15 ttl=3D64 time=3D0.609 ms 64 bytes from 10.242.241.213: icmp_seq=3D16 ttl=3D64 time=3D0.591 ms 64 bytes from 10.242.241.213: icmp_seq=3D1 ttl=3D64 time=3D20397 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D3 ttl=3D64 time=3D18349 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D10 ttl=3D64 time=3D11204 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D12 ttl=3D64 time=3D9165 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D13 ttl=3D64 time=3D8141 ms (DUP!) 64 bytes from 10.242.241.213: icmp_seq=3D16 ttl=3D64 time=3D5101 ms (DUP!) >From 10.242.241.212 icmp_seq=3D50 Destination Host Unreachable >From 10.242.241.212 icmp_seq=3D51 Destination Host Unreachable >From 10.242.241.212 icmp_seq=3D52 Destination Host Unreachable >From 10.242.241.212 icmp_seq=3D53 Destination Host Unreachable >From 10.242.241.212 icmp_seq=3D54 Destination Host Unreachable # Expected Results Ping continues to reach target (possibly some packets dropped). For instanc= e, in the above log, the first 2 DUPs happen when the interface media is chang= ed but service resumes, then I changed it a second time and there are a lot mo= re DUPs and never starts working again. # Build Date FreeBSD bsd-vbox 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r368820: Tue Jan 5 17:30:19 EST 2021=20=20=20=20 jcaplan@bsd-vbox:/usr/obj/usr/src-head/amd64.amd64/sys/GENERIC amd64 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253172-227>