Home > Timed Out > Kernel Tg3 Tg3_stop_block Timed Out

Kernel Tg3 Tg3_stop_block Timed Out

Contents

Any help is much appreciated! sg ? ). >> >> Some debugging messages from other guys: >> >> [ 3538.223529] tg3 0000:01:08.0: eth1: transmit timed out, resetting >> [ 3538.229698] tg3 0000:01:08.0: eth1: DEBUG: MAC_TX_STATUS[00000008] >> I'll post an update if I have any new issues. Ian (ibatterb) wrote on 2009-10-24: #15 It seems that the problem is specific to situations where the driver has to transmit full size packets, but does not occur when it receives http://computerhelpdev.com/timed-out/err-connection-timed-out-the-operation-timed-out.php

and I hope that someone keeps their old backups handy (I typically take one a week and keep the past month and a half). The interface affected is the routed upstream port of the system, the system doesn't do much more than to route/firewall to an internal bridge where several KVM VMs are connected to. The >> laptop ran Ubuntu 10.04 (2.6.32) since then and the problem was gone, so >> I'd say 2.6.32 fixed it. rt_mutex_trylock+0x70/0x70 > ---[ end trace 9de668a859ee5d6c ]--- > tg3 0000:02:00.0: p2p1: transmit timed out, resetting > > > -- > BOFH excuse #438: > > sticky bit has come loose > https://bugzilla.kernel.org/show_bug.cgi?id=12877

Netdev Watchdog Eth0 Transmit Timed Out

kernel: NETDEV WATCHDOG: eth1: transmit timed out kernel: tg3: eth1: transmit timed out, resetting kernel: tg3: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000008] kernel: tg3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000000] kernel: tg3: tg3_stop_block timed out, ofs=1800 enable_bit=2 This patch > makes the necessary change. > > Signed-off-by: Matt Carlson <mcarlson [at] broadcom> Ping, what's the status of this? -- To unsubscribe from this list: send the line "unsubscribe Upon doing apt-get update, it showed this: [email protected]:/# apt-get upgrade Reading package lists... remote_softirq_receive+0x20/0x20 >> >> ? ?[] ?

This laptop is mounting 2 readonly NFS shares from a box in the same LAN and when scanning lots of files on these NFS shares, the transmit timeouts occur more often, Open Source Communities Comments Helpful Follow Why NIC stops working with "tg3_abort_hw timed out, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff" messages in RHEL6? They crash! dev_watchdog+0x1cc/0x1e0 > >> ?[] ?

If this issue still exists in a supported series, please file a new bug. Tg3_abort_hw Timed Out szboardstretcher View Public Profile View LQ Blog View Review Entries View HCL Entries Visit szboardstretcher's homepage! lock_timer_base+0x2c/0x60 Jul 8 17:07:09 Alatheia kernel: [10054.000171] [] ? Get More Info The relevant dmesg entries: [ 1086.816047] ------------[ cut here ]------------ [ 1086.816057] WARNING: at /build/buildd/linux-2.6.27/net/sched/sch_generic.c:219 dev_watchdog+0x272/0x280() [ 1086.816062] NETDEV WATCHDOG: eth0 (tg3): transmit timed out [ 1086.816065] Modules linked in: af_packet

