** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about
[Expired for linux (Ubuntu Vivid) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Vivid)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu Trusty) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu Utopic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Utopic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been stable on all systems for quite some time now. I don't
know what fixed it. It might be the SR-IOV thing. I'm marking it
Incomplete, since I can't reproduce it any more.
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Trusty)
The production system has been stable for a week. I suspect the problem
is fixed.
I recall reading something where someone was having trouble with an
ixgbe NIC, and they turned on SR-IOV in the BIOS. I rebooted the server
with Trusty today during maintenance and took screenshots of the BIOS
It's been fine with two different high traffic guests. We have generic-
receive-offload disabled now, to fix a different problem (it breaks IPv6
PMTUD when bridging). Maybe that's it. But when I was testing (for
comment #13), I did try leaving gro enabled and I still couldn't
reproduce the
Thanks for all the testing rlaager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
I've put a (less critical) production guest back on this system to see
if that reproduces the problem. If it's stable, I'll move the mission
critical guest (the one that typically reproduced the problem in the
past) over. Maybe that'll help narrow it down.
--
You received this bug notification
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because
I reinstalled Trusty from scratch and I still can't reproduce it. It's
always been somewhat intermittent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC
I do see some a kernel log entry that says audit_printk_skb: 42
callbacks suppressed, but definitely no stack dumps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel
I tested with this for some time tonight. I couldn't reproduce the
issue. In the past, for some reason, it's been easier (or only
possible?) to reproduce with a fresh install of Trusty. I'm going to
reinstall Trusty tomorrow and re-test.
--
You received this bug notification because you are a
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go
I haven't had a chance to test yet, but I will soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These commits may address the issue based on the stacktrace:
d4bcef3fbe887ff93b58da4fcf6df1eee416e8fa
72b1405964c19b99ad9f75340249b16305cf31ab
0213668f060ea966ee8f4e6334f0fd27b6a1c428
10e4fb333c9ad72491f80bed018f8007e17060d1
53d6471cef17262d3ad1c7ce8982a234244f68ec
I have test build here for
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
I did a fresh install of Trusty, and then I was able to reproduce this
again tonight.
I upgraded the kernel to linux-image-3.19.0-031900rc3-generic from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc3-vivid/ I had to
stop cgmanager and unmount the cgroups filesystem again to get the
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC
Unfortunately, my test case isn't 100% reproducible. I haven't changed
anything, but I have been unable to reproduce the problem tonight, even
on the stock Trusty kernel.
On the mainline kernel, I can't get the VM to start at all unless I unmount the
cgroups filesystem to force libvirt to not
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Using 3.4.0-1.2 from Quantal (the earliest non-3.2 kernel that built)
yields the same skbuff error (not the stack trace as on Trusty).
Using 3.7.0-0.5 from Quantal (the earliest non-3.5 kernel that built)
also yields the same skbuff error.
The problem persists even after upgrading the BIOS to 2.0c, so I've
removed the bios-outdated-2.0c tag.
** Tags removed: bios-outdated-2.0c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
The kernel from Precise (3.2.0-74.109) works (on a Trusty system).
On 3.5.0-51-generic (3.5.0-51.76) from Quantal, I get a different kind of
brokenness. I don't get a stack dump, but I get this kernel message printed:
skbuff: bond0.7: received packets cannot be forwarded while LRO is enabled
** Tags added: bios-outdated-2.0c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
** Tags added: regression-release
** Tags added: utopic
** Description changed:
I posted this to net...@vger.kernel.org as well:
http://www.spinics.net/lists/netdev/msg309110.html
I think the next step is to try to bisect this down to a specific commit. I'm
starting to look at the
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this
29 matches
Mail list logo
