Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no traffic flows on latest ten64 branch #18

Closed
dch opened this issue Mar 22, 2023 · 2 comments
Closed

no traffic flows on latest ten64 branch #18

dch opened this issue Mar 22, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@dch
Copy link

dch commented Mar 22, 2023 •
edited
Loading

src 5f6b8b3 tip of ten64 branch.

Not quite sure how to characterise this bug. I see inbound IP traffic but nothing
makes it out an interface, nor across between interfaces. pf is running, route
appears to select the correct interface. Just nothing gets out.

# ifconfig
dpni1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8002b<RXCSUM,TXCSUM,VLAN_MTU,JUMBO_MTU,LINKSTATE>
        ether 00:0a:fa:24:2b:16
        inet 172.16.1.1 netmask 0xffffff00 broadcast 172.16.1.255
        inet6 fe80::20a:faff:fe24:2b16%dpni1 prefixlen 64 scopeid 0x2
        inet6 2a02:ab8:201:14a0::1 prefixlen 128
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
dpni2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8002b<RXCSUM,TXCSUM,VLAN_MTU,JUMBO_MTU,LINKSTATE>
        ether 00:0a:fa:24:2b:17
        inet 172.16.2.1 netmask 0xffffff00 broadcast 172.16.2.255
        media: Ethernet autoselect (1000baseT <full-duplex,master>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
...
  • still see arp
root@continuity:~ # arp -a
? (172.16.3.1) at 00:0a:fa:24:2b:18 on dpni3 permanent [ethernet]
? (172.16.2.28) at 7c:9e:bd:e0:1f:4c on dpni2 expires in 1088 seconds [ethernet]
? (172.16.2.4) at f0:9f:c2:17:e4:3c on dpni2 expires in 1080 seconds [ethernet]
? (172.16.2.37) at (incomplete) on dpni2 expired [ethernet]
? (172.16.2.5) at 00:03:ac:41:53:52 on dpni2 expires in 1101 seconds [ethernet]
? (172.16.2.2) at 80:2a:a8:83:e2:a3 on dpni2 expires in 1114 seconds [ethernet]
? (172.16.2.3) at 80:2a:a8:59:bd:3f on dpni2 expires in 1110 seconds [ethernet]
? (172.16.2.1) at 00:0a:fa:24:2b:17 on dpni2 permanent [ethernet]
? (172.16.1.5) at b8:59:9f:1a:82:26 on dpni1 expires in 1082 seconds [ethernet]
? (172.16.1.4) at ac:1f:6b:67:e1:38 on dpni1 expires in 1079 seconds [ethernet]
? (172.16.1.1) at 00:0a:fa:24:2b:16 on dpni1 permanent [ethernet]
  • and tcpdump sees udp & bootp requests as well, coming in:
00:04:39.287011 IP (tos 0x0, ttl 64, id 13090, offset 0, flags [DF], proto UDP (17), length 273)
    172.16.2.2.42964 > 255.255.255.255.10001: [udp sum ok] UDP, length 245
00:04:39.288209 IP6 (flowlabel 0x63218, hlim 1, next-header UDP (17) payload length: 253) fe80::822a:a8ff:fe83:e2a3.44188 > ff02::1.10001: [udp sum ok] UDP, length 245
00:04:41.650980 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 252)
    172.16.2.4.50424 > 255.255.255.255.10001: [udp sum ok] UDP, length 224
00:04:41.651607 IP6 (hlim 1, next-header UDP (17) payload length: 232) fe80::f29f:c2ff:fe17:e43c.44241 > ff02::1.10001: [udp sum ok] UDP, length 224
00:04:44.214711 IP (tos 0x0, ttl 64, id 32404, offset 0, flags [DF], proto UDP (17), length 274)
    192.168.1.20.55774 > 255.255.255.255.10001: [udp sum ok] UDP, length 246
00:04:44.215969 IP6 (flowlabel 0xbcec0, hlim 1, next-header UDP (17) payload length: 254) fe80::822a:a8ff:fe59:bd3f.46677 > ff02::1.10001: [udp sum ok] UDP, length 246
00:04:51.671240 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 252)
    172.16.2.4.53764 > 255.255.255.255.10001: [udp sum ok] UDP, length 224
