@Roland Sommer
Can you check which board revision do you get?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications about this bug go to:
I got a replacement board and the error seems to have gone. I did run
iperf for over an hour and no hanging was detected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected
Answer from asrock...
i think that this is more of an issue with the Kernel. I can ask the engineers
to look into it but as this OS is not on the tested list this does not warranty
an rma.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The "no longer affects" is not correct, but the assignment to the
correct source package was wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-lts-xenial (Ubuntu)
** No longer affects: linux-lts-xenial (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I just tried booting with pcie_aspm=off. It took 7 seconds until freeze
after starting iperf. The funny thing is, that i'm using the igb-driver
on the other side of the test, but on an I354 controller.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You can try to compile a dkms igb driver.
My solution is to run the working 3.2 kernel on Debian wheezy
I read something that the kernel pcie code was updated on nwer kernel.
The igb on the bridge chip PLX 8608 has problems
You can try the following
pcie_aspm=off
I am using the C2550. I just tried the "disable intel speedstep and
C-state" hint but within 60 seconds i got the tx unit hang again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
Hi rsommer,
you use the Asrock C2550D4I?
Currently i am hunting the same problem on Ubuntu and on Debian
Some related links: ...
https://sourceforge.net/p/e1000/bugs/424/
http://enira.net/?p=709
http://forums.tweaktown.com/asrock/56730-c2750d4i-stability-problems-2.html
Hi, i'm encountering the same/similar bug on xenial 4.4.0-28-generic. If
i apply network load via iperf i get the unit (Intel 210i) reproducible
to hang. Maybe this is a regression or another bug. The network
interface does not recover, i have to reboot the machine to get it back
online. dmesg
** Changed in: linux-lts-utopic (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications
My server has now been running on this kernel (3.16.0-56-generic) for
over 48 hours with no recurrence of the igb Tx Unit Hang.
I think we can say it's working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My server has been running on this kernel (3.16.0-56-generic) for almost
24 hours now with no recurrence of the igb Tx Unit Hang.
I'm still monitoring, but it looks like this kernel is stable on my
server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have installed linux-
image-3.16.0-56-generic_3.16.0-56.75~14.04.1_amd64.deb and linux-image-
extra-3.16.0-56-generic_3.16.0-56.75~14.04.1_amd64.deb from
http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/
It's been running without issues for significantly longer than the
Thanks again for testing, Mark. I've created on more test kernel. This
kernel makes no changes to the igb code at all. So if the bug does not
exist with your current up to date kernel, it shouldn't occur with the
test kernel.
Could you and any other folks affected by this bug test my new test
Sorry to report that I have the same issue after installing linux-
image-3.16.0-55-generic_3.16.0-55.74~14.04.1_amd64.deb and linux-image-
extra-3.16.0-55-generic_3.16.0-55.74~14.04.1_amd64.deb from
http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/
--
You received this bug
@Mark
Thanks for testing my last kernel and confirming the regression still
exists.
I've created one more test kernel for bug 1454892. Could you and any
other folks affected by this bug test my new test kernel? It can be
downloaded from:
The igb clash appears sporadically, once in two days or so. I can't reliably
reproduce it - only by waiting for couple of days until it breaks.
We seeing that in Ubuntu 14.04 with xen hypervisor 4.4.2-0ubuntu0.14.04.3
installed.
--
You received this bug notification because you are a member of
Hello,
any news on this one? We also expecting this problem on two servers -
with kernel 3.19.0-33-generic #38~14.04.1-Ubuntu. Anything we can do to
make this fixed asap? I'm open to any tests. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for your help testing, Mark. I'll investigate further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications about this bug go to:
The commits that caused this bug were introduced by the fixes for bug
1454892.
I've created a new test kernel for bug 1454892, but I would like to
ensure it does not introduce this regression again. Could folks
affected by this bug test my new test kernel? It can be downloaded
from:
I spoke too soon. It took about 20 minutes for the issue to develop, but
it has reappeared just as before with the new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb
I have installed
linux-image-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb and
linux-image-extra-3.16.0-52-generic_3.16.0-52.71~14.04.1_amd64.deb
from http://kernel.ubuntu.com/~jsalisbury/lp1454892/lts-backport-utopic/
and rebooted and I do not see the issue reported in this bug. It appears
Tested 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9 10:03:23 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Looks stable for this issue: 523 packets transmitted, 523 received, 0% packet
loss, time 526808ms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9 10:03:23 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux from trusty/proposed. Looks stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
As per comment #21, I'm tagging this bug as verified.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug was fixed in the package linux-lts-utopic -
3.16.0-49.65~14.04.1
---
linux-lts-utopic (3.16.0-49.65~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1493759
[ Upstream Kernel Changes ]
* Revert "hv_netvsc: Use the xmit_more skb
This bug was fixed in the package linux-lts-utopic -
3.16.0-49.65~14.04.1
---
linux-lts-utopic (3.16.0-49.65~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1493759
[ Upstream Kernel Changes ]
* Revert "hv_netvsc: Use the xmit_more skb
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage
@boot0user I agree with you. The best workaround for now is to update
kernel to Vivid!
# Physical Server (with EFI):
sudo apt-get -y purge linux-{headers,image}-3.16.0-48-generic
sudo apt-get -y install linux-signed-generic-lts-vivid
sudo reboot
uname -r # 3.19.0-26-generic
sudo apt-get -y purge
Same problem here with
Dell Inc. PowerEdge R730/0H21J3, BIOS 1.2.10 03/09/2015
and
Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
Renders the machine useless.
Kernel 3.16.0-43 is OK
--
You received this bug notification because you are a member of Ubuntu
I have the same problem
FUJITSU Server PRIMERGY RX1330 M1
-cpu
product: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
size: 3100MHz
capacity: 3100MHz
width: 64 bits
-network
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux-lts-utopic (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe the problem lies in a bad backport in a set of patches for
hyper-v. I've uploaded a test kernel that simply reverts this hyper-v
patchset. Here's the URL:
http://people.canonical.com/~henrix/lp1492146/v1/amd64/
Could anyone please see if this kernel solves the issue? Thanks!
**
I believe the problem lies in a bad backport in a set of patches for
hyper-v. I've uploaded a test kernel that simply reverts this hyper-v
patchset. Here's the URL:
http://people.canonical.com/~henrix/lp1492146/v1/amd64/
Could anyone please see if this kernel solves the issue? Thanks!
--
** Also affects: linux-lts-utopic (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage
3.16.0-48-generic #64~14.04.1~lp1492146v1 SMP Tue Sep 8 13:08:54 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux runs stable for ~1h.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb
sudo apt-get -y purge linux-{headers,image}-3.16.0-48-generic
sudo apt-get -y install linux-generic-lts-vivid
sudo reboot [0]
-
linux-headers-3.16.0-46 linux-headers-3.16.0-46-generic
linux-headers-3.16.0-48 linux-image-3.16.0-46-generic
Use 'apt-get autoremove' to remove them.
I'm, personally, prefer to install a new kernel by running "apt-get
install linux-signed-generic-lts-vivid".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
I have the same problem with Intel I210AT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications about this bug go to:
This bug should be a top priority because people will suffer from it as soon as
they reboot
their 14.04 LTS with an Intel Gigabit NIC and the "current" Utopic kernel
(3.16.0-48-generic).
I had the same problem with HP ProLiant DL380e Gen8 which an Intel I350 Gigabit
NIC
(Hewlett-Packard
Same bug as https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1488024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications
Maybe it's another kernel regression with Intel NIC and TSO
so you can try this :
# tso => tcp-segmentation-offload
# gso => generic-segmentation-offload
# gro => generic-receive-offload
# sg => scatter-gather
# ufo => udp-fragmentation-offload (Cannot change)
# lro => large-receive-offload
I'm trying ethtool -K em1 tso off gso off lro off and it's doesn't
help.
igb driver version is the same in 46 and 48 version of kernel. Seems
that something changed in the kernel but not in the igb driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If directly related to igb module maybe this
LP: #1465653
https://lists.ubuntu.com/archives/kernel-team/2015-June/058671.html
https://lists.ubuntu.com/archives/kernel-team/2015-June/058586.html
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465653
if not directly related to igb modules
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
I have the same problem. The same driver, distro, kernel. Had to revert
to older kernel. My motherboard with the NICs is X9DRD-7JLN4F.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
I have very similar issue running in hyper-v. Networking stop after a
minute or two. Reverting back to 3.16.0-46 fixes he issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb
I have the same issue with similar kern.log entries after upgrading to
kernel 3.16.0-48. Removing that and falling back to 3.16.0-46 fixed it
for me.
** Attachment added: "Excerps from kern.log, lshw, ifconfig"
** Description changed:
Hello!
Have a:
>lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename: trusty
with kenel 3.16.0-46-generic.
Today i do dist-upgrade and kernel was upgraded
** Description changed:
Hello!
Have a:
>lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename: trusty
with kenel 3.16.0-46-generic.
Today i do dist-upgrade and kernel was upgraded
** Description changed:
Hello!
Have a:
>lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename: trusty
with kenel 3.16.0-46-generic.
Today i do dist-upgrade and kernel was upgraded
53 matches
Mail list logo