** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1836031
Title:
[SRU][B/B-OEM]Fix resume failure on some TP
The test result on AMD64:
startup='Tue Jul 9 14:23:18 2019'
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP
prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed
prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: New =>
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1767992
Title:
Linux md raid-10 freezes during resync
Sta
Public bug reported:
This failure was only spotted on PowerPC (node "modoc"), it has passed
with AMD64 / i386, entirely skipped on ARM64.
startup='Mon Jul 15 22:48:25 2019'
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP
prctl04.c:12
Does kernel parameter "i8042.nomux=1" help?
--
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/1836474
Title:
dell touchpad not working
Status in linux package in Ubuntu:
Confirmed
Bug d
I could see this failing on Trusty ARM64 Moonshot node, but not the ppc64le
node "modoc":
startup='Tue Jul 9 07:45:17 2019'
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.
Upstream stable 4.4.181 had many brcmfmac updates. From the trace
suspicious seems:
brcmfmac: revise handling events in receive path
commit 9c349892ccc90c6de2baaa69cc78449f58082273 upstream.
which has a fixup upstream that sounds like the issue:
commit 31143e2933d1675c4c1ba6ce125cdd9587
I can also confirm that the issue still exists, but only if I run perf top as
root or with sudo.
Running perf top it as regular user is fine - even w/o the patches packages!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
[Impact]
Wake up from runtime suspend, Goodix doesn't report correct Tap event by
tapping it the first time, so if you double tap the touchpad, the system
only got one tap.
[Fix]
Adding one missing platform which uses Goodix touchpad IC to the i2c
designware quirk list.
[Tes
https://lists.ubuntu.com/archives/kernel-team/2019-July/102298.html
https://lists.ubuntu.com/archives/kernel-team/2019-July/102299.html
** Description changed:
+ SRU Justification:
+
+ [Impact]
+ Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to
+ pair BT LE HID devices on re
2 patches were skipped because they were already applied:
0002-mm-page_idle.c-fix-oops-because-end_pfn-is-larger-th.patch
0036-KVM-X86-Fix-scan-ioapic-use-before-initialization.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Applied patches:
* fs/binfmt_flat.c: make load_flat_shared_library() work
* scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()
* tracing: Silence GCC 9 array bounds warning
* gcc-9: silence 'address-of-packed-member' warning
* usb: chipidea: udc: workaround for endpoint conflict issue
* Inp
All patches from this updated were already applied.
--
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/1836667
Title:
Xenial update: 4.4.184 upstream stable release
Status in linux package
One patch was skipped as it was already present:
0039-Revert-Bluetooth-Align-minimum-encryption-key-size-f.patch
--
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/183
Title:
Xenial upd
All patches from this updated were already applied.
--
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/1836665
Title:
Xenial update: 4.4.182 upstream stable release
Status in linux package
Applied patches:
* Linux 4.4.182
--
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/1836665
Title:
Xenial update: 4.4.182 upstream stable release
Status in linux package in Ubuntu:
Confi
Applied patches:
* fs/fat/file.c: issue flush after the writeback of FAT
* sysctl: return -EINVAL if val violates minmax
* ipc: prevent lockup on alloc_msg and free_msg
* hugetlbfs: on restore reserve error path retain subpool reservation
* mm/cma.c: fix crash on CMA allocation if bitmap allocatio
Applied patches:
* Linux 4.4.184
--
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/1836667
Title:
Xenial update: 4.4.184 upstream stable release
Status in linux package in Ubuntu:
Confi
Yes, please test hwe-edge kernel.
--
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/1818974
Title:
Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
Status in linux package in U
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-lts-xenial (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Thank you, Warren. So I think I can begin to send a patch to the series
don't have REL0450 ibt-17-16-1.sfi, so that owners of the same devices
don't have to manually download again.
For polluted /lib/firmware, I think I would restore what it was and copy
only ibt-17-16-1.sfi to keep Bluetooth work
On GCP trace_printk module can't be found which triggers exit_unresolved
/home/jenkins/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
+ rmmod trace-printk
rmmod: ERROR: Module trace_printk is not currently loaded
+ :
+ modprobe tra
On Google, GCP this appears to fail across all of our tested instances.
Looks like that the cause is from the following due to the following
07/16 06:52:00 DEBUG| utils:0153| [stdout] [16] Test trace_printk from module
[UNRESOLVED]
07/16 06:52:05 DEBUG| utils:0153| [stdout] [21] ftrace - funct
Failure on Trusty:
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.4VEzBBYPcp -smp 1
# -initrd /tmp/tmp.Ef5R8Mt7p5
enabling ap
Thanks for the bug report.
Please tell us what version of Ubuntu you are using. Then please report
the problem to the BlueZ developers at:
https://bugzilla.kernel.org (Product: Drivers, Component: Bluetooth)
and then tell us the new bug ID.
** Changed in: bluez (Ubuntu)
Status: New =>
** Attachment added: "dmesg output after reverting to rel0450 of
ibt-17-16-1.sfi"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277544/+files/dmesg3.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
OK - after installing the rel0450 version, shutting down for 5 minutes and
rebooting, Bluetooth is still working for me. Here's the new md5sum
b24eceb411cf63695aac8e0b6d9f1743 /lib/firmware/intel/ibt-17-16-1.sfi
I'll upload the latest output of dmesg | egrep -i "blue|firm", in case
that helps.
The md5sum of what is current installed and working is:
5740378bfc048108341a204b83ca97c7 /lib/firmware/intel/ibt-17-16-1.sfi
Which is the same md5sum as the rel0472 version you link to above, so
yes, that does seem to be working.
I've downloaded the rel0450 version now, I'll install it, and leav
** Also affects: plymouth (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: linux-firmware (Ubuntu)
Status: In Progress => Fix Committed
--
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/1835879
Title:
Intel Wireless-AC 9462/9560 not
** Summary changed:
- ubuntu_kernel_tests ftrace fails on disco, linux-azure
+ ubuntu_kernel_tests ftrace fails
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags added: regression-testing-passed
--
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/1834930
Title:
linux-aws: 4.15.0-1044.46 -proposed tracker
Status in Kernel SRU Workflow:
I
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Tags added: regression-testing-passed
--
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/1834886
Title:
linux-aws: 5.0.0-1011.12 -proposed tracker
Status in Kernel SRU Workflow:
In
** Changed in: dkms (Ubuntu Disco)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1828948
Title:
OBSOLETE_BY in DKMS.CONF does not work
Status in DKMS:
I went to try again and get the log ... and with today's build it is
working. Let me try on the other machine that I was seeing this with and
then I will close the bug.
(The one thing I noticed is that I needed to restart the computer before
it worked, while I could swear it used to work as soon a
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1836816
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1836816
[Impact]
There are a number of races in nf_conntrack when multiple packets are
sent from the same origin to the same destination at the same time,
where there is no pre-existing confirmed conntrack entry, in a NAT
environment.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1836742
Title:
Please enable CONFIG_PMIC_OPREGION and it's components
I can confirm that the SCHED_STACK_END_CHECK config option has been
enabled in the linux-kvm kernel 4.4.0-1052.59 for xenial, 4.15.0-1039.39
for bionic, and 5.0.0-1011.12 for disco. Thanks!
** Tags added: verification-done-bionic verification-done-disco
verification-failed-xenial
** Tags removed:
This issue affects only kernels after 4.17 and before 5.2, hence it's
fixed on Bionic and Eoan, and won't be fixed in Cosmic (4.18) since it
is EOL.
Patches submitted to kernel-team ML: https://lists.ubuntu.com/archives
/kernel-team/2019-July/102287.html
Cheers,
Guilherme
--
You received this
** Description changed:
- TBD
+ [Impact]
+
+ * During raid0 error path testing, by removing one member of the array,
+ we've noticed after kernel 4.18 we can trigger a crash depending if
+ there's I/O in-flight during the array removal. When debugging the
+ issue, a second problem was found, that
I can confirm that the PAGE_POISONING, PAGE_POISONING_NO_SANITY, and
PAGE_POISONING_ZERO config options are set in the linux-kvm
5.0.0-1011.12 kernel in disco proposed. Thanks!
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Package
linux-kvm is currently 5.0.0-1010.11 in disco, looks like this bug got
left behind. Closing.
** Changed in: linux-kvm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-kvm (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
5.0.0-1011.12 linux-kvm kernel in disco-proposed. Thanks!
** Tags added: verifiction-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
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/1824981
Title:
cifs set_oplock buffer overflow in strcat
Stat
All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.3) for disco
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
4.15.0-1039.39 linux-kvm kernel in bionic-proposed. Thanks!
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubunt
Public bug reported:
Hello everyone,
We are currently developing a device that contains two HID services.
That device, as it is right now, is properly functioning on Windows & Android.
However, when pairing the device on Linux running bluez 5.50 we do get
segfaults (see attached files).
Our blue
** Changed in: linux (Ubuntu Ff-series)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a mem
** Changed in: linux-firmware (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux-firmware (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notif
** Also affects: linux (Ubuntu Eoan)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
Turning this option off is only significant in 4.12 kernels and newer,
where the LSM hooks make use of __ro_after_init if
CONFIG_SECURITY_SELINUX_DISABLE is disabled.
Per the discussion on the kernel-team list
(https://lists.ubuntu.com/archives/kernel-team/2019-July/102026.html),
I've made sure th
Public bug reported:
TBD
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Disco)
Importance: Undecided
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-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1836801
Title:
BCM43602 802.11ac Wirel
Just to add more ubuntu/debian specific details because this includes a
kernel config options that was changed from vanilla kernel and that not
everyone may agree with and I had missed myself.
This seem to have started when crg_init was changed in the kernel to 1
to fix a CVE. This caused a change
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277507/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277508/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277509/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.
SRU request was sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-July/102282.html
Cheers,
Guilherme
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
**
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277500/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277497/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277505/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277502/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https:/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277501/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277498/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277503/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277496/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1836
Public bug reported:
[Description]
The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running
with the proposed kernel 4.4.0-155.182-generic will cause kernel
trace[1]. However the wifi function works properly with the kernel
4.4.0-154.181
[Steps to Reproduce]
1. Install ubuntu xenial
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277495/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277504/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.la
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277499/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1836801/+attachment/5277506/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.16) for
bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#bio
I have tested a kernel with _only_
6c6bc1aee6a61fe7a98196794735849286761a4a "PCI: PM: Skip devices in D0
for suspend-to-idle" reverted. That appears to fix all issues with
suspend on this system. I am now attempting to find a minimal patch for
restoring functionality.
** Also affects: linux via
** Description changed:
- TBA
+ [Impact]
+
+ * Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool l
It looks like reverting 1bde9ecf018ee646b68258921bf0fa364afda38a fixes
suspend issues when writing devices to /sys/power/pm_test, but also
reverting 6c6bc1aee6a61fe7a98196794735849286761a4a fixes suspend issues
when using standard suspend/resume:
commit 6c6bc1aee6a61fe7a98196794735849286761a4a
Aut
Hello quanxian, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-
1ubuntu7.16 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
** Changed in: libvirt (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Cosmic)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Disco)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Eoan)
Importance: Undecided => Wish
also occurs on AWS-disco 5.0.0-1011.12 : amd64
** Summary changed:
- fib related test in net from ubuntu_kernel_selftests failed on C-KVM
+ fib related test in net from ubuntu_kernel_selftests failed
** Tags added: aws disco sru-20190701
** Also affects: linux-aws (Ubuntu)
Importance: Undec
Hello quanxian, or anyone else affected,
Accepted qemu into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg-
2ubuntu3.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
The application of 1bde9ecf018ee646b68258921bf0fa364afda38a appears to
have caused https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630
--
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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Fix Released
** Changed in: kernel-s
Also reported here: https://bugzilla.kernel.org/show_bug.cgi?id=204187
** Bug watch added: Linux Kernel Bug Tracker #204187
https://bugzilla.kernel.org/show_bug.cgi?id=204187
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** 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/1836202
Title:
bionic/linux-gke-5.0: 5.0.0-1011
** Changed in: kernel-sru-workflow/automated-testing
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/1836202
Title:
bionic/linux-gke-5.0: 5.0.0-1011.11~18.
I was able to narrow this down to this commit:
commit 1bde9ecf018ee646b68258921bf0fa364afda38a
Author: Keith Busch
Date: Thu May 23 09:27:35 2019 -0600
nvme-pci: Use host managed power state for suspend
BugLink: https://bugs.launchpad.net/bugs/1808957
The nvme pci driver prepares
Hi Klaus,
The same version of perf is expected.
I was able to reproduce the issue and I can confirm that I see the same
behavior as you described even with the patched test kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This issues is due to a test case bug. Please close.
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
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/1831268
Title:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1836201 (gke-ker
Public bug reported:
TBA
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux
** Tags added: ath10k
--
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/1799988
Title:
Missing wifi and bluetooth after sleep on XPS 9370
Status in Dell Sputnik:
New
Status in linux pack
** Tags added: ath10k
--
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/1818881
Title:
ath10k_pci crashing
Status in OEM Priority Project:
Triaged
Status in linux package in Ubuntu:
Co
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1836755
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Description changed:
- [Expected result]
- External microphone can work well
+ [Impact]
+ The external can't be detected when plugging headset in the
+ front audio jack.
- [Actual result]
- Can not detect external microphone
+ [Fix]
+ apply the alc891 fixup to set headset-mic and headpphone-
1 - 100 of 196 matches
Mail list logo
