I built a test kernel with a revert of commit
de3ef1eb1cd0cc3a75f7a3661e10ed827f370ab8. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
nassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
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
I'd like to perform a "Reverse" bisect to figure out what commit fixes
this bug. We need to identify the last kernel version that had the bug,
and the first kernel version that fixed the bug.
Can you test the following kernels and report back:
4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mai
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1762353
Title:
Bionic request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091481.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/1762353
Title:
[Ubuntu 18.04] cryptsetup: 'd
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Released
--
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/1754911
Title:
b44 Ethernet driver not working in Linux 4.15 on
I built a 16.04(4.4 based kenrel) with the requested patch.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761674/xenial
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
linux-image-
I built a second test kernel with a revert of commit
de3ef1eb1cd0cc3a75f7a3661e10ed827f370ab8. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
Can you test this kernel and see if it resolves this bug?
If it does not, I'll build the test kernel with these c
Thanks for testing. I should have the next kernel ready for testing
shortly.
--
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/1745646
Title:
Battery drains when laptop is off (shutdown)
I built another test kernel with a revert of the following commits:
0ce3fca PCI / PM: Restore PME Enable after config space restoration
de3ef1e PM / core: Drop run_wake flag from struct dev_pm_info
0847684 PCI / PM: Simplify device wakeup settings code
The test kernel can be downloaded from:
http
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Linux-next commit 2be8ffed093b91536d52b5cd2c99b52f605c9ba6 does not
apply cleanly to v4.15. The commit was cc'd to upstream stable, but
without a backport. I'd like to see what upstream stable applies for a
backport.
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
** Ta
I started a kernel bisect between v4.15-rc2 and v4.15-rc3. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
78d9b048446c3c0a83313444fb706f8f3bccdae7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsali
If this issue still also exists on v4.16-rc4, we would also want to test
some of the newer release candidates, such as -rc5, -rc6, etc.
--
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/176172
I built another test kernel with a revert of the following commits:
0ce3fca PCI / PM: Restore PME Enable after config space restoration
de3ef1e PM / core: Drop run_wake flag from struct dev_pm_info
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
Can you tes
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Incomplete
** Also affects: install-package (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags added: kernel-key
** Changed in: linux (Ubuntu
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kerne
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1759787
Title:
Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with ker
** Tags removed: kernel-key
--
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/1734130
Title:
[18.04 FEAT] Add kvm_stat from kernel tree
Status in Ubuntu on IBM z Systems:
In Progress
Sta
** Tags removed: kernel-key
--
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/1761626
Title:
[regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Status in linux package in Ubuntu:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Also affec
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Also affec
Bionic request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091525.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/1762928
Title:
[LTC Test] Ubuntu 18.04: tm_t
Bionic request:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091528.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/1762913
Title:
[OPAL] Assert fail:
core/mem_region.c
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Can you see if the bug happens with and of these mainline kernels? We
can perform a kernel bisect if we can narrow down to the last good
kernel version and first bad one:
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1762725
The Bionic request has been sent. However, because Artful is a stable
release, it requires testing before submitting a SRU request.
I built an Artful test kernel with commit
47712a921bb781caf69fca9eae43be19968816cb. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/l
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
** This bug has been marked a duplicate of bug 1759920
intel-microcode 3.20180312.0 causes lockup at login screen(w/
linux-image-4.13.0-37-generic)
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
** This bug has been marked a duplicate of bug 1759920
intel-microcode 3.20180312.0 causes lockup at login screen(w/
linux-image-4.13.0-37-generic)
--
You received this bug notification because you are
Can you next test -rc5 and -rc7:
v.16-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc5/
v.16-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
I built one more test kernel with a revert of the following commits:
0ce3fca PCI / PM: Restore PME Enable after config space restoration
0847684 PCI / PM: Simplify device wakeup settings code
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
Can you test this
I built the first test kernel, up to the following commit:
6a5e05a47b6cb8e59bfad351444322b1e4012326
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761751
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Thanks for finding the mainline 4.10 does not have the bug and 4.11
final does. Can you also test v4.11-rc1, so we can find which release
candidate introduced the bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1
--
You received this bug notification because you are a member of Kerne
=> In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Artful)
Assignee: Canonical Kernel
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Ch
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Changed in: linux (Ubuntu Bionic)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Changed in: linux (U
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
**
I built a Bionic test kernel with commit 510c321. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746474/bionic
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .de
Hi Rafael,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following two commits resolved
this bug:
0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration")
0847684cfc5f("PCI / PM: Simplify device wakeup settings code"
Whoops, yes, the last kernel was the second.
I built the next test kernel, up to the following commit:
2391f0b4808e3d5af348324d69f5f45c56a26836
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761751
--
You received this bug notification because you are a member o
Thanks for testing. I would have thought 4.4 with the Artful configs
would not have had the bug if a config change is the fix.
We know:
4.12-rc4 with Artful configs is good.
4.12-rc4 with Xenial configs is bad.
Any kernel with Xenial configs is bad.
It is possible a patch in combination to a co
@Gopal, can you confirm the answer to Rafaels question in comment #85.
Your system is physically powered off and not suspended, correct?
--
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/17456
On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
> wrote:
>> Hi Rafael,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following tw
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
>>>> Hi Rafael,
>&g
I built the next test kernel, up to the following commit:
af57b7fffaf74ff337e479abb19026d72065673b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761751
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => In Progress
--
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/1761674
Title:
[Ubuntu 16.04] kernel: fix rwlock implementati
*** This bug is a duplicate of bug 1763755 ***
https://bugs.launchpad.net/bugs/1763755
** This bug has been marked a duplicate of bug 1763755
'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p' after the
kernel upgrade
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4)
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
linux-image and
linux-image-extra .deb packages.
Thanks in advance!
** Changed in: linux (Ubuntu Artful)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
As
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Thanks for the 4.13 back ports. I built an Artful test kernel with your
patches.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761674/artful
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a memb
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in:
I built Artful and Bionic test kernels with commit
f212bf9abe5de9f938fecea7df07046e74052dde. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1764194/artful
http://kernel.ubuntu.com/~jsalisbury/lp1764194/bionic
Can you test this kernel and see if it resolves this b
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
201 - 300 of 17733 matches
Mail list logo
