[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
** Changed in: linux (Ubuntu Xenial)
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/1772775
Title:
4.4.0-127.153 generates many "sit: non-ECT" messages
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
A regression was introduce in Xenial linux-image-4.4.0-127-generic. It
was found that this regression was introduced by mainline commit
b699d0035836. This commit was applied to Xenial via the 4.4.128 upstream
stable
updates.
Upstream decided to revert this commit in mainline commit f4eb17e1efe5,
which was added in v4.12-rc5.
== Fix ==
f4eb17e1efe5 ("Revert "sit: reload iphdr in ipip6_rcv"")
== Regression Potential ==
Low. This is a revert request to resolve a regression. The revert was
also performed upstream.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
Xenial VM with a sit tunnel, I get such messages:
May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0
with TOS=0x5
Those are logged quite often:
# grep -cF 'sit: non-ECT' /var/log/syslog
9108
Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
issue.
# lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04
# apt-cache policy linux-image-4.4.0-127-generic
linux-image-4.4.0-127-generic:
Installed: 4.4.0-127.153
Candidate: 4.4.0-127.153
Version table:
*** 4.4.0-127.153 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-127-generic 4.4.0-127.153
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 20:08 seq
crw-rw 1 root audio 116, 33 May 22 20:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
Date: Tue May 22 21:18:45 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
RelatedPackageVersions:
linux-restricted-modules-4.4.0-127-generic N/A
linux-backports-modules-4.4.0-127-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.5
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.5
dmi.sys.vendor: QEMU
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 21:33 seq
crw-rw 1 root audio 116, 33 May 22 21:33 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lspci: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0
nmi_watchdog=0 nr_cpus=1 pti=on
[Kernel-packages] [Bug 1744173] Re: rfi-flush: Switch to new linear fallback flush
** Changed in: linux (Ubuntu Xenial) 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/1744173 Title: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: In Progress Bug description: [Impact] Change flush method from "congruence-first with dependencies" to "linear with no dependencies", which increases flush performance by 8x on P8, and 3x on P9. Measured with null syscall loop, which will have the flush area in the L2 cache. The flush also becomes simpler and more adaptable to different cache geometries. [Test Case] TBD. [Regression Potential] The risk is deemed low since the changes are confined to POWER only and the provided test kernels have been tested by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
** Changed in: linux (Ubuntu Xenial) 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/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in iotop package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in iotop source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The CVE-2018-3639 for Xenial introduced a double newline sequence in the /proc/PID/status files. This breaks some userspace tools, such as iotop, that parse those files. [Test Case] Incorrect output in 4.4.0-127.153-generic: $ cat /proc/self/status ... Seccomp: 0 Speculation_Store_Bypass: thread vulnerable ... Expected output: $ cat /proc/self/status ... Seccomp: 0 Speculation_Store_Bypass: thread vulnerable ... [Regression Potential] None [Original Report] Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
** Changed in: linux (Ubuntu Xenial)
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/1772575
Title:
Kernel 4.4 NBD size overflow with image size exceeding 1TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
With the Xenial kernel, the bug reporter states there is an NBD size
overflow with image size exceeding 1TB.
There's an issue in kernel's NBD module which prevents some larger images to
be
correctly "connected" , largely described here:
https://github.com/NetworkBlockDevice/nbd/issues/44
This is a regression from Trusty and was fixed in mainline as of
v4.10-rc1.
== Fix ==
ef77b515243b ("nbd: use loff_t for blocksize and nbd_set_size args")
== Regression Potential ==
Medium. A backport was needed. However, it was due to some context
diffs and the way debugfs_create_u32 was used in Xenial and how
debugfs_create_u64 was used in the patch.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Report ==
Release 16.04, kernel 4.4.0-124-generic
There's an issue in kernel's NBD module which prevents some larger images to
be
correctly "connected" , largely described here:
https://github.com/NetworkBlockDevice/nbd/issues/44
There is a small patch here that was accepted into mainline 4.10:
https://www.spinics.net/lists/linux-block/msg07060.html
This is a regression from the previous LTS 3.13 kernel.
Here is a small example of the faulty behaviour:
# qemu-img create -f qcow2 test.img 1100G
Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536
lazy_refcounts=off refcount_bits=16
# qemu-nbd -c /dev/nbd0 test.img
# blockdev --getsize64 /dev/nbd0
18446743055802302464
The correct response would be 1181116006400; this breaks most tools
and makes the image unusable, e.g.
# fdisk -l /dev/nbd0
fdisk: cannot open /dev/nbd0: Invalid argument
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 21 12:51 seq
crw-rw 1 root audio 116, 33 May 21 12:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Supermicro SYS-1028R-WTR
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANGUAGE=en_AU:
TERM=xterm
PATH=(custom, no user)
LANG=en_AU
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
RelatedPackageVersions:
linux-restricted-modules-4.4.0-124-generic N/A
linux-backports-modules-4.4.0-124-generic N/A
linux-firmware 1.157.18
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-124-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 02/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0a
dmi.board.asset.tag: Default string
dmi.board.name: X10DRW-i
dmi.board.vendor: Supermicro
dmi.board.version: 1.10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
dmi.product.name: SYS-1028R-WTR
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771301] Re: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels
** Changed in: linux (Ubuntu Xenial) 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/1771301 Title: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When booting with ipv6.disable=1, vxlan tunnels will fail to initialize with the error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT. Expected result is that vxlan tunnels work when ipv6 is disabled. # Tested on : Description: Ubuntu 16.04.4 LTS Release: 16.04 Kernel : linux-image-4.4.0-124-generic [Test Case] Deploy two identical 14.04 nodes with the following configuration: Add the following to /etc/default/grub then run 'sudo update-grub' GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" Reboot both nodes sudo reboot Set up a tunnel using the following commands on each node modifying remote_ip to be the ip of the other node. modify veth0 ip to be subnet using the tunnel 10.10.10.x/24 ovs-vsctl del-port br-int vx1 ovs-vsctl del-port br-int veth1 ip link del veth0 ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan options:remote_ip=192.168.122.161 # remote_ip should be the ip of the other node ip link add type veth ip link set veth0 up ip link set veth1 up ovs-vsctl add-port br-int veth1 ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24 Expected result is once the tunnel is configured on each side, you should be able to ping the ip of veth0 on the remote side while ipv6 is disabled. ping 10.10.10.2 or 10.10.10.3, whichever is the remote side. [Regression Potential] Regression Potential = Low. This has been tested by more than one person (pre-SRU) and the patch provide the expected behaviour for this particular bug. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/d074bf9600443403aa24fbc12c1f18eadc90f5aa * RHEL bug equivalent : https://bugzilla.redhat.com/show_bug.cgi?id=1445054 [Original Description] When booting with ipv6.disable=1, vxlan tunnels will fail to initialize with the error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT. Expected result is that vxlan tunnels work when ipv6 is disabled. Description: Ubuntu 16.04.4 LTS Release: 16.04 linux-image-4.4.0-124-generic bug is fixed in RHEL in https://bugzilla.redhat.com/show_bug.cgi?id=1445054 Steps to reproduce: Deploy two identical 14.04 nodes with the following configuration: Add the following to /etc/default/grub then run 'sudo update-grub' GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" Reboot both nodes sudo reboot Set up a tunnel using the following commands on each node modifying remote_ip to be the ip of the other node. modify veth0 ip to be subnet using the tunnel 10.10.10.x/24 ovs-vsctl del-port br-int vx1 ovs-vsctl del-port br-int veth1 ip link del veth0 ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan options:remote_ip=192.168.122.161 # remote_ip should be the ip of the other node ip link add type veth ip link set veth0 up ip link set veth1 up ovs-vsctl add-port br-int veth1 ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24 Expected result is once the tunnel is configured on each side, you should be able to ping the ip of veth0 on the remote side while ipv6 is disabled. ping 10.10.10.2 or 10.10.10.3, whichever is the remote side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
** Changed in: linux (Ubuntu Xenial)
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/1771826
Title:
Creation of IMA file hashes fails when appraisal is enabled
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
On a system that has IMA appraisal enabled it is impossible to create
security.ima extended attribute files that contain IMA hash. This is
due to mainline commit c68ed80c97d, which prevents writing file hashes as
security.ima xattrs.
This bug is fixed by reverting commit c68ed80c97d, which is done by
mainline commit f5acb3dcba1f as of v4.10-rc1.
== Fix ==
f5acb3dcba1f ("Revert "ima: limit file hash setting by user to fix and log
modes"")
== Regression Potential ==
Low. This revert happend in v4.10-rc1. It has been in Artful and
Bionic for a while without any reported issues.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
On a system that has IMA appraisal enabled it is impossible to create
security.ima extended attribute files that contain IMA hash.
For instance, consider the following use case:
1) extract application files to a staging area as non root user
2) verify that installation is correct
3) create IMA extended attributes for the installed files
4) move the files to their destination
5) change the files ownership to root
With kernel 4.4.x step 3 will fail.
The issues is fixed in upstream kernels by the following commit [1]:
commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
Author: Mimi Zohar
Date: Wed Nov 2 09:14:16 2016 -0400
Revert "ima: limit file hash setting by user to fix and log modes"
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-124-generic 4.4.0-124.148
ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 17 14:07 seq
crw-rw 1 root audio 116, 33 May 17 14:07 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Thu May 17 14:08:59 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0
console=tty1 console=ttyS0 crashkernel=384M-:128M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-124-generic N/A
linux-backports-modules-4.4.0-124-generic N/A
linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771826/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => 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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
This is a text-only installation, and I cannot seem to login to launchpad via a text browser (error: "bad robot go away"). Is there another way I can provide the information needed? ** 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/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
The amdgpu driver in Bionic is not new enough. Please try mainline kernel and latest firmware from [1]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770108] Re: No wifi in 4.13.0-41-generic
So yo do have -extra package. Please run `apport-collect` when the issue happens. -- 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/1770108 Title: No wifi in 4.13.0-41-generic Status in linux package in Ubuntu: Confirmed Bug description: Wifi adapter not showing since upgrading to 4.13.0-41-generic, still works fine if i roll back to 4.13.0-39-generic. Ubuntu 16.04 adapter details *-network description: Wireless interface product: RTL8192CE PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 01 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
This requires kernel bisection between v4.14 and v4.15. $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good v4.14 $ git bisect bad v4.15 $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775230] Missing required logs.
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 1775230 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Sure, http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.9-wily/ -- 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/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04
[Kernel-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
tried with nospectre_v2 rcu_nocbs=0-7 the behaviour changed, and it got out of the initial loop, but eventually it still crashed. -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775452] Re: Nvidia problems
It sounds like you're reporting a problem with the nouveau driver. Unfortunately the attached logs don't show the "flood" you refer to. Please copy and paste an example of the message flood. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Nvidia problems + Nouveau problems ** Tags added: nouveau -- 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/1775452 Title: Nouveau problems Status in linux package in Ubuntu: Incomplete Bug description: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
This bug has been reported with both GF106 (bug 1775279) and GM107GLM (this bug) hardware. -- 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/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 18.04(Updated 30.03.2018) System Language: Turkish Please check screenshots --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775452] [NEW] Nvidia problems
You have been subscribed to a public bug: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- Nvidia problems https://bugs.launchpad.net/bugs/1775452 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775486] Re: Bionic boot kernel oopses on Power
Unable to log collect as this happens in the ephemeral during boot and the system is not usable. ** 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/1775486 Title: Bionic boot kernel oopses on Power Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [3.839446] VFIO - User Level meta-driver version: 0.3 [3.839587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.839728] ehci-pci: EHCI PCI platform driver [3.839780] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [3.839825] ohci-pci: OHCI PCI platform driver [3.839898] uhci_hcd: USB Universal Host Controller Interface driver [3.840232] xhci_hcd 0009:03:00.0: xHCI Host Controller [3.840298]
[Kernel-packages] [Bug 1775487] [NEW] Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
Public bug reported: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub, I get nothing. And on a USB 3.0 port on the machine directly, I get this in dmesg: [ 1395.230629] xhci_hcd :03:00.0: Cannot set link state. [ 1395.230641] usb usb2-port4: cannot disable (err = -32) [ 1396.966273] xhci_hcd :03:00.0: Cannot set link state. [ 1396.966285] usb usb2-port4: cannot disable (err = -32) [ 1398.706493] xhci_hcd :03:00.0: Cannot set link state. [ 1398.706505] usb usb2-port4: cannot disable (err = -32) [ 1400.446161] xhci_hcd :03:00.0: Cannot set link state. [ 1400.446172] usb usb2-port4: cannot disable (err = -32) [ 1402.182073] xhci_hcd :03:00.0: Cannot set link state. [ 1402.182085] usb usb2-port4: cannot disable (err = -32) ...repeats until unplugged... It doesn't show up in lsusb in the USB 3.0 port. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:22:35 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-06 (304 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-05-29 (8 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports Status in linux-signed package in Ubuntu: New Bug description: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub,
[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
Any progress on the verification for this?
--
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 implementation
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reported this bug due to a regression introduced by mainline commit
94232a4332de. IBM has requested this SAUCE backport to resolve this
regression in Artful and Xenial.
With Bionic and v4.15, the rwlock code has been rewritten. See upstream
gitcommit:
eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").
Since the upstream code has been rewritten there also won't be an upstream
git commit id available which contains the attached fix.
== Fix ==
UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation
== Regression Potential ==
Low. The backport was written and tested by IBM. It is specific to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Description: kernel: fix rwlock implementation
Symptom: Kernel hangs, due to deadlock on an rwlock.
Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
write-lock the lock, then CPU 1 sets the writer bit and
afterwards busy waits for CPU 0 to release the lock. If now CPU 0
tries to read-lock the lock again (recursively) it will also
busy
wait until CPU 1 removes the writer bit, which will never
happen,
since it waits for the first reader on CPU 0 to release the
lock.
Solution: Revert the rwlock writer fairness semantics again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1761674/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded
Any progress on the verification for this?
--
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/1764982
Title:
[bionic] machine stuck and bonding not working well when nvmet_rdma
module is loaded
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This bug causes the machine to get stuck and bonding to not work when
the nvmet_rdma module is loaded.
Both of these commits are in mainline as of v4.17-rc1.
== Fixes ==
a3dd7d0022c3 ("nvmet-rdma: Don't flush system_wq by default during
remove_one")
9bad0404ecd7 ("nvme-rdma: Don't flush delete_wq by default during remove_one")
== Regression Potential ==
Low. Limited to nvme driver and tested by Mellanox.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
Hi
Machine stuck after unregistering bonding interface when the nvmet_rdma
module is loading.
scenario:
# modprobe nvmet_rdma
# modprobe -r bonding
# modprobe bonding -v mode=1 miimon=100 fail_over_mac=0
# ifdown eth4
# ifdown eth5
# ip addr add 15.209.12.173/8 dev bond0
# ip link set bond0 up
# echo +eth5 > /sys/class/net/bond0/bonding/slaves
# echo +eth4 > /sys/class/net/bond0/bonding/slaves
# echo -eth4 > /sys/class/net/bond0/bonding/slaves
# echo -eth5 > /sys/class/net/bond0/bonding/slaves
# echo -bond0 > /sys/class/net/bonding_masters
dmesg:
kernel: [78348.225556] bond0 (unregistering): Released all slaves
kernel: [78358.339631] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78368.419621] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78378.499615] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78388.579625] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78398.659613] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78408.739655] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78418.819634] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78428.899642] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78438.979614] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78449.059619] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78459.139626] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78469.219623] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78479.299619] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78489.379620] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78499.459623] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78509.539631] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
kernel: [78519.619629] unregister_netdevice: waiting for bond0 to become
free. Usage count = 2
The following upstream commits that fix this issue
commit a3dd7d0022c347207ae931c753a6dc3e6e8fcbc1
Author: Max Gurtovoy
Date: Wed Feb 28 13:12:38 2018 +0200
nvmet-rdma: Don't flush system_wq by default during remove_one
The .remove_one function is called for any ib_device removal.
In case the removed device has no reference in our driver, there
is no need to flush the system work queue.
Reviewed-by: Israel Rukshin
Signed-off-by: Max Gurtovoy
Reviewed-by: Sagi Grimberg
Signed-off-by: Keith Busch
Signed-off-by: Jens Axboe
diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
index aa8068f..a59263d 100644
--- a/drivers/nvme/target/rdma.c
+++ b/drivers/nvme/target/rdma.c
@@ -1469,8 +1469,25 @@ static struct nvmet_fabrics_ops nvmet_rdma_ops = {
static void nvmet_rdma_remove_one(struct ib_device *ib_device, void
*client_data)
{
struct nvmet_rdma_queue *queue, *tmp;
+ struct nvmet_rdma_device *ndev;
+ bool found = false;
+
+ mutex_lock(_list_mutex);
+ list_for_each_entry(ndev, _list, entry) {
+ if (ndev->device == ib_device) {
+ found = true;
+ break;
+ }
+ }
+ mutex_unlock(_list_mutex);
+
+ if (!found)
+ return;
- /* Device is being removed, delete all queues using this device */
+ /*
+ * IB Device that is used by nvmet controllers is being removed,
+ * delete all queues using this device.
+ */
mutex_lock(_rdma_queue_mutex);
[Kernel-packages] [Bug 1764690] Re: SRU: bionic: apply 50 ZFS upstream bugfixes
Any progress on the verification for this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764690 Title: SRU: bionic: apply 50 ZFS upstream bugfixes Status in linux package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Invalid Bug description: SRU Justification, bionic Apply the first round of SRU bugfixes for ZFS from 0.7.5 onwards from upstream ZFS repository. This round fixes the following ZFS bugs: - OpenZFS 8373 - TXG_WAIT in ZIL commit path Closes zfsonlinux #6403 - zfs promote|rename .../%recv should be an error Closes zfsonlinux #4843, #6339 - Fix parsable 'zfs get' for compressratios Closes zfsonlinux #6436, #6449 - Fix zpool events scripted mode tab separator Closes zfsonlinux #6444, #6445 - zv_suspend_lock in zvol_open()/zvol_release() Closes zfsonlinux #6342 - Allow longer SPA names in stats, allows bigger pool names Closes zfsonlinux #6481 - vdev_mirror: load balancing fixes Closes zfsonlinux #6461 - Fix zfs_ioc_pool_sync should not use fnvlist Closes zfsonlinux #6529 - OpenZFS 8375 - Kernel memory leak in nvpair code Closes zfsonlinux #6578 - OpenZFS 7261 - nvlist code should enforce name length limit Closes zfsonlinux #6579 - OpenZFS 5778 - nvpair_type_is_array() does not recognize DATA_TYPE_INT8_ARRAY Closes zfsonlinux #6580 - dmu_objset: release bonus buffer in failure path Closes zfsonlinux #6575 - Fix false config_cache_write events Closes zfsonlinux #6617 - Fix printk() calls missing log level Closes zfsonlinux #6672 - Fix abdstats kstat on 32-bit systems Closes zfsonlinux #6721 - Relax ASSERT for #6526 Closes zfsonlinux #6526 - Fix coverity defects: 147480, 147584 (Logically dead code) Closes zfsonlinux #6745 - Fix coverity defects: CID 161388 (Resource Leak) Closes zfsonlinux #6755 - Use ashift=12 by default on SSDSC2BW48 disks Closes zfsonlinux #6774 - OpenZFS 8558, 8602 - lwp_create() returns EAGAIN Closes zfsonlinux #6779 - ZFS send fails to dump objects larger than 128PiB Closes zfsonlinux #6760 - Sort output of tunables in arc_summary.py Closes zfsonlinux #6828 - Fix data on evict_skips in arc_summary.py Closes zfsonlinux #6882, #6883 - Fix segfault in zpool iostat when adding VDEVs Closes zfsonlinux #6748, #6872 - ZTS: Fix create-o_ashift test case Closes zfsonlinux #6924, #6877 - Handle invalid options in arc_summary Closes zfsonlinux #6983 - Call commit callbacks from the tail of the list Closes zfsonlinux #6986 - Fix 'zpool add' handling of nested interior VDEVs Closes zfsonlinux #6678, #6996 - Fix -fsanitize=address memory leak kmem_alloc(0, ...) in userspace returns a leakable pointer. Closes zfsonlinux #6941 - Revert raidz_map and _col structure types Closes zfsonlinux #6981, #7023 - Use zap_count instead of cached z_size for unlink Closes zfsonlinux #7019 - OpenZFS 8897 - zpool online -e fails assertion when run on non-leaf vdevs Closes zfsonlinux #7030 - OpenZFS 8898 - creating fs with checksum=skein on the boot pools fails ungracefully Closes zfsonlinux #7031 - Emit an error message before MMP suspends pool Closes zfsonlinux #7048 - OpenZFS 8641 - "zpool clear" and "zinject" don't work on "spare" or "replacing" vdevs Closes zfsonlinux #7060 - OpenZFS 8835 - Speculative prefetch in ZFS not working for misaligned reads Closes zfsonlinux #7062 - OpenZFS 8972 - zfs holds: In scripted mode, do not pad columns with spaces Closes zfsonlinux #7063 - Revert "Remove wrong ASSERT in annotate_ecksum" Closes zfsonlinux #7079 - OpenZFS 8731 - ASSERT3U(nui64s, <=, UINT16_MAX) fails for large blocks Closes zfsonlinux #7079 - Prevent zdb(8) from occasionally hanging on I/O Closes zfsonlinux #6999 - Fix 'zfs receive -o' when used with '-e|-d' Closes zfsonlinux #7088 - Change movaps to movups in AES-NI code Closes zfsonlinux #7065, #7108 - tx_waited -> tx_dirty_delayed in trace_dmu.h Closes zfsonlinux #7096 - OpenZFS 8966 - Source file zfs_acl.c, function Closes zfsonlinux #7141 - Fix zdb -c traverse stop on damaged objset root Closes zfsonlinux #7099 - Fix zle_decompress out of bound access Closes zfsonlinux #7099 - Fix racy
[Kernel-packages] [Bug 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!
Any progress on the verification for this? -- 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/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace: [Wed Apr 4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] power9_idle_type+0x24/0x40 (unreliable) [Wed Apr 4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] stop_loop+0x40/0x5c [Wed Apr 4 13:38:25 2018] [c00ff596fdf0] [c0acd9a4] cpuidle_enter_state+0xa4/0x450 [Wed Apr 4 13:38:25 2018] [c00ff596fe50] [c017195c] call_cpuidle+0x4c/0x90 [Wed Apr 4
[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race
Any progress on the verification for this? -- 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/1765564 Title: fsnotify: Fix fsnotify_mark_connector race Status in Linux: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-azure source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Released Bug description: On Azure we have had sporadic cases of soft lockups in fsnotify that may very well be mitigated by the following fix. The LKML thread is "kernel panics with 4.14.X". This should be applied to 4.13 and 4.15 versions of the linux-azure kernel, and possibly the 4.15 generic kernel in bionic as well. - fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector's 'destroy_next' field right before fsnotify() tries to traverse the linked list referenced by the connector's 'list' field. Since these two fields are members of the same union, this behavior results in a kernel panic. This issue is resolved by moving the connector's 'destroy_next' field into the object pointer union. This should work since the object pointer access is protected by both a spinlock and the value of the 'flags' field, and the 'flags' field is cleared while holding the spinlock in fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be possible for another thread to accidentally read from the object pointer after the 'destroy_next' field is updated. The offending behavior here is extremely unlikely; since fsnotify_put_mark() removes references to a connector (specifically, it ensures that the connector is unreachable from the inode it was formerly attached to) before updating its 'destroy_next' field, a sizeable chunk of code in fsnotify_put_mark() has to execute in the short window between when fsnotify() acquires the connector reference and saves the value of its 'list' field. On the HEAD kernel, I've only been able to reproduce this by inserting a udelay(1) in fsnotify(). However, I've been able to reproduce this issue without inserting a udelay(1) anywhere on older unmodified release kernels, so I believe it's worth fixing at HEAD. References: https://bugzilla.kernel.org/show_bug.cgi?id=199437 Fixes: 08991e83b7286635167bab40927665a90fb00d81 CC: sta...@vger.kernel.org Signed-off-by: Robert Kolchmeyer Signed-off-by: Jan Kara To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1765564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769027] Re: perf record crash: refcount_inc assertion failed
Any progress on the verification for this?
--
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/1769027
Title:
perf record crash: refcount_inc assertion failed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
This SRU request is for two commits, that are needed for two bug reports. The
first bug(1767204) is marked as a duplicate of the bug used for this SRU
request. The commit(3d8bba9535ac) required to fix the first bug introduced
the second
bug. The second bug is then fixed buy commit cd8dd032f61a.
The first issue is perf crashes due to swapped xyarray function signatures
and is
fixed by commit 3d8bba9535ac.
The second issue is a crash due to "refcount_inc assertion failed".
This second bug is introduced by picking commit 3d8bba9535ac without
picking commit cd8dd032f61a first.
== Fixes ==
cd8dd032f61a ("perf cgroup: Fix refcount usage")
3d8bba9535ac ("perf xyarray: Fix wrong processing when closing evsel fd")
== Regression Potential ==
Low. Limited to perf tool.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
On linux-hwe-tools-4.13.0-39 in xenial:
Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion
failure:
refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.
Confirmed fixed by patching my linux-tools package with this upstream
commit (on top of the commit in bug #1767204):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769027/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768761] Re: linux-snapdragon: reduce EPROBEDEFER noise during boot
Any progress on the verification for this? -- 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/1768761 Title: linux-snapdragon: reduce EPROBEDEFER noise during boot Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: IMPACT: During boot, after the rootfs is mounted, the linux-snapdragon kernel prints several lines like these: ... [5.258027] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.258052] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [5.274320] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [5.274451] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops): -517 [5.300115] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.300140] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [5.733725] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [5.733841] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops): -517 [5.760228] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.760252] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [6.146074] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 ... these are the audio and drm modules failing to attach due to the adv7511 i2c bridge missing - they will retry several times, until the adv7511_drm is finally loaded and these messages disappear. While both audio and video work fine in the end, these lines make parsing the boot logs harder and might fool a user to think there's a potential problem. FIX: To fix it, make the config DRM_I2C_ADV7511=y. HOW TO REPRODUCE: Boot a patched kernel and check the boot logs. REGRESSION POTENTIAL: Probably none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev
Any progress on the verification for this? -- 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/1770770 Title: Switch Build-Depends: transfig to fig2dev Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux-raspi2 source package in Bionic: Fix Committed Bug description: [SRU Justification] == Impact == We are still depending on a transitional package for transfig. Switch to the real package fig2dev. This is contributing to NBS in cosmic but is also valid in bionic. We need to bear in mind it is _not_ valid in xenial. == Fix == Change the dependency from transfig into fig2dev in the source package control file(s). == Testcase == This is a build dependency for the architecture independent part, so successful build of amd64 is the testing. == Regression Potential == Minimal, this affects only build and even there only generating documentation files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775486] [NEW] Bionic boot kernel oopses on Power
Public bug reported: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [3.839446] VFIO - User Level meta-driver version: 0.3 [3.839587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.839728] ehci-pci: EHCI PCI platform driver [3.839780] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [3.839825] ohci-pci: OHCI PCI platform driver [3.839898] uhci_hcd: USB Universal Host Controller Interface driver [3.840232] xhci_hcd 0009:03:00.0: xHCI Host Controller [3.840298] xhci_hcd 0009:03:00.0: new USB bus registered, assigned bus number 1 [3.840580] xhci_hcd 0009:03:00.0: Using 64-bit DMA iommu bypass [3.840830] xhci_hcd 0009:03:00.0: hcc params 0x0270f06d hci version 0x96 quirks 0x0400 [3.841395] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [3.841516] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.841570] usb usb1: Product: xHCI Host Controller [3.841746] usb usb1: Manufacturer: Linux 4.15.0-22-generic xhci-hcd [3.841790] usb usb1: SerialNumber: 0009:03:00.0 [
[Kernel-packages] [Bug 1775486] Missing required logs.
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 1775486 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1775486 Title: Bionic boot kernel oopses on Power Status in linux package in Ubuntu: Incomplete Bug description: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [
[Kernel-packages] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial
** Changed in: linux (Ubuntu Xenial) 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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
** Information type changed from Public Security to Public -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu Xenial) Status: Fix Committed => In Progress -- 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/1774306 Title: enable mic-mute hotkey and led on Lenovo M820z and M920z Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button with led on them, without this patch, the hotkey and led only works on M810z, if we want 820z and 920z to work, we need to add their subsystem id in the driver, but since they use same codec with same pin conf, we use a better way than adding id. [Fix] With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY. [Test Case] press mic-mute button, then check sound-setting, we found the input will mute or unmute as users press button, and led will on or off to indicate the input status. [Regression Potential] Very low, through the strictly match the pin conf, codec id and vendor id, this fix only apply to M810z, M820z and M920z. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- 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/1774306 Title: enable mic-mute hotkey and led on Lenovo M820z and M920z Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button with led on them, without this patch, the hotkey and led only works on M810z, if we want 820z and 920z to work, we need to add their subsystem id in the driver, but since they use same codec with same pin conf, we use a better way than adding id. [Fix] With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY. [Test Case] press mic-mute button, then check sound-setting, we found the input will mute or unmute as users press button, and led will on or off to indicate the input status. [Regression Potential] Very low, through the strictly match the pin conf, codec id and vendor id, this fix only apply to M810z, M820z and M920z. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu) ** Changed in: linux-oem (Ubuntu Artful) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Invalid ** No longer affects: linux-oem (Ubuntu Bionic) ** No longer affects: linux-oem (Ubuntu Artful) -- 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/1774306 Title: enable mic-mute hotkey and led on Lenovo M820z and M920z Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button with led on them, without this patch, the hotkey and led only works on M810z, if we want 820z and 920z to work, we need to add their subsystem id in the driver, but since they use same codec with same pin conf, we use a better way than adding id. [Fix] With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY. [Test Case] press mic-mute button, then check sound-setting, we found the input will mute or unmute as users press button, and led will on or off to indicate the input status. [Regression Potential] Very low, through the strictly match the pin conf, codec id and vendor id, this fix only apply to M810z, M820z and M920z. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
** 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Incomplete Bug description: I am having trouble with the bluetooth connection between the laptop and my Logitech MX Master wireless mouse. The computer will lose connection with the mouse multiple times per day. When this happens, the bluetooth icon in the upper right-hand corner of the screen disappears. Checking the Bluetooth system preference panel, Bluetooth is turned off. I can toggle the switch to "on" but bluetooth remains off. Neither restarting the computer nor power cycling the computer bring bluetooth back. $ sudo service bluetooth restart also doesn't work. The only way I have found to renable bluetooth is: 1. reboot 2. disable bluetooth in BIOS 3. reboot 4. enable bluetooth in BIOS 5. reboot Also, I was running Ubuntu 16.04 until this past Friday. I experienced this problem under 16.04 but it happened much less frequently (once every couple weeks or so). I upgraded to 18.04 ahead of 18.04.1 in hopes that a newer kernel/driver would work better with my brand new hardware. Now, under 18.04, bluetooth is crashing multiple times per day. Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41
[Kernel-packages] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- 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/1774306 Title: enable mic-mute hotkey and led on Lenovo M820z and M920z Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button with led on them, without this patch, the hotkey and led only works on M810z, if we want 820z and 920z to work, we need to add their subsystem id in the driver, but since they use same codec with same pin conf, we use a better way than adding id. [Fix] With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY. [Test Case] press mic-mute button, then check sound-setting, we found the input will mute or unmute as users press button, and led will on or off to indicate the input status. [Regression Potential] Very low, through the strictly match the pin conf, codec id and vendor id, this fix only apply to M810z, M820z and M920z. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
** Information type changed from Public to Public Security -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772927] Re: linux: 4.15.0-23.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1772927 Title: linux: 4.15.0-23.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: 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: bug 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 1772942 (linux-azure-edge) derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 1772934 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775477] Re: Xenial update to 4.4.133 stable release
* arm64: Add work around for Arm Cortex-A55 Erratum 1024718 -> needed some backport which should be sanity checked * proc: meminfo: estimate available memory more conservatively -> the conversion done was silently added when backporting mm/page_alloc.c: calculate 'available' memory in a separate function * cpufreq: intel_pstate: Enable HWP by default -> already applied for bug 1674390 * procfs: fix pthread cross-thread naming if !PR_DUMPABLE -> already applied for bug 1690225 * s390/cpum_sf: ensure sample frequency of perf event attributes is non-zero -> already applied for bug 1772593 -- 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/1775477 Title: Xenial update to 4.4.133 stable release Status in linux package in Ubuntu: New Bug description: 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 a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.133 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.133 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775483] Re: Bionic update: upstream stable patchset 2018-06-06
** 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
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- 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 a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2018-06-06 (ported from v4.14.38 and v4.16.6)
+ from git://git.kernel.org/
-upstream stable patchset 2018-06-06
-from git://git.kernel.org/
+ kprobes: Fix random address output of blacklist file
+ s390/cpum_cf: rename IBM z13/z14 counter names
+ hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics
+ hwmon: (k10temp) Add temperature offset for Ryzen 2700X
+ VSOCK: make af_vsock.ko removable again
+ virtio-net: add missing virtqueue kick when flushing packets
+ bnxt_en: Fix memory fault in bnxt_ethtool_init()
+ s390/qeth: handle failure on workqueue creation
+ s390/qeth: avoid control IO completion stalls
+ s390/qeth: fix error handling in adapter command callbacks
+ l2tp: fix {pppol2tp, l2tp_dfs}_seq_stop() in case of seq_file overflow
+ l2tp: hold reference on tunnels printed in l2tp/tunnels debugfs file
+ l2tp: hold reference on tunnels printed in pppol2tp proc file
+ l2tp: hold reference on tunnels in netlink dumps
+ vmxnet3: fix incorrect dereference when rxvlan is disabled
+ net: stmmac: Disable ACS Feature for GMAC >= 4
+ net: mvpp2: Fix DMA address mask size
+ docs: ip-sysctl.txt: fix name of some ipv6 variables
+ ACPI / video: Only default only_lcd to true on Win8-ready _desktops_
+ s390/uprobes: implement arch_uretprobe_is_alive()
+ s390/dasd: fix IO error for newly defined devices
+ s390/cio: update chpid descriptor after resource accessibility event
+ tracing: Fix missing tab for hwlat_detector print format
+ block/swim: Fix IO error at end of medium
+ block/swim: Fix array bounds check
+ block/swim: Select appropriate drive on device open
+ block/swim: Rename macros to avoid inconsistent inverted logic
+ block/swim: Remove extra put_disk() call from error path
+ block/swim: Don't log an error message for an invalid ioctl
+ block/swim: Check drive type
+ m68k/mac: Don't remap SWIM MMIO region
+ cdrom: information leak in cdrom_ioctl_media_changed()
+ scsi: mptsas: Disable WRITE SAME
+ commoncap: Handle memory allocation failure.
+ microblaze: Setup dependencies for ASM optimized lib functions
+ s390: correct module section names for expoline code revert
+ KVM: s390: force bp isolation for VSIE
+ virtio_net: fix adding vids on big-endian
+ virtio_net: split out ctrl buffer
+ net: ethernet: ti: cpsw: fix tx vlan priority mapping
+ llc: fix NULL pointer deref for SOCK_ZAPPED
+ llc: hold llc_sap before release_sock()
+ net: sched: ife: check on metadata length
+ net: sched: ife: handle malformed tlv length
+ tcp: clear tp->packets_out when purging write queue
+ net: sched: ife: signal not finding metaid
+ strparser: Fix incorrect strp->need_bytes value.
+ amd-xgbe: Only use the SFP supported transceiver signals
+ strparser: Do not call mod_delayed_work with a timeout of LONG_MAX
+ amd-xgbe: Improve KR auto-negotiation and training
+ sctp: do not check port in sctp_inet6_cmp_addr
+ amd-xgbe: Add pre/post auto-negotiation phy hooks
+ vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
+ pppoe: check sockaddr length in pppoe_connect()
+ tipc: add policy for TIPC_NLA_NET_ADDR
+ packet: fix bitfield update race
+ team: fix netconsole setup over team
+ net/smc: fix shutdown in state SMC_LISTEN
+ team: avoid adding twice the same option to the event list
+ net: fix deadlock while clearing neighbor proxy table
+ tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
+ net: af_packet: fix race in PACKET_{R|T}X_RING
+ tcp: don't read out-of-bounds opsize
+ llc: delete timers synchronously in llc_sk_free()
+ net: validate attribute sizes in neigh_dump_table()
+ l2tp: check sockaddr length in pppol2tp_connect()
+ KEYS: DNS: limit the length of option strings
+ ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts
+ ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
+ bonding: do not set slave_dev npinfo before slave_enable_netpoll in
bond_enslave
+ Revert "ath10k: send (re)assoc peer command when NSS changed"
+ tpm: add retry logic
+ tpm: tpm-interface: fix
[Kernel-packages] [Bug 1775483] [NEW] Bionic update: upstream stable patchset 2018-06-06
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2018-06-06 (ported from v4.14.38 and v4.16.6)
from git://git.kernel.org/
kprobes: Fix random address output of blacklist file
s390/cpum_cf: rename IBM z13/z14 counter names
hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics
hwmon: (k10temp) Add temperature offset for Ryzen 2700X
VSOCK: make af_vsock.ko removable again
virtio-net: add missing virtqueue kick when flushing packets
bnxt_en: Fix memory fault in bnxt_ethtool_init()
s390/qeth: handle failure on workqueue creation
s390/qeth: avoid control IO completion stalls
s390/qeth: fix error handling in adapter command callbacks
l2tp: fix {pppol2tp, l2tp_dfs}_seq_stop() in case of seq_file overflow
l2tp: hold reference on tunnels printed in l2tp/tunnels debugfs file
l2tp: hold reference on tunnels printed in pppol2tp proc file
l2tp: hold reference on tunnels in netlink dumps
vmxnet3: fix incorrect dereference when rxvlan is disabled
net: stmmac: Disable ACS Feature for GMAC >= 4
net: mvpp2: Fix DMA address mask size
docs: ip-sysctl.txt: fix name of some ipv6 variables
ACPI / video: Only default only_lcd to true on Win8-ready _desktops_
s390/uprobes: implement arch_uretprobe_is_alive()
s390/dasd: fix IO error for newly defined devices
s390/cio: update chpid descriptor after resource accessibility event
tracing: Fix missing tab for hwlat_detector print format
block/swim: Fix IO error at end of medium
block/swim: Fix array bounds check
block/swim: Select appropriate drive on device open
block/swim: Rename macros to avoid inconsistent inverted logic
block/swim: Remove extra put_disk() call from error path
block/swim: Don't log an error message for an invalid ioctl
block/swim: Check drive type
m68k/mac: Don't remap SWIM MMIO region
cdrom: information leak in cdrom_ioctl_media_changed()
scsi: mptsas: Disable WRITE SAME
commoncap: Handle memory allocation failure.
microblaze: Setup dependencies for ASM optimized lib functions
s390: correct module section names for expoline code revert
KVM: s390: force bp isolation for VSIE
virtio_net: fix adding vids on big-endian
virtio_net: split out ctrl buffer
net: ethernet: ti: cpsw: fix tx vlan priority mapping
llc: fix NULL pointer deref for SOCK_ZAPPED
llc: hold llc_sap before release_sock()
net: sched: ife: check on metadata length
net: sched: ife: handle malformed tlv length
tcp: clear tp->packets_out when purging write queue
net: sched: ife: signal not finding metaid
strparser: Fix incorrect strp->need_bytes value.
amd-xgbe: Only use the SFP supported transceiver signals
strparser: Do not call mod_delayed_work with a timeout of LONG_MAX
amd-xgbe: Improve KR auto-negotiation and training
sctp: do not check port in sctp_inet6_cmp_addr
amd-xgbe: Add pre/post auto-negotiation phy hooks
vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
pppoe: check sockaddr length in pppoe_connect()
tipc: add policy for TIPC_NLA_NET_ADDR
packet: fix bitfield update race
team: fix netconsole setup over team
net/smc: fix shutdown in state SMC_LISTEN
team: avoid adding twice the same option to the event list
net: fix deadlock while clearing neighbor proxy table
tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
net: af_packet: fix race in PACKET_{R|T}X_RING
tcp: don't read out-of-bounds opsize
llc: delete timers synchronously in llc_sk_free()
net: validate attribute sizes in neigh_dump_table()
l2tp: check sockaddr length in pppol2tp_connect()
KEYS: DNS: limit the length of option strings
ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts
ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
bonding: do not set slave_dev npinfo before slave_enable_netpoll in bond_enslave
Revert "ath10k: send (re)assoc peer command when NSS changed"
tpm: add retry logic
tpm: tpm-interface: fix tpm_transmit/_cmd kdoc
tpm: cmd_ready command can be issued only after granting locality
i40e: Fix attach VF to VM issue
drm: bridge: dw-hdmi: Fix overflow workaround for Amlogic Meson GX SoCs
Revert "pinctrl: intel: Initialize GPIO properly when used through irqchip"
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1775477] [NEW] Xenial update to 4.4.133 stable release
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 a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.133 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.133 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug -- 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/1775477 Title: Xenial update to 4.4.133 stable release Status in linux package in Ubuntu: New Bug description: 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 a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.133 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.133 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770108] Re: No wifi in 4.13.0-41-generic
I have attached the output of "dpkg -l | grep linux | grep extra". The output of that command was the same across both kernels 4.13.0-43-generic and 4.13.0-39-generic. An important thing I would like to add is: the problem I had mentioned regarding black screen, low-graphics, dialog boxes, and no wifi happens 9/10 times in kernels 4.13.0-43-generic and 4.13.0-41-generic. But, 1/10 times those kernels boot absolutely normally, and wifi also works at that time. It seems to me that maybe sometimes the OS cannot detect certain things (devices/drivers) during boot-up. Could this be due to a virus or hardware problem? Thanks! ** Attachment added: "dpkg -l | grep linux | grep extra" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770108/+attachment/5149491/+files/dpkgOutput.txt -- 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/1770108 Title: No wifi in 4.13.0-41-generic Status in linux package in Ubuntu: Confirmed Bug description: Wifi adapter not showing since upgrading to 4.13.0-41-generic, still works fine if i roll back to 4.13.0-39-generic. Ubuntu 16.04 adapter details *-network description: Wireless interface product: RTL8192CE PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 01 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support
** Changed in: libdrm (Ubuntu Xenial) Milestone: None => ubuntu-16.04.5 -- 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/1753954 Title: Intel Whiskey Lake (WHL) graphics support Status in libdrm package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libdrm source package in Xenial: New Status in linux-oem source package in Xenial: Won't Fix Status in mesa source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: New Status in libdrm source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, libdrm, mesa and xserver. [Test Case] Test the installation on a WHL machine, the graphical session should have full acceleration after these updates. [Regression Potential] None, just adds PCI-ID's to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775137] Re: Prevent speculation on user controlled pointer
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (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 Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Precise:
New
Status in linux source package in Trusty:
New
Status in linux source package in Xenial:
New
Bug description:
== SRU Justification ==
Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
== Fix ==
Backport the following patches:
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
== Regression Potential ==
Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
== Test Case ==
TBD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1019672] Re: 8086:4230 [Lenovo ThinkPad T61] WiFi hw hangs
** Tags removed: kernel-bug-exists-upstream-3.5-rc5 ** Tags added: kernel-bug-exists-upstream-3.5-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/1019672 Title: 8086:4230 [Lenovo ThinkPad T61] WiFi hw hangs Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: iwl4965 wireless hardware hangs randomly (sometimes very rarely, sometimes very often) with 'MAC is in deep sleep!' message. (syslog attached) the wireless led turns off also. reloading the module doesn't help. (syslog attached) only rebooting solves the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: istvan 2130 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20d7,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat Jun 30 23:41:27 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c520c7a6-f648-456c-962a-12ae1aa0b830 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 76641FG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=e689c33b-901e-4855-a19d-f054fc989fc6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic N/A linux-backports-modules-3.2.0-26-generic N/A linux-firmware1.79 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 76641FG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn76641FG:pvrThinkPadT61:rvnLENOVO:rn76641FG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 76641FG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1019672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1019672] Re: 8086:4230 [Lenovo ThinkPad T61] WiFi hw hangs
** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-3.5-rc5 needs-upstream-testing ** Changed in: linux (Ubuntu) Importance: Medium => Low -- 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/1019672 Title: 8086:4230 [Lenovo ThinkPad T61] WiFi hw hangs Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: iwl4965 wireless hardware hangs randomly (sometimes very rarely, sometimes very often) with 'MAC is in deep sleep!' message. (syslog attached) the wireless led turns off also. reloading the module doesn't help. (syslog attached) only rebooting solves the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: istvan 2130 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20d7,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat Jun 30 23:41:27 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c520c7a6-f648-456c-962a-12ae1aa0b830 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 76641FG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=e689c33b-901e-4855-a19d-f054fc989fc6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic N/A linux-backports-modules-3.2.0-26-generic N/A linux-firmware1.79 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 76641FG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn76641FG:pvrThinkPadT61:rvnLENOVO:rn76641FG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 76641FG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1019672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command
What are the ways to figure out if the symptoms I am seeing is because of this bug or something else? -- 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/1313279 Title: xHCI host not responding to stop endpoint command Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 Hardware: Intel NUC D34010WYK (Core i3 4010U) Memory: 4 gigabytes USD device: PCTV 292e DVB-T tuner I have 2 PCTV 292e DVB-T tuners connected to the system. When I start to use either of the tuner, the xHCI host crashes. Since I'm booting from an USB disk. If I only connect 1 of the tuners, the system works ok. It does not matter which one of the tuners I connect. [ 68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. [ 68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host. Sometimes this also leads to this: [ 638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0 [ 638.183057] PGD 0 [ 638.183077] Oops: [#1] SMP I can also observe the same fault with OpenELEC Linux distribution that runs kernel 3.14 when I run the system from an internal SATA SSD drive (not from an external USB disk). lsusb -v: http://paste.ubuntu.com/7343384/ dmesg: http://sprunge.us/HMXH dmesg (crash type 2): http://sprunge.us/PSiX ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lubuntu-desktop 0.55 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 11:12:22 2014 InstallationDate: Installed on 2014-04-07 (19 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: lubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1313279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
I built a test kernel with commit 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1775390 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
I built a test kernel with the patch you posted in the description. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1775235
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
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/1775235
Title:
Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127).
Only guests with scsi mq enabled suffered from this problem. AHV is
one of the few hypervisor products to offer multiqueue for virtio-scsi
devices.
Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the
first time the kernel destroys a target (given it doesn't have luns).
This could be confirmed with gdb (attached to qemu's gdbserver):
#0 0xc0045039 in ?? ()
#1 0x88022c753c98 in ?? ()
#2 0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:
(gdb) p *(struct virtio_scsi_target_state *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq =
0x88022cbdd9e8}
(gdb)
This drew our attention to the following patch which is exclusive to the
Ubuntu kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh
Date: Thu Apr 19 21:40:00 2018 +0200
In a nutshell, the patch spins on the target's 'reqs' counter waiting for the
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target
*starget)
static void virtscsi_target_destroy(struct scsi_target *starget)
{
struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+ /* we can race with concurrent virtscsi_complete_cmd */
+ while (atomic_read(>reqs))
+ cpu_relax();
kfree(tgt);
}
Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs
disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
long time to quiesce during a target_destroy() could hog the CPU for
relatively long periods of time.
Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.
The following patch fixes the issue:
--- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
+++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
@@ -641,9 +641,10 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;
- if (shost_use_blk_mq(sh))
+ if (shost_use_blk_mq(sh)) {
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
- else
+ atomic_inc(>reqs);
+ } else
req_vq = virtscsi_pick_vq(vscsi, tgt);
return virtscsi_queuecommand(vscsi, req_vq, sc);
Signed-off-by: Felipe Franciosi
Please consider this a urgent fix as all of our customers which use
Ubuntu 16.04 and have MQ enabled for better performance will be
affected by your latest update. Our workaround is to recommend that
they disable SCSI MQ while you work on the issue.
Best regards,
Felipe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775235/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation
I built a test kernel with commit 966f53e750aedc5f59f9ccae6bbfb8f671c7c842. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1775391 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1540045] Re: BUG: Bad rss-counter state mm:ffff88010af5cb00 idx:1 val:512
Are you guys still experiencing the issue ? -- 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/1540045 Title: BUG: Bad rss-counter state mm:88010af5cb00 idx:1 val:512 Status in linux package in Ubuntu: Expired Bug description: I'm not sure exactly what triggered this, but happened while a vmware virtual machine was under heavy load. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 [modified: boot/vmlinuz-4.3.0-7-generic] ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wade 2121 F pulseaudio /dev/snd/controlC1: wade 2121 F pulseaudio /dev/snd/controlC0: wade 2121 F pulseaudio Date: Sun Jan 31 04:14:52 2016 Failure: oops HibernationDevice: RESUME=UUID=659ef7fe-fc16-45e4-a3cb-4484d08c8422 InstallationDate: Installed on 2016-01-31 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) MachineType: MSI MS-7924 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.3.0-7-generic.efi.signed root=UUID=740f64dc-d330-484d-9a81-d9c683d362ec ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: BUG: Bad rss-counter state mm:88010af5cb00 idx:1 val:512 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-G43(MS-7924) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd01/08/2016:svnMSI:pnMS-7924:pvr1.0:rvnMSI:rnZ97M-G43(MS-7924):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7924 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
I manually install 4.17.0-041700-generic from http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.17/ and hibernate is working very 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762554] Re: [Hyper-V] IB/mlx5: Respect new UMR capabilities
Hi, Madhuri. Is this entire PR from comment #1 necessary? I'm facing a lot of conflicts when trying to apply it to 4.15. The two commits from the initial description apply cleanly though. -- 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/1762554 Title: [Hyper-V] IB/mlx5: Respect new UMR capabilities Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Bug description: In some firmware configuration, UMR usage from Virtual Functions is restricted. This information is published to the driver using new capability bits. Avoid using UMRs in these cases and use the Firmware slow-path flow to create mkeys and populate them with Virtual to Physical address translation. Older drivers that do not have this patch, will end up using memory keys that aren't populated with Virtual to Physical address translation that is done part of the UMR work. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?h=next-20180409=c8d75a980fab886a9c716567e6b47cc414ad84ee and pull this patch as well IB/mlx5: Enable ECN capable bits for UD RoCE v2 QPs https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=ea8af0d2f2b5b16da4553205ddaf225e0a057e03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1762554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770423] Re: Please cherry-pick upstream patch for HDMI on Dell XPS 9360
Sorry for the late reply. The patch was merged upstream in https://github.com/torvalds/linux/commit/9a86cda07af2c63649932f0a4fc757701ef54c42 -- 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/1770423 Title: Please cherry-pick upstream patch for HDMI on Dell XPS 9360 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Connecting the Dell USB-C HDMI/LAN/VGA/USB adapter to my XPS 9360 doesn’t quite work: I could not get my monitor to display a picture at all, regardless of which resolution I tried. A quick search on the internet revealed this patch: https://lists.freedesktop.org/archives/intel- gfx/2017-March/124077.html. Applying it to the 4.4.0-122 kernel does indeed make the HDMI work Could you please cherry-pick this patch into the Ubuntu kernel? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Changed in: ubuntu-z-systems Status: Triaged => 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775443] Status changed to Confirmed
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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: I am having trouble with the bluetooth connection between the laptop and my Logitech MX Master wireless mouse. The computer will lose connection with the mouse multiple times per day. When this happens, the bluetooth icon in the upper right-hand corner of the screen disappears. Checking the Bluetooth system preference panel, Bluetooth is turned off. I can toggle the switch to "on" but bluetooth remains off. Neither restarting the computer nor power cycling the computer bring bluetooth back. $ sudo service bluetooth restart also doesn't work. The only way I have found to renable bluetooth is: 1. reboot 2. disable bluetooth in BIOS 3. reboot 4. enable bluetooth in BIOS 5. reboot Also, I was running Ubuntu 16.04 until this past Friday. I experienced this problem under 16.04 but it happened much less frequently (once every couple weeks or so). I upgraded to 18.04 ahead of 18.04.1 in hopes that a newer kernel/driver would work better with my brand new hardware. Now, under 18.04, bluetooth is crashing multiple times per day. Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun
[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation
** Changed in: ubuntu-z-systems Status: Triaged => 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
** No longer affects: linux-signed (Ubuntu) -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: I am having trouble with the bluetooth connection between the laptop and my Logitech MX Master wireless mouse. The computer will lose connection with the mouse multiple times per day. When this happens, the bluetooth icon in the upper right-hand corner of the screen disappears. Checking the Bluetooth system preference panel, Bluetooth is turned off. I can toggle the switch to "on" but bluetooth remains off. Neither restarting the computer nor power cycling the computer bring bluetooth back. $ sudo service bluetooth restart also doesn't work. The only way I have found to renable bluetooth is: 1. reboot 2. disable bluetooth in BIOS 3. reboot 4. enable bluetooth in BIOS 5. reboot Also, I was running Ubuntu 16.04 until this past Friday. I experienced this problem under 16.04 but it happened much less frequently (once every couple weeks or so). I upgraded to 18.04 ahead of 18.04.1 in hopes that a newer kernel/driver would work better with my brand new hardware. Now, under 18.04, bluetooth is crashing multiple times per day. Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520
[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
** Description changed: + I am having trouble with the bluetooth connection between the laptop and + my Logitech MX Master wireless mouse. The computer will lose connection + with the mouse multiple times per day. When this happens, the bluetooth + icon in the upper right-hand corner of the screen disappears. Checking + the Bluetooth system preference panel, Bluetooth is turned off. I can + toggle the switch to "on" but bluetooth remains off. Neither restarting + the computer nor power cycling the computer bring bluetooth back. $ sudo + service bluetooth restart also doesn't work. The only way I have found + to renable bluetooth is: + + 1. reboot + 2. disable bluetooth in BIOS + 3. reboot + 4. enable bluetooth in BIOS + 5. reboot + + Also, I was running Ubuntu 16.04 until this past Friday. I experienced + this problem under 16.04 but it happened much less frequently (once + every couple weeks or so). I upgraded to 18.04 ahead of 18.04.1 in hopes + that a newer kernel/driver would work better with my brand new hardware. + Now, under 18.04, bluetooth is crashing multiple times per day. + Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230:
[Kernel-packages] [Bug 1775443] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149479/+files/WifiSyslog.txt ** Description changed: - Posted a question here and it was recommended that I file a kernel bug - report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing + Here's the output of `grep blue /var/log/syslog`: + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) + Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 + Jun 6 09:12:41 Precision-5520
[Kernel-packages] [Bug 1775443] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149474/+files/ProcInterrupts.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775443] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149475/+files/ProcModules.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1768852] Re: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead
Thanks all for working on this. I've been trying to nail down the issues on my Thinkpad X1 Carbon for a couple of weeks and this seems to be the solution. I'm a little unclear from the bug report when this bug fix will be released, will it be in July with the 18.04.1 update? -- 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/1768852 Title: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: ===SRU Justification=== [Impact] When unplugging the Thunderbolt 3 cable from the TBT controller, kernel oops. [Test] The user confirms this patch works. [Fix] tty_unregister_driver may be called more than 1 time in some hotplug cases,it will cause the kernel oops. This patch checked dbc_tty_driver to make sure it is unregistered only 1 time. [Regression Potential] Low. The change is to guard against null pointer, so it's the correct behavior. ===Original Bugreport=== When unplugging the Thunderbolt 3 cable that was connected to a Lenovo Thunderbolt 3 Dock: [78402.194718] xhci_hcd :0f:00.0: remove, state 4 [78402.194726] usb usb8: USB disconnect, device number 1 [78402.194727] usb 8-2: USB disconnect, device number 2 [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, assume dead [78402.195086] xhci_hcd :0f:00.0: remove, state 1 [78402.195091] usb usb7: USB disconnect, device number 1 [78402.195092] usb 7-2: USB disconnect, device number 2 [78402.195094] usb 7-2.1: USB disconnect, device number 3 [78402.242648] usb 7-2.2: USB disconnect, device number 4 [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19 [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed. [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered [78402.247998] pcieport :0a:03.0: Refused to change power state, currently in D3 [78402.255841] xhci_hcd :0d:00.0: remove, state 1 [78402.255847] usb usb6: USB disconnect, device number 1 [78402.255849] usb 6-1: USB disconnect, device number 2 [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, status -108 [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered [78402.302679] xhci_hcd :0d:00.0: remove, state 1 [78402.302685] usb usb5: USB disconnect, device number 1 [78402.302687] usb 5-3: USB disconnect, device number 2 [78402.302688] usb 5-3.4: USB disconnect, device number 3 [78402.302689] usb 5-3.4.1: USB disconnect, device number 4 [78402.430677] usb 5-3.4.2: USB disconnect, device number 5 [78402.470512] usb 5-3.4.3: USB disconnect, device number 6 [78402.506481] usb 5-3.4.4: USB disconnect, device number 7 [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 0034 [78402.507540] IP: tty_unregister_driver+0xd/0x70 [78402.507542] PGD 0 P4D 0 [78402.507544] Oops: [#1] SMP PTI [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt [78402.507582] snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
[Kernel-packages] [Bug 1775443] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149477/+files/RfKill.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149476/+files/PulseList.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775443] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149478/+files/UdevDb.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149473/+files/ProcCpuinfoMinimal.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775443] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149472/+files/ProcCpuinfo.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775443] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149467/+files/CRDA.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149470/+files/Lspci.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149471/+files/Lsusb.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149469/+files/IwConfig.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
apport information ** Tags added: apport-collected ** Description changed: Posted a question here and it was recommended that I file a kernel bug report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3 Candidate: 5.48-0ubuntu3 Version table: *** 5.48-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 10:48:07 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-01-12 (145 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: cspencer 2416 F pulseaudio + CurrentDesktop: GNOME + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-01-12 (145 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + MachineType: Dell Inc. Precision 5520 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux-signed + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=602f267c-ef2b-4892-8b98-8dda563da166 ro acpi_rev_override quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-22-generic N/A + linux-backports-modules-4.15.0-22-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-22-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/23/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.9.4 + dmi.board.name: 06X96V + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5520 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149466/+files/AlsaInfo.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775443] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775443/+attachment/5149468/+files/CurrentDmesg.txt -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: Confirmed Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]:
[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state()
[Kernel-packages] [Bug 1772972] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: Confirmed => Invalid -- 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/1772972 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Bug description: 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: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
Commit 7fa32e5ec28b was actually mentioned in bug 1664663, an I don't think it factors into this bug. ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
Commit 7fa32e5ec28b was mentioned in the descriptions. However, that commit has been in mainlien since 4.15-rc3, so it's always been in 18.04. We may want to split the two issues in to two separate bugs, so they each get addressed. Do both issues still happen with the latest Bionic kernel? Per comment #6, it sounds liek the second issues still happens. How about the first issue, where the KVP daemon crashes after approximatively 2 minutes of uptime? -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker
** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772927] Re: linux: 4.15.0-23.25 -proposed tracker
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1772927 Title: linux: 4.15.0-23.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: 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: bug 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 1772942 (linux-azure-edge) derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 1772934 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker
** 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1772934 Title: linux-gcp: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775443] [NEW] Ubuntu 18.04 Bluetooth Crash
Public bug reported: Posted a question here and it was recommended that I file a kernel bug report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3 Candidate: 5.48-0ubuntu3 Version table: *** 5.48-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 10:48:07 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-01-12 (145 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic kernel -- 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/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux-signed package in Ubuntu: New Bug description: Posted a question here and it was recommended that I file a kernel bug report: https://askubuntu.com/questions/1044235/18-04-bluetooth- crashing $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3 Candidate: 5.48-0ubuntu3 Version table: *** 5.48-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 10:48:07 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-01-12 (145 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
In my own VMs, this does not affect linux-azure, it only affects the generic 4.15 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
Still an issue on Bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: Confirmed Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
I'm happy to create a new bug report for this, however before I do I wanted to follow up here first. I've been working on a bionic VM template this week and the issue has resurfaced. Client (18.04) reboots daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later, the CIFS mount point stops responding. Meanwhile other clients (16.04, and Windows) continue chugging along merrily. A reboot sometimes fixes the problem, and sometimes the problem has fixed itself by 8am when I arrive. Here's some syslog debug output after the machine finishes booting. Yesterday it cleared up on its own. Today the server is still down 10 hours later. I would blame Java, except that the whole mount point becomes non- responsive when this happens, not just for that one process. Jun 6 03:00:37 localhost systemd[1]: Reached target Multi-User System. Jun 6 03:00:37 localhost systemd[1]: Starting Execute cloud user/final scripts... Jun 6 03:00:37 localhost systemd[1]: Reached target Graphical Interface. Jun 6 03:00:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 6 03:00:38 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 running 'modules:final' at Wed, 06 Jun 2018 03:00:38 +. Up 23.72 seconds. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 finished at Wed, 06 Jun 2018 03:00:38 +. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 23.84 seconds Jun 6 03:00:38 localhost systemd[1]: Started Execute cloud user/final scripts. Jun 6 03:00:38 localhost systemd[1]: Reached target Cloud-init target. Jun 6 03:00:38 localhost systemd[1]: Startup finished in 2.806s (kernel) + 21.078s (userspace) = 23.885s. Jun 6 03:00:39 localhost kernel: [ 24.927412] TCP: ens160: Driver has suspect GRO implementation, TCP performance may be compromised. Jun 6 03:00:51 localhost systemd-timesyncd[574]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Jun 6 03:14:28 localhost systemd[1]: Starting Message of the Day... Jun 6 03:14:30 localhost 50-motd-news[1699]: * Meltdown, Spectre and Ubuntu: What are the attack vectors, Jun 6 03:14:30 localhost 50-motd-news[1699]:how the fixes work, and everything else you need to know Jun 6 03:14:30 localhost 50-motd-news[1699]:- https://ubu.one/u2Know Jun 6 03:14:30 localhost systemd[1]: Started Message of the Day. Jun 6 03:15:48 localhost systemd[1]: Starting Cleanup of Temporary Directories... Jun 6 03:15:48 localhost systemd[1]: Started Cleanup of Temporary Directories. Jun 6 03:17:01 localhost CRON[1770]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:00:01 localhost CRON[1878]: (root) CMD (/mnt/www/config/backup_config.sh) Jun 6 04:17:01 localhost CRON[1916]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] failed to bind to LDAP server ldap://dc01.example.com: Can't contact LDAP server Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] connected to LDAP server ldap://dc02.example.com Jun 6 04:30:01 localhost CRON[1938]: (root) CMD (/usr/sbin/ntpdate time-a.nist.gov time-b.nist.gov 0.pool.ntp.org 1.pool.ntp.org) Jun 6 04:30:01 localhost CRON[1937]: (CRON) info (No MTA installed, discarding output) Jun 6 05:12:02 localhost kernel: [ 7906.798052] CIFS VFS: Server cifshost.example.com has not responded in 120 seconds. Reconnecting... Jun 6 05:12:02 localhost kernel: [ 7906.800726] CIFS VFS: Free previous auth_key.response = 3e802799 Jun 6 05:13:10 localhost kernel: [ 7975.657719] INFO: task java:1672 blocked for more than 120 seconds. Jun 6 05:13:10 localhost kernel: [ 7975.657741] Not tainted 4.15.0-22-generic #24-Ubuntu Jun 6 05:13:10 localhost kernel: [ 7975.657757] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 6 05:13:10 localhost kernel: [ 7975.657779] javaD0 1672 1 0x8000 Jun 6 05:13:10 localhost kernel: [ 7975.657781] Call Trace: Jun 6 05:13:10 localhost kernel: [ 7975.657788] __schedule+0x297/0x8b0 Jun 6 05:13:10 localhost kernel: [ 7975.657791] ? __wake_up+0x13/0x20 Jun 6 05:13:10 localhost kernel: [ 7975.657792] schedule+0x2c/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657795] io_schedule+0x16/0x40 Jun 6 05:13:10 localhost kernel: [ 7975.657798] wait_on_page_bit_common+0xd8/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657800] ? page_cache_tree_insert+0xe0/0xe0 Jun 6 05:13:10 localhost kernel: [ 7975.657801] __filemap_fdatawait_range+0xfa/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657803] filemap_write_and_wait+0x4d/0x90 Jun 6 05:13:10 localhost kernel: [ 7975.657826] cifs_flush+0x43/0x90 [cifs] Jun 6 05:13:10 localhost kernel: [ 7975.657830] filp_close+0x2f/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657832] __close_fd+0x85/0xa0 Jun 6 05:13:10 localhost
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
(just for completeness reasons) Patches that were sent over: https://lists.ubuntu.com/archives/kernel-team/2018-May/thread.html#92233 -- 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to start Journal Service.
[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker
** 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/1772931 Title: linux-aws: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: 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: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
(collisionTwo from the same forum question above says he was experiencing this issue with an XPS 9560, mind you, which is a Kaby Lake Mobile CPU, so it's still a bit of conjecture until we get more specs from others experiencing the 'doesn't actually suspend and needs a hard reset to do anything' probem.) -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command
I'm way out of date on this, but that patch looks like it was committed into the Linux kernel in Mach 2015: https://github.com/torvalds/linux/commit/227a4fd801c8a9fa2c4700ab98ec1aec06e3b44d ... which would suggest that it would have appeared "in the wild" with 3.19.2 or thereabouts? Even if my timeline isn't completely accurate, and if that patch fixes the problem, then it should be ancient history by your 4.4.0 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/1313279 Title: xHCI host not responding to stop endpoint command Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 Hardware: Intel NUC D34010WYK (Core i3 4010U) Memory: 4 gigabytes USD device: PCTV 292e DVB-T tuner I have 2 PCTV 292e DVB-T tuners connected to the system. When I start to use either of the tuner, the xHCI host crashes. Since I'm booting from an USB disk. If I only connect 1 of the tuners, the system works ok. It does not matter which one of the tuners I connect. [ 68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. [ 68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host. Sometimes this also leads to this: [ 638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0 [ 638.183057] PGD 0 [ 638.183077] Oops: [#1] SMP I can also observe the same fault with OpenELEC Linux distribution that runs kernel 3.14 when I run the system from an internal SATA SSD drive (not from an external USB disk). lsusb -v: http://paste.ubuntu.com/7343384/ dmesg: http://sprunge.us/HMXH dmesg (crash type 2): http://sprunge.us/PSiX ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lubuntu-desktop 0.55 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 11:12:22 2014 InstallationDate: Installed on 2014-04-07 (19 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: lubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1313279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Matalak's Acer Aspire ES1-511 (from https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend where I found the 4.14 kernel solution) is also an Intel Celeron (N2830) CPU as far as I can tell from the specs. I've asked him to contribute to the bug report, but don't think he's seen my requests yet. I'll ask if he's using an SSD as well. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@Matze thanks for adding to the bug report - Here's where it starts to get interesting :) My problem laptop is an HP Pavilion x360 11-n013na with a quadcore Intel Pentium N3540 4GB of DDR3 Ram 250GB SSD (Samsung 850 EVO) I also have an HP Stream 11 with an Intel Celeron N2840 that does NOT have any suspend problems. The HP Stream is almost identical hardware-wise. Components such as the entire screen assembly, battery and USB board are inter-changeable (which I know because I have actually swapped them over!) So for the Stream to be fine, but the Pavilion to have suspend problems makes me curious about the differences. The Stream that suspends has eMMc storage and 2GB Ram (soldered to the main board :( ) With your Acer E13, you have an Intel Celeron based Atom CPU (N2940) coupled with an SSD. My Pavilion also has an Intel Celeron based Atom CPU (N3540) coupled with an SSD. (The 'Pentium' title for the N3540 is just a branding thing I believe - same architecture) So it is pure conjecture at the moment, but if we gather more people experiencing the same problem, I wonder if there might be a significant number of these Atom-style Celeron variant CPU's with an SSD as their main storage experiencing problems with suspend. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759961] Re: Update to bluez 5.50
** Summary changed: - Update to bluez 5.50 (mostly bug-fix release) + Update to bluez 5.50 -- 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/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
