On Thursday 21 February 2013 16:13:07 Hauke Mehrtens wrote:
> On 02/20/2013 02:46 PM, Cezary Jackiewicz wrote:
> > Dnia 2013-02-20, o godz. 14:11:53
> >
> > Hauke Mehrtens <ha...@hauke-m.de> napisał(a):
> >> On my e3200 Ethernet works with the default config. Are there more
> >> problems discussed in this tread?
> >
> > On my e3200 also ethernet seems to work, but often hangs up with:
> >
> > [ 121.980000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 120! End of ring: 0 [ 121.988000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 121! End of ring: 0 [
> > 121.996000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 122! End of ring: 0 [ 122.008000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 123! End of ring: 0 [
> > 122.016000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 124! End of ring: 0 [ 122.024000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 125! End of ring: 0 [
> > 122.036000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 126! End of ring: 0 [ 122.044000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 127! End of ring: 0 [
> > 122.052000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 0! End of ring: 0 [ 122.064000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 1! End of ring: 0 [
> > 122.072000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 2! End of ring: 0 [ 122.080000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 3! End of ring: 0 [
> > 122.088000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 4! End of ring: 0 [ 122.100000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 5! End of ring: 0 [
> > 122.108000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 6! End of ring: 0 [ 122.116000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 7! End of ring: 0 [
> > 122.128000] bgmac bcma0:1: Hardware reported transmission for empty TX
> > ring slot 8! End of ring: 0 [ 122.136000] bgmac bcma0:1: Hardware
> > reported transmission for empty TX ring slot 9! End of ring: 0
> >
> > etc.
>
> I have seen the same problem with my e3200. When this happens I see
> ~17MByte/s of garbage traffic on the NIC of my desktop connected to this
> devices. It looks like it sends out old packages or parts of it in an
> endless loop. Most of them did not contained a valid Ethernet header but
> some contained the OpenWrt logo, where I expected an Ethernet or IP
> header. ;-)
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I notice the same behaviour here. I see this happen regularly, when booting
the device, without network cables plugged in, or no network traffic being
received. By default, an udhcp client is run on internet interface, which
sends out packets, but no answer is (ever) returned.
After about 300 seconds, the driver will start reporting these messages, after
a while the system reboots.
I made a tcpdump on the wan port, which shows only udp dhcp requests being
sent. At the moment the driver starts reporting, I can see two packets being
echoed from the past (dhcp requests hold the 'seconds elapsed' field, which
normally only augments).
Packets sent out, with increasing seconds elapsed:
17:53:54.097432 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.q..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:53:57.098021 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.t..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:00.101515 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.w..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102124 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
The following two packets are from the past
17:54:03.102145 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gn.....1.Us....................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102152 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gn.....1.Us. ..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
After this, the latest packet, with highest seconds elapsed field is being
repeated indefinately at a high rate:
17:54:03.102203 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102232 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102266 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102299 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102333 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102427 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
17:54:03.102434 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 20:aa:4b:21:19:73 (oui Unknown), length 351
E..{....@.ys.........D.C.gl.....1.Us.z..................
.K!.s..........................................................................................................................................................................................................c.Sc5..9..@7.......*<.udhcp
1.19.4.................................................................................
On the other hand, I can stress the device for hours with high network load,
without seeing this problem.
Regards,
Tijs_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