getnstimeofday+0x4b/0x100 Nov 24 18:50:43 zilla kernel: [16085.000093] [] ? better way is get another NIC, or disable some its >> feature to workaround if we got what feature block it (tso ? Jul 8 13:36:29 Alatheia kernel: [ 11.219923] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input4 Jul 8 13:36:29 Alatheia kernel: [ 11.244486] device eth1 entered promiscuous mode Jul 8 13:36:29 Alatheia kernel: [ You are currently viewing LQ as a guest.

Tg3_abort_hw Timed Out

mwait_idle+0x55/0xa0 Jul 8 12:43:24 Alatheia kernel: [ 502.000232] [] cpu_idle+0x94/0xd0 Jul 8 12:43:24 Alatheia kernel: [ 502.000239] [] rest_init+0x62/0x70 Jul 8 12:43:24 Alatheia kernel: [ 502.000245] [] start_kernel+0x356/0x35c Jul 8 12:43:24 But this is just >> >> manual observation, I haven't been able to reproduce this reliably. >> >> However, there's constant traffic on the device (maybe ~700KB/s both tx >> >> Netdev Watchdog Eth0 Transmit Timed Out After rebooting the machine, it would be fine until the next night/morning, and it would stop accepting connections again. Because of the nature of the fault (dying when full-mtu packets are sent), I tried it again with a lower MTU, and /can not get it to hang/ when MTU is

When there's sequential traffic (i.e. have a peek at these guys reading > >> larger files from the NFS shares), fewer warnings occur. Still no clue about that, I need to find someone who can connect something there. In spite of that, though, I'm going to go get another PCI NIC today and put it in the box and configure br0 to eth0 + eth2 (new card I am

mwait_idle+0x4a/0x50 Nov 24 18:50:43 zilla kernel: [16085.000139] [] cpu_idle+0x7d/0x140 Nov 24 18:50:43 zilla kernel: [16085.000142] [] rest_init+0x53/0x60 Nov 24 18:50:43 zilla kern... Please visit this page to clear all LQ-related cookies. dev_watchdog+0x1cc/0x1e0 >> >> ?[] ? http://computerhelpdev.com/timed-out/what-does-timed-out-mean-on-gta-5.php Read more...

The cheap (well lazy) fix that I took was to add a spare PCI gigabit NIC to the client machine. Kernel Bug Tracker – Bug12877 tg3: eth0 transit timed out, resetting -> dead NIC Last modified: 2016-11-29 09:32:26 UTC Home | New | Browse | Search | [?] | Reports | Need to get 0B/56.8MB of archives.

remote_softirq_receive+0x20/0x20 > [] ?

Please respond via emailed reply-to-all, not via the bugzilla web interface). I've put everything (the whole logs and more) here: http://nerdbynature.de/bits/3.4.0/tg3/ Is that what you're looking for? > Would it be possible to try a the latest kernels and get this information? set_normalized_timespec+0x16/0x90 Nov 24 18:50:43 zilla kernel: [16085.000096] [] ? Please use Jul 9 08:51:22 Alatheia kernel: [ 2974.511657] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or Jul 9 08:51:22 Alatheia kernel: [ 2974.511664] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.

For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. I'll also post back here later on today, or more likely tomorrow, to say if the system has stopped giving trouble. enqueue_task_fair+0x48/0x50 Nov 24 18:50:43 zilla kernel: [16085.000084] [] ? http://computerhelpdev.com/timed-out/ntp-timed-out.php dev_watchdog+0x1cc/0x1e0 > [] ?

But the penalty was that now all of my applications were so memory constrained their performance suffered a bit. reading larger files from the NFS shares), fewer warnings occur. Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest dev_watchdog+0x0/0x280 [ 1086.816343] [] run_timer_softirq+0x179/0x260 [ 1086.816349] [] ?

From time ago this > nic hang sometimes and the kernel reinicialized it. > NETDEV WATCHDOG: eth0: transmit timed out > tg3: eth0: transmit timed out, resetting > tg3: tg3_stop_block timed Looking at the logs, it seems as if the system itself is fine, but the eth1 (the on-board one) is giving problems. apic_timer_interrupt+0x31/0x38 > >> ?[] ? For example, my leased server is a one stop shop for website and email.

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. the 1497 MTU that worked for me two hours ago no longer works, and neither does 1496. Select a country/region: United States IBM® Site map Search Select a language Translate this page Return to English Portuguese French German Italian Japanese Korean Spanish Russian Simplified Chinese Traditional Chinese Support dev_watchdog+0x1fe/0x210 Jul 8 12:43:24 Alatheia kernel: [ 502.000141] [] ?

Device 0000 Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Brendan_P (brendan-p) wrote on 2009-09-21: #13 Screenshot-System Monitor.png Edit (60.1 KiB, image/png) Hi All, I use the tg3 driver on a Dell Studio XPS 16; "Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Red Hat Account Number: Red Hat Account Account Details Newsletter and Contact Preferences User Management Account Maintenance Customer Portal My Profile Notifications Help For your security, if you’re on a public rt_mutex_trylock+0x70/0x70 >> >> ---[ end trace 9de668a859ee5d6c ]--- >> >> tg3 0000:02:00.0: p2p1: transmit timed out, resetting >> >> >> >> >> >> -- >> >> BOFH excuse #438: >> >>

Oops. rest_init+0x66/0x70 [ 1086.816441] [ 1086.816444] ---[ end trace 0b1fb181c0127e1a ]--- [ 1086.816448] tg3: eth0: transmit timed out, resetting [ 1086.816457] tg3: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000000] [ 1086.816464] tg3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000000] [ Just my 2 cents. If not, please provide lspci -vvvxxx on the eth0 device after the failure.

run_timer_softirq+0xd1/0x1d0 > [] ? __do_softirq+0x75/0x100 > [] ? They suggest you can work around the problem by turnthing 'scatter/grather' off with: sudo ethtool --offload eth0 sg off Which appears to work but slightly reduces the maximum throughput. I have reported the error against the Fedora 17 kernel [0] but it happens with a vanilla 3.4.0 too[1] - check out for full dmesg, .config and more.