Hi Joseph,
Attached is the output of lspci -vvvnn command. This is taken on
4.13.0-041300-generic which had bnxt_en 1.7.0 driver.
** Attachment added: "attached output of lspci -vvvnn command"
Can you run: 'lspci -vvvnn' on a kernel that is working properly and
attach the output? That will give us the exact pci id's that need to be
added.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** No longer affects: linux (Ubuntu 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/1715368
Title:
Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
You don't need to test multiple kernels or perform a bisect. You know
the latest kernel has the IDs, so just run a git blame on that module
and see what commit added those new IDs to the list.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
We don't generally pull in a new version of a driver to fix a bug.
There is a document that describes the SRU process[0].
For this bug, what we would want to do is find the specific commit in the newer
driver that fixes the bug, then SRU it to the 16.04.03 kernel.
To identify the commit that
Hi Joseph,
Did we zero down on the kernel that we see this issue with.
Can we pull in the latest bnxt driver for 16.04.03 updates ?
Thanks,
Anand
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of
Joseph Salisbury
Sent: Thursday, September 21, 2017
Hi Joseph,
Yes, Ubuntu 16.04.03 has 4.4.0-87-generic kernel and we see the issue on
"4.4.0-87-generic" kernel which has "bnxt_en 0.1.24" driver.
Hi Joseph,
Yes Ubuntu 16.04.03 has 4.4.0-87-generic kernel
i tried installing all the below kernels on top of Ubuntu 16.04.03 base
The purpose of going through a "Reverse" bisect is to identify the
commit that fixes this bug and adds the proper CuW B1 device IDs. To do
that, we would want to figure out the last kernel that did not have the
ids and the first kernel that did.
However, it sounds like all the upstream kernels
Joseph,
Murali has tried with 4.4 kernel as well and even that kernel has Cu device
ID's. Can we not just pull in the latest kernel patch which is 4.13.
Thanks,
Anand
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of
Joseph Salisbury
Sent:
Can you also test the follow kernels:
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
4.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
Again, you don't have to test every kernel, just up until the
Hi Joseph,
we don't see this issue with all of the below kernels:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11
v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1
all these kernels have same
I'd like to perform a reverse bisect to figure out which commit upstream
fixes this regression. We need to figure out the last kernel that had
this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for
the last kernel version that has
12 matches
Mail list logo