00:04:51.673338 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 80:2a:a8:59:bd:3f (oui Unknown), length 300, xid 0x6b4285a, secs 122, Flags [none] (0x0000)
          Client-Ethernet-Address 80:2a:a8:59:bd:3f (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Client-ID Option 61, length 7: ether 80:2a:a8:59:bd:3f
            Requested-IP Option 50, length 4: 172.16.2.3
            MSZ Option 57, length 2: 576
            Parameter-Request Option 55, length 8:
              Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
              Domain-Name, BR, NTP, Vendor-Option
            Vendor-Class Option 60, length 4: "ubnt"
            Hostname Option 12, length 7: "terrace"
            END Option 255, length 0
            PAD Option 0, length 0, occurs 12

but nothing goes out:

root@continuity:~ # vmstat -i | grep dpaa
its0,33: dpaa2_mac0                                       1          0
its0,34: dpaa2_mac1                                       2          0
its0,35: dpaa2_mac2                                       2          0
its0,37: dpaa2_mac4                                       2          0
its0,43: dpaa2_io0                                       17          0
its0,44: dpaa2_io1                                      449          1
its0,45: dpaa2_io2                                     1122          4
its0,46: dpaa2_io3                                     1111          4
its0,47: dpaa2_io4                                     1061          4
its0,48: dpaa2_io5                                       90          0
its0,49: dpaa2_io6                                     1013          3
its0,50: dpaa2_io7                                      359          1
its0,52: dpaa2_ni1                                        1          0
its0,53: dpaa2_ni2                                        1          0
its0,58: dpaa2_ni7                                        1          0

root@continuity:~ # ping -fc 1000 172.16.1.4

root@continuity:~ # vmstat -i | grep dpaa
its0,33: dpaa2_mac0                                       1          0
its0,34: dpaa2_mac1                                       2          0
its0,35: dpaa2_mac2                                       2          0
its0,37: dpaa2_mac4                                       2          0
its0,43: dpaa2_io0                                       17          0
its0,44: dpaa2_io1                                      449          1
its0,45: dpaa2_io2                                     1430          4
its0,46: dpaa2_io3                                     1392          4
its0,47: dpaa2_io4                                     1353          4
its0,48: dpaa2_io5                                       90          0
its0,49: dpaa2_io6                                     1320          3
its0,50: dpaa2_io7                                      359          1
its0,52: dpaa2_ni1                                        1          0
its0,53: dpaa2_ni2                                        1          0
its0,58: dpaa2_ni7                                        1          0

root@continuity:~ # sysctl dev.dpaa2_ni.1
dev.dpaa2_ni.1.stats.in_all_frames: 15310
dev.dpaa2_ni.1.stats.in_all_bytes: 1346077
dev.dpaa2_ni.1.stats.in_multi_frames: 619
dev.dpaa2_ni.1.stats.eg_all_frames: 160
dev.dpaa2_ni.1.stats.eg_all_bytes: 24574
dev.dpaa2_ni.1.stats.eg_multi_frames: 6
dev.dpaa2_ni.1.stats.in_filtered_frames: 3
dev.dpaa2_ni.1.stats.in_discarded_frames: 0
dev.dpaa2_ni.1.stats.in_nobuf_discards: 0
dev.dpaa2_ni.1.stats.buf_free: 1392
dev.dpaa2_ni.1.stats.buf_num: 11200
dev.dpaa2_ni.1.%parent: dpaa2_rc0
dev.dpaa2_ni.1.%pnpinfo:
dev.dpaa2_ni.1.%location:
dev.dpaa2_ni.1.%driver: dpaa2_ni
dev.dpaa2_ni.1.%desc: DPAA2 Network Interface
@dsalychev dsalychev added the bug Something isn't working label Mar 22, 2023
@pkubaj
Copy link

pkubaj commented Jul 13, 2023

I'm not sure whether it's the same issue, but I can't do any traffic after booting until I replug the network cables. If I just unplug them and immediately plug in, traffic starts working.

@dsalychev
Copy link

dsalychev commented Jul 28, 2023 •
edited
Loading

@pkubaj Sounds like a different issue. Could you report it as a separate bug? I'm going to close this one because almost all of the changes in the ten64 branch have found its way into https://github.com/mcusim/freebsd-src/tree/dpaa2 one and it's a correct branch to test.

@mcbridematt mcbridematt mentioned this issue Aug 1, 2023
Closed
dsalychev pushed a commit that referenced this issue Sep 9, 2023
@np-2020
cxgbe(4): Avoid hang on kldunload on netlink enabled kernels.
3814249 
netlink(4) calls back into the driver during detach and it attempts to
start an internal synchronized op recursively, causing an interruptible
hang.  Fix it by failing the ioctl if the VI has been marked as DOOMED
by cxgbe_detach.

Here's the stack for the hang for reference.
 #6  begin_synchronized_op
 #7  cxgbe_media_status
 #8  ifmedia_ioctl
 #9  cxgbe_ioctl
 #10 if_ioctl
 #11 get_operstate_ether
 #12 get_operstate
 #13 dump_iface
 #14 rtnl_handle_ifevent
 #15 rtnl_handle_ifnet_event
 #16 rt_ifmsg
 #17 if_unroute
 #18 if_down
 #19 if_detach_internal
 #20 if_detach
 #21 ether_ifdetach
 #22 cxgbe_vi_detach
 #23 cxgbe_detach
 #24 DEVICE_DETACH

MFC after:	3 days
Sponsored by:	Chelsio Communications
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dch @dsalychev @pkubaj