Latest working kernel version: Earliest failing kernel version: Distribution: Debian amd64 lenny Hardware Environment: Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) Software Environment: atl1 module Problem Description: dmesg get flooded on irregular intervals by atl1 0000:01:00.0: tx busy and atl1 0000:01:00.0: hw csum wrong, pkt_flag:1600, err_flag:80 There aren't any visibile problems with it. eth0 Link encap:Ethernet HWaddr 00:1e:8c:a9:bf:11 inet addr:192.168.66.2 Bcast:192.168.66.255 Mask:255.255.255.0 inet6 addr: fe80::21e:8cff:fea9:bf11/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:80176035 errors:0 dropped:0 overruns:0 frame:0 TX packets:75185297 errors:0 dropped:0 overruns:0 carrier:17 collisions:0 txqueuelen:1000 RX bytes:76786214500 (71.5 GiB) TX bytes:57132572737 (53.2 GiB) Steps to reproduce: don't know exactly, probably under high network load.
Reply-To: akpm@linux-foundation.org (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sat, 5 Jul 2008 03:54:15 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=11036 > > Summary: atl1 tx busy and hw csum wrong > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.24-1-amd64 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: low > Priority: P1 > Component: Network > AssignedTo: jgarzik@pobox.com > ReportedBy: scurippio@gmail.com > > > Latest working kernel version: > Earliest failing kernel version: > Distribution: Debian amd64 lenny > Hardware Environment: Ethernet controller: Attansic Technology Corp. L1 > Gigabit > Ethernet Adapter (rev b0) > Software Environment: atl1 module > Problem Description: > dmesg get flooded on irregular intervals by > atl1 0000:01:00.0: tx busy > and > atl1 0000:01:00.0: hw csum wrong, pkt_flag:1600, err_flag:80 > > There aren't any visibile problems with it. > > eth0 Link encap:Ethernet HWaddr 00:1e:8c:a9:bf:11 > inet addr:192.168.66.2 Bcast:192.168.66.255 Mask:255.255.255.0 > inet6 addr: fe80::21e:8cff:fea9:bf11/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:80176035 errors:0 dropped:0 overruns:0 frame:0 > TX packets:75185297 errors:0 dropped:0 overruns:0 carrier:17 > collisions:0 txqueuelen:1000 > RX bytes:76786214500 (71.5 GiB) TX bytes:57132572737 (53.2 GiB) > > > Steps to reproduce: don't know exactly, probably under high network load. >
On Sat, 5 Jul 2008 12:23:48 -0700 Andrew Morton <akpm@linux-foundation.org> wrote: > > (switched to email. Please respond via emailed reply-to-all, not via > the bugzilla web interface). > > On Sat, 5 Jul 2008 03:54:15 -0700 (PDT) > bugme-daemon@bugzilla.kernel.org wrote: > > > http://bugzilla.kernel.org/show_bug.cgi?id=11036 > > > > Summary: atl1 tx busy and hw csum wrong > > Product: Drivers > > Version: 2.5 > > KernelVersion: 2.6.24-1-amd64 > > Platform: All > > OS/Version: Linux > > Tree: Mainline > > Status: NEW > > Severity: low > > Priority: P1 > > Component: Network > > AssignedTo: jgarzik@pobox.com > > ReportedBy: scurippio@gmail.com > > > > > > Latest working kernel version: > > Earliest failing kernel version: > > Distribution: Debian amd64 lenny > > Hardware Environment: Ethernet controller: Attansic Technology > > Corp. L1 Gigabit Ethernet Adapter (rev b0) > > Software Environment: atl1 module > > Problem Description: > > dmesg get flooded on irregular intervals by > > atl1 0000:01:00.0: tx busy This is a KERN_DEBUG advisory message indicating you ran out of transmit descriptors. This can happen under heavy load. In current mainline this message is filtered by netif_msg_tx_queued, and by default the message will not be issued; it can be turned on using ethtool -s ethX msglvl <value>. > > and > > atl1 0000:01:00.0: hw csum wrong, pkt_flag:1600, err_flag:80 This is also a KERN_DEBUG message, and it indicates that a received packet was too short. pkt_flag:1600 - ipv4, tcp, packet with error err_flag:80 - runt packet In current mainline this message is filtered by netif_msg_rx_err, so it too can be controlled with ethtool (and will also be off by default). To get rid of the messages in your 2.6.24 kernel, you might try reducing the loglevel to exclude KERN_DEBUG messages.