This bug was fixed in the package linux - 3.13.0-144.193
---
linux (3.13.0-144.193) trusty; urgency=medium
* linux: 3.13.0-144.193 -proposed tracker (LP: #1755227)
* CVE-2017-12762
- isdn/i4l: fix buffer overflow
* CVE-2017-17807
- KEYS: add missing permission check fo
This bug was fixed in the package linux - 4.4.0-119.143
---
linux (4.4.0-119.143) xenial; urgency=medium
* linux: 4.4.0-119.143 -proposed tracker (LP: #1760327)
* Dell XPS 13 9360 bluetooth scan can not detect any device (LP: #1759821)
- Revert "Bluetooth: btusb: fix QCA Rome
Hi,
We do ship an iso for ppc64le for Trusty - I'm not sure whether it does
bare metal/PowerNV or just as an LPAR under PowerVM, but it's probably a
bit moot at this point.
The good news is that as you can see, the artful kernel was released with the
fix.
The Xenial kernel also contains the fix;
This bug was fixed in the package linux - 4.13.0-38.43
---
linux (4.13.0-38.43) artful; urgency=medium
* linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)
* Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter prog
I didn't think Trusty would even run baremetal on ppc64el?
--
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/1715519
Title:
bnx2x_attn_int_deasserted3:4323 MC assert!
Status in linux packa
Fantastic!
If I understand correctly, that is sufficient for verification-done-
artful, so I am changing that over for you.
The one remaining kernel is Trusty 3.13. I am guessing your module
doesn't compile for that? If it doesn't, there probably isn't much point
on booting with just a virtual et
Full test passes. No crash with proposed hwe-16.04 kernel and tso/gso
enabled.
--
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/1715519
Title:
bnx2x_attn_int_deasserted3:4323 MC assert!
S
After conferring with the IBM Novalink dev team, we found a way to
exploit some undocumented preliminary artful support in the DKMS, to
successfully install the hwe-16.04 kernel (4.13.0-38) from xenial-
proposed. It boots and passes traffic. I hope to report back later today
or possibly tomorrow wi
These Linux LPARs are running Novalink, in a mode that allows them to
serve in place of the traditional PowerVM AIX VIO server. So they're
providing virtual I/O for other LPARs (this is how we ended up sending
64k packets into the bnx2x nics via open vswitch). The DKMS modules
enable that function.
Hi,
Thanks for the Xenial test!
The kernel team process is that patches will always be committed from
the most recent kernel first and then back to older kernels, so that no-
one ends up with a regression if they upgrade to a more recent kernel.
So if it is applied to Xenial it will be applied to
We're not set up to test the artful kernel, but I can envision a near-
to-mid-term future where we will need this patch to be present in the
artful kernel. What's the best way for me to help make sure that future
obtains?
--
You received this bug notification because you are a member of Kernel
Pa
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1715519
Title:
bnx2x_attn_int_deasserted3:4323 MC asser
Our validation tests pass with tso/gso enabled and 4.4.0-117 (no crash).
We'll do a couple more tests but it's looking good so far.
--
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/1715519
T
I was able to install the ppc64el 4.4.0-117 kernel from xenial-proposed.
It boots and passes at least enough traffic to make an interactive ssh
session function.
I'm having some DKMS issues, however, which are preventing me from
validating the patch prevents crash as expected (one of the modules w
Ok, that works. I should be able to provide basic validation much more
easily.
We are having trouble reproducing the crash with the unpatched kernel,
as we've put many remediating workarounds in place and it's been an
adventure to remember where they all are and how exactly they all
interacted (an
Hi,
As well as Po-Hsu's comment above, I also have this internal update from
the kernel team:
As this is also a security fix, don't stress too much. If things
could be verified for at least for one of the kernels until next week
that is better than nothing. We are rather unlikely rip out fixe
In addition to what Po-Hsu Lin and Daniel Axtens said, to have each of
the kernels test-booted and checked for obvious regressions would be
great and if in addition one of those can be tested for the reported
problem being fixed, then this is sufficient. But mainly this procedure
is to ensure we d
Hello r.stricklin,
The planned SRU schedule this cycle
* Current cycle: 09-Mar through 31-Mar
09-Mar Last day for kernel commits for this cycle.
12-Mar - 17-Mar Kernel prep week.
18-Mar - 30-Mar Bug verification & Regression testing.
02-Apr Rele
Hi,
I am the support engineer on the Canonical side who has been working on
this with IBM Support on your behalf. Apologies for the confusion. I
will contact our kernel team now and get this clarified for you as soon
as I can.
Now, I can't speak for the kernel team or make any commitments on thei
I am the end user who originally reported this problem. We have been
working with Canonical through IBM Support to get this problem resolved
-- When I last spoke with IBM about this a few weeks ago, I got the
impression we'd have a little extra time to perform verification (e.g.
the test period wou
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New =
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
** Description changed:
SRU Justification
=
A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
card attached, and uses openvswitch to bridge an ibmveth interface for
traffic from other LPARs.
We see the following crash sometimes when running ne
This has been assigned CVE-2018-126.
** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-126
** Description changed:
SRU Justification
=
A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
card attached, and uses openvswitch to
** Description changed:
SRU Justification
=
A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
card attached, and uses openvswitch to bridge an ibmveth interface for
traffic from other LPARs.
We see the following crash sometimes when running ne
** Description changed:
- (This bug provides a place to track the progress of this issue upstream
- and then in to Ubuntu.)
+ SRU Justification
+ =
A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
card attached, and uses openvswitch to bridge an ibmveth
A set of 2 patches to fix this was accepted upstream:
https://github.com/torvalds/linux/commit/2b16f048729bf35e6c28a40cbfad07239f9dcd90
https://github.com/torvalds/linux/commit/8914a595110a6eca69a5e275b323f5d09e18f4f9
I will send an SRU shortly.
--
You received this bug notification because you
31 matches
Mail list logo
