Sorry Walter, I should have updated with info from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795092
the xubuntu 18.10 x86 has the same (or very similar) messages, but they
stop far sooner, and xubuntu drops to busybox/initramfs with an error.
I was asked by jsalisbury to do a test; wh
The bug triggered again this morning:
> modprobe -r btusb
gives
[ 6998.064598] usbcore: deregistering interface driver btusb
[ 6998.064608] usb usb1: usb auto-resume
[ 6998.064639] hub 1-0:1.0: hub_resume
[ 6998.064659] usb usb1-port2: status 0507 change
[ 6998.064674] usb usb1-port7: statu
Hmm, I guess the dmesg above was mispasted.
"modprobe -r btusb" gives
[ 6998.064598] usbcore: deregistering interface driver btusb
[ 6998.064608] usb usb1: usb auto-resume
[ 6998.064639] hub 1-0:1.0: hub_resume
[ 6998.064659] usb usb1-port2: status 0507 change
[ 6998.064674] usb usb1-port7:
Not working
--
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/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal sequence
Status
Is it possible for you to try latest mainline kernel [1]?
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/
--
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/1784878
Title:
Back
I only did a quick loot on the ACPI tables, but the brightness control
methods looks fine.
--
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/1784878
Title:
Backlight Not Functional - Origin
I could reproduce the panic with a loop of ipset destroys / swaps / restores
and then saves in another. Standard xenial machines consistently panic within a
few minutes max.
With the same loops and the proposed kernel, I got them running overnight
without any issues.
I'll check with Joel and if
This is the dmesg line with 4.15.0-34-generic (machine with 24 logical
cores).
[3.743484] i40e :67:00.0: Features: PF-id[0] VFs: 32 VSIs: 66
QP: 24 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA
I already tried it with mainline kernel 4.19-rc5, I have the same
problems with this kernel
Tested on node "rumford" with AMD64 X kernel in -released, this issue
still exist.
--
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/1793464
Title:
Kernel panic after the ubuntu_nbd_smoke_t
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags added: bloc
Private bug reported:
Business case (Partner benefit):
Dell: dcdbas driver is used to raise SMIs. Dell System BIOS will implement
support for WSMT table soon. This change in dcdbas driver will implement
support for WSMT table.
Patch details:
If the WSMT ACPI table is present and indicates that
No SATA performance regression observed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1794165
Title:
commit 534daf431c88b24236d23572039cdd79223b246a
Author: Balakrishna Godavarthi
Date: Mon Sep 17 15:29:33 2018 +0530
qca: update BT firmware files for QCA ROME chip.
This patch will resolve the Bluetooth vulnerability CVE-2018-5383
for ROME chip v3.2
Signed-off-by: Bala
Is it possible for you to attach full dmesg? i.e. everything from boot.
I'd like to check if LPM is enabled for this device.
--
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/1790454
Title:
Public bug reported:
[Impact]
The issue has been found on new Dell laptop with DW1820 combo card(BT is
[0cf3:e007])
1) Use wireless hotkey to turn off WiFi/BT.
2) Wait 5 minutes.
3) Use wireless hotkey to turn on WiFi/BT.
4) Wifi is back, but BT is still off
5) Only reboot can recovery the BT sta
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1745032
Title:
AC adapter status not detected on Asus ZenBook UX41
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-maste
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives: bug 1796641 (li
Hello Joseph,
I have checked with lp1795653 build and my problem is solved.
IPSec packets are not translated anymore when passing thru a L2 tunnel.
Thanks,
Boris
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
** Tags removed: originate-from-1789327 somerville
** Tags added: originate-from-1783927 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1796634
Title:
[0cf3:e007] Ca
** Description changed:
- This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM node
-
+ This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM
+ node
+
The test itself will pass, but the system will hang after a few second.
Steps:
- 1. Deploy a node
** Changed in: kernel-sru-workflow/automated-testing
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/1796346
Title:
linux: 4.18.0-9.10 -proposed tra
** Changed in: kernel-sru-workflow/automated-testing
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/1795564
Title:
linux: 4.15.0-37.40 -proposed tr
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1795618
Title:
linux-gcp: 4.18.0-1001.2 -pr
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1795567
Title:
linux-aws: 4.15.0-1024.24 -p
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1795571
Title:
linux-gcp: 4.15.0-1022.23 -p
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1795566
Title:
linux-oem: 4.15.0-1022.25 -p
I've no clue in which kernel version it started...
--
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/1794067
Title:
Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
Status in linux pac
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1795492
Title:
linux-aws: 4.18.0-1001.2 -pr
You are using 4.18.12-041812-generic, which is not a supported kernel. You
can uninstall the nvidia driver doing the following:
sudo apt-get --purge remove libnvidia* nvidia-*
On Sun, 7 Oct 2018 at 14:55, Unkraut <1778...@bugs.launchpad.net> wrote:
> Please add rollback instructions. I'm now stu
Can reproduce this on a -133 xenial kernel too on Xenial VM. After the
test, I ran vmstat 1 and observed the machine just hang after ~20 or so
seconds.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided
And occurs way back to 4.4.0-21 too.
--
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/1793464
Title:
Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel
Status in ubuntu-kernel-
Since bionic-updates containes kernel 4.15.0-36. and git says that 's390:
detect etoken facility' is included:
$ git log --oneline | grep "s390: detect etoken facility"
cffc6b1 s390: detect etoken facility
$ git tag --contains cffc6b1
Ubuntu-4.15.0-35.38
Ubuntu-4.15.0-36.39
Ubuntu-4.15.0-37.40
Ubu
Since cosmic contains kernel 4.18.0.8.9 and git says that 's390: detect etoken
facility' is included:
$ git log --oneline | grep "s390: detect etoken facility"
edb9bc2 s390: detect etoken facility
$ git tag --contains edb9bc2
Ubuntu-4.18.0-8.9
Ubuntu-4.18.0-9.10
Ubuntu-raspi2-4.18.0-1004.4
Ubuntu-
And just for the records, the kernel part already landed in xenial, too:
xenial updates kernel today: 4.4.0.137.
$ git log --oneline | grep "s390: detect etoken facility"
c32821c s390: detect etoken facility
$ git tag --contains c32821c
Ubuntu-4.4.0-136.162
Ubuntu-4.4.0-137.163
Ubuntu-4.4.0-138.164
Course sanity check with mainline kernels:
4.2 OK
4.3 hangs
4.4 hangs
4.5 hang
4.6 - 4.8 no hang, but dumps message (see below)
4.9 OK
Oct 8 11:04:03 ubuntu kernel: [ 31.788232] block nbd0: NBD_DISCONNECT
Oct 8 11:04:03 ubuntu kernel: [ 31.788286] block nbd0: shutting down socket
Oct 8 11:
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
** Tags removed: kernel-release-tracking-bug-live
--
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/1796319
Title:
linux: -proposed tracker
Status in Kernel SRU Workflow:
Invalid
Status
** Tags removed: kernel-release-tracking-bug-live
--
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/1796084
Title:
linux-aws-edge: 4.18.0-1001.1~18.04.1 -proposed tracker
Status in Kernel
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1796323
Title:
linux-azure: -proposed tracker
Status in Kernel SRU Workflow:
In
** Also affects: linux-oem (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu Bionic)
Status: New => Confirmed
** Tags removed: kernel-sru-cycle-kernel-sru-cycle-2018.10.01-1
** Tags added: kernel-sru-cycle-kernel-sru-cycle-2018.10.01-2
--
You re
Public bug reported:
computer freezes, no more movement, force to power of and restart,,,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion:
** Summary changed:
- linux-oem: -proposed tracker
+ linux-oem: 4.15.0-1023.26 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =
This bug was fixed in the package nvidia-settings -
390.77-0ubuntu0.18.04.1
---
nvidia-settings (390.77-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release.
* 08_add_prime_support.patch:
- Recommend a simple log out (LP: #1778011).
-- Alberto Milone Thu, 02 Aug
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu25
---
zfs-linux (0.6.5.6-0ubuntu25) xenial; urgency=medium
* Fix zpl_mount() deadlock (LP: #1781364)
- Upstream ZFS fix ac09630d8b0b ("Fix zpl_mount() deadlock")
fixes deadlock on multiple parallelized mount/umo
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.77-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.77-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release:
- Improved compatibility with recent Linux kernels.
- Fixed an intermittent hang o
This bug was fixed in the package ubuntu-drivers-common - 1:0.5.2.1
---
ubuntu-drivers-common (1:0.5.2.1) bionic; urgency=medium
* debian/rules:
- Make sure to remove "__pycache__" directory.
* debian/source/options:
- Ignore the "__pycache__" directory.
* gpu-manager.(c
This bug was fixed in the package nvidia-prime - 0.8.8.1
---
nvidia-prime (0.8.8.1) bionic; urgency=medium
[ Alberto Milone ]
* 90-nvidia.conf,
debian/rules,
prime-select:
- Make sure to remove the old blacklist file.
- Use /lib for blacklist-nvidia.conf.
- Do
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/bugs/1796659
Title:
ubuntu freezes compleet
Statu
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1793702
Title:
linux-lts-trusty: -proposed tracker
Status in Kernel SRU Work
It's definitely NOT happening while supending/resuming.
It happens while I'm using the machine, literally while moving the mouse.
--
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/1796553
Tit
Bluetooth adapter is builtin. so I can't change the port.
--
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/1796553
Title:
BT mouse getting reset during operation
Status in linux package i
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1793700
Title:
linux-lts-trusty: -proposed tracker
Status in Kernel SRU Work
** Tags removed: kernel-sru-cycle-kernel-sru-cycle-2018.10.01-2
** Tags added: kernel-sru-cycle-2018.10.01-2
** Tags removed: kernel-sru-derivative-of-1796640
** Tags added: kernel-sru-derivative-of-1795564
** Description changed:
This bug is for tracking the upload package. This
bug will c
Ok, please use v4.19-rc6 or rc7, and boot with kernel parameter
"usbcore.quirks=8087:0a2b:k" which disables LPM for the Bluetooth
device, and see if this issue still persists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Sure, here it is.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198582/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
*** This bug is a duplicate of bug 1796641 ***
https://bugs.launchpad.net/bugs/1796641
** This bug has been marked a duplicate of bug 1796641
linux-oem: -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem i
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794435
Title:
linux-azure: -proposed tracker
Status in Kernel SRU Workflow:
In
IBM tested and verified this fix upfront.
Hence adjusting tags accordingly.
** 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.
Course bisect, fixed between 4.8 and 4.9
--
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/1796250
Title:
sysfs test ubuntu_stress_smoke_test will cause kernel oops on
X-lowlatency
Statu
Hi Guo, the Ubuntu kernels schedule can be checked here:
https://wiki.ubuntu.com/Kernel/Support .
Ubuntu kernel team chooses a kernel version for a specific release, and
once that release is available, there's a support schedule. Some
versions have long-term support, so they're called LTS.
In par
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
With kernel 4.19rc7 and the kernel parameter as you prescribed, the BT adapter
won't work at all. The timeouts that would only occur sporadically after
resume, are now present from boot, and the previous
unload-modules/suspend/resume/load-modules cycle no longer works to get BT back
on.
Dme
** Attachment added: "dmesg-4.19rc7.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198639/+files/dmesg-4.19rc7.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
I think tlp was responsible for the issue, as after uninstalling it, I
could not reproduce it consistently (only happens very rarely).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1788807
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.15.0-1024.25~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canoni
Some extra information: a tool to reproduce the problem is available in
the linux-block mailing list: https://www.spinics.net/lists/linux-
block/msg28507.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
** Changed in: ubuntu-z-systems
Status: Fix Committed => 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/1790457
Title:
kernel: improve spectre mitigation
Status in U
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.6
---
qemu (1:2.11+dfsg-1ubuntu7.6) bionic; urgency=medium
[ Christian Ehrhardt ]
* Add cpu model for z14 ZR1 (LP: #1780773)
* d/p/ubuntu/lp-1789551-seccomp-set-the-seccomp-filter-to-all-threads.patch:
ensure that
** Tags added: kernel-bug-reported-upstream
--
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/1794763
Title:
High utilisation of memory freezes Ubuntu completely for a long time,
with an
** Changed in: systemd (Ubuntu Xenial)
Status: New => 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/bugs/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priority P
As this ticket only relates to Xenial and 4.4 kernel, marking as "Fix
Released".
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a me
This is now broken also on Hyper-V VMs, tested with 4.18.0-8-generic and
daily 18.10 server
--
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/1794477
Title:
[Azure] Accelerated networking b
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
That already in the current cosmic kernel:
$ git log --oneline | grep "Check if IOMMU page is contained in the pinned
physical page"
76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page
$ git tag --contains 76fa497
Ubuntu-4.18.0-7.8
Ubuntu-4.18.0-8.9
Ubuntu-4.18.0-9.10
v4
Since we are already on kernel 4.18.0.8.9 in cosmic that incl. the mentioned
patches:
$ git log --oneline | grep "Check if IOMMU page is contained in the pinned
physical page"
76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page
fheimes@T570:~/ubuntu-cosmic$ git tag --co
Since we are at kernel level 4.18.0.8.9 in cosmic that incl. the fix:
$ git log --oneline | grep "cpuidle: powernv: Fix promotion from snooze if next
state disabled"
0a4ec6a cpuidle: powernv: Fix promotion from snooze if next state disabled
$ git tag --contains 0a4ec6a
Ubuntu-4.18.0-7.8
Ubuntu-4.1
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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 is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008
Hello,
Was able to get this to load.
This is a new install of ubuntu 18.04.
Had to run the "install -f" cmd a few times, then the updates worked.
Mark Dannunzio
> On October 7, 2018 at 10
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-cosmic
** Tags removed: block-proposed
--
You received this bug notification becau
Marking as "Incomplete" while waiting for test kernel results to be
posted.
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Marking as "Incomplete" while waiting for test kernel results to be
posted.
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Changed in: ubuntu-power-systems
Status: Triaged => 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/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
Hmmm, do you still see this if you cold boot with the quirk?
--
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/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
Status
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => 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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Pr
There's something wrong going on here. I first reported this issue as a
'linux' bug, based on a hasty reading of documentation. I never
finished that report, so I expect that to be incomplete.
Shortly afterwards I re-reported it as a probable NetworkManager issue.
It seems that these two issues
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc7 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 f
** Bug watch added: Linux Kernel Bug Tracker #201291
https://bugzilla.kernel.org/show_bug.cgi?id=201291
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=201291
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Thanks for all the testing, Chris. It leaves me a little baffled.
That said, to Joseph et al, two questions:
1. This seems to be the same messages from 1794922 but slightly different
symptoms. Should they be considered as the same?
2. With the kernel apparently working in Bionic, that suggests
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that up
The error appears to be different that the error posted in the bug
description. The descriptions mentions a tx_timeout. Are you seeing
that error still as well?
Also, the descriptions seems to indication this is a regression. Was
there a specific prior kernel version that did not exhibit this b
Hello,
It would be possible to create this report with:
$ ubuntu-bug linux
To add all the necessary technical information
Thanks for helping to create a better Ubuntu...
--
Cristian Aravena Romero (caravena)
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Incomple
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.19-rc7 kern
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
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.19-rc7 kern
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1795583
Title:
linux-aws: 4.4.0-1032.35
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => 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/bugs/1764087
Kai-Heng Feng: I did some more testing and I don't see the problem in the
cosmic proposed kernel 4.18.0-9.10.
1) the live CD appeared to boot fine, but I didn't totally trust the test
procedure.
2) I installed cosmic 4.18.0-9.10 from
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/u
1 - 100 of 173 matches
Mail list logo
