Has anyone applied the patch to the tg3 driver that was shared in
comment# 13? That one solved the issue for me. If that was the real
fix, I'd like to inform the tg3 maintainers about it so that we can have
it patched in the mainline. thanks.
tp
--
You received this bug notification because
It is confirmed, disabling HIGHDMA fixed the NIC problem. This was
tested by putting a system under load for 120+ hours, and simulated over
12TB of data through the tg3 NIC. Great find Lauri, and thank you
again!
--
You received this bug notification because you are a member of Kernel
Packages,
Lauri,
I've pumped over 1.5TB of data and have never seen the hic-up yet. I
think we've found the smoking gun. Below is a simple patch to the tigon
device driver if you prefer not to use the udev rule solution.
I believe the root cause is that the tigon net driver uses virtual
memory for DMA tr
Lauri,
Can you let me know if you've tested the work-around solution on a 64bit or
32bit OS? AFAK, HIGHMEM option only allows dma support on 64bit system (>4GB),
so I dont think it would make a difference if the native OS is 32bit. The
reason I am asking because I've tested the bug on both
Thank you for your valuable finding. I'll test your suggestion in the
next few days to confirm that it works.
I've also reported the work-around to Broadcom dev team and suggested a patch
to the tg3 driver to disable highdma. I'll keep you updated on the issue...
thank you once again.
--
Yo
Here is the bug report email to netdev mailing list:
http://www.spinics.net/lists/netdev/msg326389.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447664
Title:
14e4:1687 broadcom
** Tags added: bcm5762 broadcom kernel-bug-exists-upstream linux-4.0
lucid tg3 tigon
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447664
Title:
broadcom tg3 network driver disconnects
Guys,
I've just confirmed that this bug exist in the upstream kernel version
4.0. Attached file is the full kernel-4.0 log (from bootup to the time
the broadcom driver crashes). We may have to report this bug to a
Broadcom network driver/firmware developer. thanks
** Attachment added: "dmesg"
Please note,this bug is unrelated to Bug #1331513 b/c even if TSO, GSO
etc... are disabled, I can still re-producible it. The lock-up would
only occur under VERY_HIGH_NETWORK_LOAD, so a typical user (web-surfing
only) would not be able catch it easily. On a side note, the machine I
am testing is
Joseph,
>Did this issue start happening after an update/upgrade?
No, I also had this issue. I tested with multiple OSes and kernel versions. I
tested the issue with kernel 2.6.39,
and three Ubuntu live CDs 12.04, 14.04, and 15.04 (which was released today).
I, however, will consider testing
** Description changed:
+ The tg3 broadcom network driver that binds with chipset 5762 goes
+ offline and unable to recover (even with tg3 watchdog timeout) when
+ network transmit is under high load. Then this happens, only a reboot
+ would be able to fix it. Sometimes, however, bringing the in
Public bug reported:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) network when tx is under
high load. Then this happens, only a reboot would be able to fix it.
Sometimes, however, bringing the interface offli
I am affected by this bug on an HP 705 MT Server. It however, uses a
boardcom 6257 chipset. The bug that I am experiencing is not
recoverable, had to reboot the system to get network online again.
If anyone here needs more info, please let me know.
--
You received this bug notification because
@Wonko,
I've updated the driver to the latest version from broadcom.com, version
3.137h; and I am still experiencing a similar issue. However, when the driver
crashes, sometimes (70%) chance that the machine is useable, and another 30%
the machine is totally locked up.
The NIC i am using i
14 matches
Mail list logo
