[Kernel-packages] [Bug 1768435] 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 1768435 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 -- 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/1768435 Title: aio-dio-extend-stat test in aio_dio_bugs failed on s390x Status in linux package in Ubuntu: Incomplete Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file' write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file Exit status: 1 Duration: 0.10453414917 stdout: write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:24:25 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux
[Kernel-packages] [Bug 1768442] [NEW] package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab
Public bug reported: Crash happened on regular apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Apr 30 15:55:19 2018 ErrorMessage: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-04-30 (1 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1768442 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück Status in linux-signed package in Ubuntu: New Bug description: Crash happened on regular apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Apr 30 15:55:19 2018 ErrorMessage: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-04-30 (1 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: Unterprozess installed linux-image-4.15.0-20-generic package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768442/+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 1768225] Re: SD card not mounted
I can hardly answer this question. I got a new notebook and installed 17.10 (beta) on it. I could use the SD card initially. Then after official launch, all external devices caused system hangs during mount. After a restart, the SD card could be mounted as sdc With 18.04 the device drivers (sdhci and sdhci-pci) are not loaded and the device does not get recognized. Even when loading the modules the medium does not get mounted. As this is my production machine and I am using it heavily this semester I am rather reluctant to experimenting with different kernels (I am not sure but the disability to mount harddisks after suspend to RAM came in at the same time as I installed a premature 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/1768225 Title: SD card not mounted Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 after fresh install: HW: Macbook Pro Retina 13" SD cards are not recognized nor mounted. The sdhci driver is not loaded by default. Manual loading of sdhci and sdhci-pci does not make the SD card mount or be recognized (loading the driver is acknowledged in the syslog) Adding a configuration file under /etc/modprobe.d with options sdhci debug_quirks2=4 does not remedy the situation. (the cards and adapters tested work fine on other - older - Macs) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 1636 F pulseaudio /dev/snd/controlC1: wolf 1636 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 1 13:05:54 2018 HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d InstallationDate: Installed on 2018-04-30 (1 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 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768225/+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 1768452] [NEW] Unable to insert test_bpf module on Xenial s390x
Public bug reported: After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-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) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768452 Title: Unable to insert test_bpf module on Xenial s390x Status in linux package in Ubuntu: Confirmed Bug description: After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768452/+subscription
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
Please try the kernel here: https://people.canonical.com/~khfeng/lp1768292/ -- 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1e/0x20 May 01 10:05:04 galvin-T570 kernel: bus_add_dri
[Kernel-packages] [Bug 1768452] 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/1768452 Title: Unable to insert test_bpf module on Xenial s390x Status in linux package in Ubuntu: Confirmed Bug description: After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768452/+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 1765698] Re: Unable to insert test_bpf module on Xenial
After discussed with Stefan, we both agree to have the issue on s390x reported in a new bug: bug 1768452 Therefore I'm marking this one as verification-done, thanks. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765698 Title: Unable to insert test_bpf module on Xenial Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: [SRU Justification] Impact: One of the self-tests which is run by test_bpf will always fail when JIT is turned on, causing the module load to fail. Fix: Picking two patches from upstream will fix this. Testcase: sudo modprobe test_bpf Risk of regression: Minimal, this modifies only a test module, no impact on normal operation. --- With 4.4.0-119, the ubuntu_bpf_jit test will pass: [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] PASSED: 291 FAILED: 0 But with 4.4.0-121, one test will fail [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] PASSED: 290 FAILED: 1 stderr: modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ dmesg|grep test_bpf|grep FAIL [ 45.286944] test_bpf: #248 BPF_MAXINSNS: Jump, gap, jump, ... FAIL to prog_create err=-524 len=4096 [ 45.619293] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-121-generic 4.4.0-121.145 ProcVersionSignature: User Name 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 12:29 seq crw-rw 1 root audio 116, 33 Apr 20 12:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 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: CurrentDmesg: Date: Fri Apr 20 12:32:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: 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.4.0-121-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-121-generic N/A linux-backports-modules-4.4.0-121-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: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765698/+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 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1604036 Title: Upgrade printer-driver-ptouch to support Brother QL-570 Status in hwdata package in Ubuntu: Confirmed Status in ptouch-driver package in Ubuntu: Fix Released Status in usbutils package in Ubuntu: Confirmed Status in hwdata source package in Xenial: New Status in ptouch-driver source package in Xenial: Triaged Status in usbutils source package in Xenial: New Bug description: Please, upgrade printer-driver-ptouch to support Brother QL-570 P-touch Label Printer. See https://bitbucket.org/philpem/printer- driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt (motivate maintainers of printer-driver-ptouch to bump their version number and release a version that supports QL-570) and also upgrade usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+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 1763454] Re: bpf_map_lookup_elem: BUG: unable to handle kernel paging request
Ubuntu 4.4.0-123.147-generic 4.4.128 does fix it for us 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/1763454 Title: bpf_map_lookup_elem: BUG: unable to handle kernel paging request Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Some unfortunate timing between the fix for CVE-2017-17862 being backported and some updates from upstream stable resulted in us not having some hunks from the CVE patch. This is causing oopses (see below). Fix: Add in the missing hunks from the CVE patch. Test case: See test results in comment #4. Regression potential: This just updates the code to match the upstream patch, which has been upstream for months, so regression potential should be low. --- Hey, we are currently debugging an issue with Scope [1] where the initialization of the used tcptracer-bpf [2] leads to a kernel oops at the first call of `bpf_map_lookup_elem`. The OS is Ubuntu Xenial with kernel version `Ubuntu 4.4.0-119.143-generic 4.4.114`. `4.4.0-116.140` does not show the problem. Example: ``` [ 58.763045] BUG: unable to handle kernel paging request at 3c0c41a8 [ 58.846450] IP: [] bpf_map_lookup_elem+0x6/0x20 [ 58.909436] PGD 80003be04067 PUD 3bea1067 PMD 0 [ 58.914876] Oops: [#1] SMP [ 58.915581] Modules linked in: 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 ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc overlay vboxsf isofs ppdev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vboxguest input_leds serio_raw parport_pc parport video ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mptspi aesni_intel scsi_transport_spi mptscsih aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd mptbase psmouse e1000 [ 59.678145] CPU: 1 PID: 1810 Comm: scope Not tainted 4.4.0-119-generic #143-Ubuntu [ 59.790501] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 59.846405] task: 88003ae23800 ti: 880022c84000 task.ti: 880022c84000 [ 60.000524] RIP: 0010:[] [] bpf_map_lookup_elem+0x6/0x20 [ 60.178029] RSP: 0018:880022c87960 EFLAGS: 00010082 [ 60.257957] RAX: 8117cd70 RBX: c922f090 RCX: [ 60.350704] RDX: RSI: 880022c87ba8 RDI: 3c0c4180 [ 60.449182] RBP: 880022c87be8 R08: R09: 0800 [ 60.547638] R10: 88003ae23800 R11: 88003ca12e10 R12: [ 60.570757] R13: 88003c601200 R14: 88003fd10020 R15: 880022c87d10 [ 60.678811] FS: 7f95ba372700() GS:88003fd0() knlGS: [ 60.778636] CS: 0010 DS: ES: CR0: 80050033 [ 60.866380] CR2: 3c0c41a8 CR3: 3aeae000 CR4: 00060670 [ 60.963736] DR0: DR1: DR2: [ 61.069195] DR3: DR6: fffe0ff0 DR7: 0400 [ 61.187006] Stack: [ 61.189256] 880022c87be8 81177411 0001 [ 61.253133] 3c0c4180 880022c87ba8 [ 61.345334] 880022c87d10 0001 [ 61.459069] Call Trace: [ 61.505273] [] ? __bpf_prog_run+0x7a1/0x1360 [ 61.625511] [] ? update_curr+0x79/0x170 [ 61.741423] [] ? update_cfs_shares+0xbc/0x100 [ 61.837892] [] ? __schedule+0x30d/0x7f0 [ 61.941349] [] ? __schedule+0x301/0x7f0 [ 62.073874] [] ? __schedule+0x30d/0x7f0 [ 62.185260] [] ? __schedule+0x301/0x7f0 [ 62.186239] [] ? __schedule+0x30d/0x7f0 [ 62.305193] [] ? __schedule+0x301/0x7f0 [ 62.399854] [] ? __schedule+0x30d/0x7f0 [ 62.406219] [] ? __schedule+0x301/0x7f0 [ 62.407994] [] ? __schedule+0x30d/0x7f0 [ 62.410491] [] ? __schedule+0x301/0x7f0 [ 62.431220] [] ? __schedule+0x30d/0x7f0 [ 62.497078] [] ? __schedule+0x30d/0x7f0 [ 62.559245] [] ? __schedule+0x301/0x7f0 [ 62.661493] [] ? __schedule+0x30d/0x7f0 [ 62.712927] [] ? __schedule+0x301/0x7f0 [ 62.799216] [] trace_call_bpf+0x37/0x50 [ 62.881570] [] kprobe_perf_func+0x37/0x250 [ 62.977365] [] ? finish_task_switch+0x76/0x230 [ 62.981405] [] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [ 63.092978] [] kprobe_dispatcher+0x31/0x50 [ 63.184696] [] ? tcp_clos
[Kernel-packages] [Bug 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code
On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>> wrote:
>> > On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
>> >> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
>> >> wrote:
>> >>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>> wrote:
>> > Hi Rafael,
>> >
>> > A kernel bug report was opened against Ubuntu [0]. After a kernel
>> > bisect, it was found that reverting the following two commits resolved
>> > this bug:
>> >
>> > 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space
>> > restoration")
>> > 0847684cfc5f("PCI / PM: Simplify device wakeup settings code")
>> >
>> > This is a regression introduced in v4.13-rc1 and still exists in
>> > mainline. The bug causes the battery to drain when the system is
>> > powered down and unplugged, which does not happed prior to these two
>> > commits.
>> What system and what do you mean by "powered down"? How much time
>> does it take for the battery to drain now?
>> >>> By powered down, the bug reporter is saying physically powered off and
>> >>> unplugged. The system is a HP laptop:
>> >>>
>> >>> dmi.chassis.vendor: HP
>> >>> dmi.product.family: 103C_5335KV HP Notebook
>> >>> dmi.product.name: HP Notebook
>> >>> vendor_id: GenuineIntel
>> >>> cpu family: 6
>> >>>
>> >>>
>> > The bisect actually pointed to commit de3ef1e, but reverting
>> > these two commits fixes the issue.
>> >
>> > I was hoping to get your feedback, since you are the patch author. Do
>> > you think gathering any additional data will help diagnose this issue,
>> > or would it be best to submit a revert request?
>> First, reverting these is not an option or you will break systems
>> relying on them now. 4.13 is three releases back at this point.
>>
>> Second, your issue appears to be related to the suspend/shutdown path
>> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
>> change in pci_enable_wake() causes the problem to happen. Can you try
>> to revert this one alone and see if that helps?
>> >>> A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
>> >>> tested. However, the test kernel still exhibited the bug.
>> >> So essentially the bisection result cannot be trusted.
>> >
>> > We performed some more testing and confirmed just a revert of the
>> > following commit resolves the bug:
>> >
>> > 0847684cfc5f0 ("PCI / PM: Simplify device wakeup settings code")
>>
>> Thanks for confirming this!
>>
>> > Can you think of any suggestions to help debug further?
>>
>> The root cause of the regression is likely the change in
>> pci_enable_wake() removing the device_may_wakeup() check from it.
>>
>> Probably, one of the drivers in the platform calls pci_enable_wake()
>> directly from its ->shutdown() callback and that causes the device to
>> be set up for system wakeup which in turn causes the power draw while
>> the system is off to increase.
>>
>> I would look at the PCI drivers used on that platform to find which of
>> them call pci_enable_wake() directly from ->shutdown() and I would
>> make these calls conditional on device_may_wakeup().
>
> I took a quick look with
>
> git grep -E "pci_enable_wake\(.*[^0]\);|device_may_wakeup"
>
> and didn't notice any pci_enable_wake() callers that called
> device_may_wakeup() first.
>
> Probably a dumb question, but would it make sense to restore the
> device_may_wakeup() check in pci_enable_wake(), e.g.,
At least as a matter of test, yes, it would, but not this way:
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index e597655a5643..9fa64c175f92 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -1932,6 +1932,9 @@ int pci_enable_wake(struct pci_dev *dev, pci_power_t
> state, bool enable)
> {
> int ret = 0;
>
> + if (enable && !device_may_wakeup(&dev->dev))
> + return -EINVAL;
> +
> /*
> * Bridges can only signal wakeup on behalf of subordinate devices,
> * but that is set up elsewhere, so skip them.
because that would break runtime PM wakeup for devices that aren't
allowed to wake up the system from sleep.
Anyway, if the patch above makes the problem go away, it will mean we
are on the right track.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745646
Title:
Battery drains when laptop is off (shutdown)
Status in Linux:
Unknown
Status in acpi package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in acpi source package in Artful:
New
Status in linux source package in Artful:
In Progress
Status in acpi source package in Bionic:
Confirmed
Statu
[Kernel-packages] [Bug 1766308] Re: inexplicably large file reported by zfs filesystem
@Matt, did the above help? -- 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/1766308 Title: inexplicably large file reported by zfs filesystem Status in zfs-linux package in Ubuntu: Triaged Bug description: I have a zfs filesystem containing a single qemu kvm disk image. The vm has been working normally. The image file is only allocated 10G, however today I became aware that the file, when examined from the ZFS host (hypervisor) is reporting an inexplicable, massive file size of around 12T. 12T is larger than the pool itself. Snapshots or other filesystem features should not be involved. I'm suspicious that the file(system?) has been corrupted. root@fusion:~# ls -l /data/store/vms/plexee/ total 6164615 -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root ^^ !! root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root image: /data/store/vms/plexee//plexee-root file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 5.9G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee NAME USED AVAIL REFER MOUNTPOINT rpool/DATA/fusion/store/vms/plexee 5.88G 484G 5.88G /data/store/vms/plexee root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee NAMEPROPERTY VALUE SOURCE rpool/DATA/fusion/store/vms/plexee type filesystem - rpool/DATA/fusion/store/vms/plexee creation Mon Mar 26 9:50 2018 - rpool/DATA/fusion/store/vms/plexee used 5.88G - rpool/DATA/fusion/store/vms/plexee available 484G - rpool/DATA/fusion/store/vms/plexee referenced5.88G - rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee mounted yes - rpool/DATA/fusion/store/vms/plexee quota none default rpool/DATA/fusion/store/vms/plexee reservation none default rpool/DATA/fusion/store/vms/plexee recordsize128K default rpool/DATA/fusion/store/vms/plexee mountpoint /data/store/vms/plexee inherited from rpool/DATA/fusion rpool/DATA/fusion/store/vms/plexee sharenfs off default rpool/DATA/fusion/store/vms/plexee checksum on default rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee atime off inherited from rpool rpool/DATA/fusion/store/vms/plexee devices off inherited from rpool rpool/DATA/fusion/store/vms/plexee exec on default rpool/DATA/fusion/store/vms/plexee setuidon default rpool/DATA/fusion/store/vms/plexee readonly off default rpool/DATA/fusion/store/vms/plexee zoned off default rpool/DATA/fusion/store/vms/plexee snapdir hidden default rpool/DATA/fusion/store/vms/plexee aclinheritrestricted default rpool/DATA/fusion/store/vms/plexee canmount on default rpool/DATA/fusion/store/vms/plexee xattr on default rpool/DATA/fusion/store/vms/plexee copies1 default rpool/DATA/fusion/store/vms/plexee version 5 - rpool/DATA/fusion/store/vms/plexee utf8only off - rpool/DATA/fusion/store/vms/plexee normalization none - rpool/DATA/fusion/store/vms/plexee casesensitivity sensitive - rpool/DATA/fusion/store/vms/plexee vscan off default rpool/DATA/fusion/store/vms/plexee nbmandoff default rpool/DATA/fusion/store/vms/plexee sharesmb off default rpool/DATA/fusion/store/vms/plexee refquota none default rpool/DATA/fusion/store/vms/plexee refreservationnone default rpool/DATA/fusion/store/vms/plexee primarycache all default rpool/DATA/fusion/store/vms/plexee secondarycacheall
[Kernel-packages] [Bug 1767452] Re: kernel oops when I undocked
Yea, I cannot do a shutdown, it will hang during something with thunderbolt and I have to do a hard poweroff :/ -- 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/1767452 Title: kernel oops when I undocked Status in linux-signed package in Ubuntu: Confirmed Bug description: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth 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 overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd e1000e glue_helper c
[Kernel-packages] [Bug 1755132] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2018-05-02 04:56 EDT--- Counters available with 4.15.0-20-generic -- 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/1755132 Title: KVM: s390: add vcpu stat counters for many instruction Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: The overall instruction counter is larger than the sum of the single counters. We should try to catch all instruction handlers to make this match the summary counter. Let us add sck,tb,sske,iske,rrbe,tb,tpi,tsch,lpsw,pswe and remove other unused ones. Available since kerne. 4.16 rc1 commit-id : a37cb07a30f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1755132/+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 1326761] Re: Tevii S471 DVB-S2 card hangs on firmware upload
This issue affecting me too, just as others have said here. I have a new system lubuntu 16.04, and running mythtv. george@tvbox:~$ uname -a Linux tvbox 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux For me the issue is more that my logs are bing spammed May 2 08:46:55 tvbox kernel: [155280.001493] ds3000_firmware_ondemand: Waiting for firmware upload(2)... May 2 09:17:57 tvbox kernel: [157141.510264] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... May 2 09:17:57 tvbox kernel: [157141.510320] ds3000_firmware_ondemand: Waiting for firmware upload(2)... May 2 09:18:18 tvbox kernel: [157162.782878] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... May 2 09:18:18 tvbox kernel: [157162.782974] ds3000_firmware_ondemand: Waiting for firmware upload(2)... Everything works, although it does take some time for the tuner to change channels and I can't say if the firmware (or lack of it) is affecting this. I would love to see some resolution or workaround for this. I'm happy to provide more information from my sysem if it will help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326761 Title: Tevii S471 DVB-S2 card hangs on firmware upload Status in linux package in Ubuntu: Confirmed Bug description: I have fresh installed Ubuntu Trusty Tahr (Server) with kernel 3.13.0-29. Firmware file dvb-fe-ds3000.fw is putted into /lib/firmware On a system cold start I see in syslog: Jun 5 16:00:54 MMC kernel: [9.601460] cx23885 driver version 0.0.3 loaded Jun 5 16:00:54 MMC kernel: [9.601881] CORE cx23885[0]: subsystem: d471:9022, board: TeVii S471 [card=35,autodetected] Jun 5 16:00:54 MMC kernel: [9.750010] cx23885_dvb_register() allocating 1 frontend(s) Jun 5 16:00:54 MMC kernel: [9.758499] cx23885[0]: cx23885 based dvb card Jun 5 16:00:54 MMC kernel: [9.879035] DVB: registering new adapter (cx23885[0]) Jun 5 16:00:54 MMC kernel: [9.879047] cx23885 :01:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)... Jun 5 16:00:54 MMC kernel: [9.894578] cx23885_dev_checkrevision() Hardware revision = 0xa5 Jun 5 16:00:54 MMC kernel: [9.894595] cx23885[0]/0: found at :01:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xfe80 But if I try to scan channels by scan or tvheadend I see this repeated lines: Jun 5 16:01:04 MMC kernel: [ 20.051633] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... Jun 5 16:01:04 MMC kernel: [ 20.052608] ds3000_firmware_ondemand: Waiting for firmware upload(2)... Card works under Debian linux kernel image from unstable repo (linux- image-3.14.1) manjur@MMC:~$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 manjur@MMC:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 3.13.0.29.35 Candidate: 3.13.0.29.35 Version table: *** 3.13.0.29.35 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.13.0.27.33 0 500 http://kz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 3.13.0.24.28 0 500 http://kz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.52 ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Jun 5 17:31:07 2014 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=e93b9d23-aced-4d3c-bb1e-07346406d8de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: E350M1
[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)
--- Comment From anjutsudha...@in.ibm.com 2018-05-02 05:19 EDT--- (In reply to comment #39) > Verified with test kernel : Issue is resolved. > === > > > > But hitting another trace : > > [ 294.764782] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 315.685952] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 317.385747] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 335.030061] hrtimer: interrupt took 1494725987 ns > [ 386.576484] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 403.964295] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 414.884012] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 431.700329] perf: Dynamic interrupt throttling disabled, can hang your > system! > [ 471.108095] INFO: rcu_sched self-detected stall on CPU > [ 471.108214]116-: (5250 ticks this GP) > idle=c9a/142/0 > softirq=6343/6344 fqs=2625 > [ 471.108351] (t=5251 jiffies g=8835 c=8834 q=1160) > [ 471.108508] Task dump for CPU 116: > [ 471.108518] perf_fuzzer R running task0 5428 5267 > 0x0004a006 > [ 471.108549] Call Trace: > [ 471.108582] [c0002038e74231c0] [c0149e98] > sched_show_task.part.16+0xd8/0x110 (unreliable) > [ 471.108627] [c0002038e7423230] [c01a9e5c] > rcu_dump_cpu_stacks+0xd4/0x138 > [ 471.108664] [c0002038e7423280] [c01a8f28] > rcu_check_callbacks+0x8e8/0xb40 > [ 471.108698] [c0002038e74233b0] [c01b71c8] > update_process_times+0x48/0x90 > [ 471.108731] [c0002038e74233e0] [c01cef14] > tick_sched_handle.isra.5+0x34/0xd0 > [ 471.108760] [c0002038e7423410] [c01cf010] > tick_sched_timer+0x60/0xe0 > [ 471.108795] [c0002038e7423450] [c01b7d74] > __hrtimer_run_queues+0x144/0x370 > [ 471.108830] [c0002038e74234d0] [c01b8ccc] > hrtimer_interrupt+0xfc/0x350 > [ 471.108867] [c0002038e74235a0] [c00248f0] > __timer_interrupt+0x90/0x260 > [ 471.108903] [c0002038e74235f0] [c0024d08] > timer_interrupt+0x98/0xe0 > [ 471.108943] [c0002038e7423620] [c000b998] > fast_exception_return+0x148/0x16c > [ 471.108990] --- interrupt: 901 at arch_local_irq_restore+0x84/0x90 >LR = __do_softirq+0xd8/0x3e4 > [ 471.109017] [c0002038e7423910] [c01b8d60] > hrtimer_interrupt+0x190/0x350 (unreliable) > [ 471.109054] [c0002038e7423930] [c0cffbc8] __do_softirq+0xd8/0x3e4 > [ 471.109089] [c0002038e7423a10] [c0115928] irq_exit+0xe8/0x120 > [ 471.109124] [c0002038e7423a30] [c0024d0c] > timer_interrupt+0x9c/0xe0 > [ 471.109164] [c0002038e7423a60] [c000b998] > fast_exception_return+0x148/0x16c > [ 471.109211] --- interrupt: 901 at mutex_unlock+0x18/0x50 >LR = perf_event_for_each_child+0xb0/0xf0 > [ 471.109236] [c0002038e7423d50] [c02b9e70] > perf_event_for_each_child+0x60/0xf0 (unreliable) > [ 471.109279] [c0002038e7423d90] [c02c4da8] > perf_event_task_enable+0x78/0xe0 > [ 471.109309] [c0002038e7423dd0] [c012d4e4] SyS_prctl+0x364/0x6a0 > [ 471.109345] [c0002038e7423e30] [c000b184] system_call+0x58/0x6c > [ 477.935937] watchdog: BUG: soft lockup - CPU#116 stuck for 23s! > [perf_fuzzer:5428] > [ 477.936042] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) > ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) > nf_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) > nf_conntrack(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) bridge(E) > stp(E) llc(E) ebtable_filter(E) ebtables(E) ip6table_filter(E) ip6_tables(E) > iptable_filter(E) kvm_hv(E) kvm(E) at24(E) ofpart(E) ipmi_powernv(E) > ipmi_devintf(E) ipmi_msghandler(E) uio_pdrv_genirq(E) uio(E) cmdlinepart(E) > powernv_flash(E) mtd(E) ibmpowernv(E) opal_prd(E) vmx_crypto(E) > sch_fq_codel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) > iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) > ip_tables(E) x_tables(E) autofs4(E) btrfs(E) zstd_compress(E) raid10(E) > raid456(E) async_raid6_recov(E) async_memcpy(E) > [ 477.936571] async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) > libcrc32c(E) raid1(E) raid0(E) multipath(E) linear(E) ast(E) mlx5_core(E) > i2c_algo_bit(E) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) > fb_sys_fops(E) ttm(E) crct10dif_vpmsum(E) ahci(E) mlxfw(E) crc32c_vpmsum(E) > drm(E) tg3(E) libahci(E) devlink(E) > [ 477.936833] CPU: 116 PID: 5428 Comm: perf_fuzzer Tainted: GE > 4.15.0-20-generic #21 > [ 477.936850] NIP: c0016e84 LR: c0cffbc8 CTR: > c0024480 > [ 477.936870] REGS: c0002038e7423690 TRAP: 0901 Tainted: GE > (4.15.0-20-generic) > [ 477.936879] MSR: 90009033 CR: > 48000244 XER: 2004 > [ 477.936970] CFAR: c0016e30 SOFTE: 1 >GPR00: c0cffbc8 c0002038e7423910 c0
[Kernel-packages] [Bug 1768474] [NEW] Xenial update to 4.4.130 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.130 upstream stable 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.130 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => 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/1768474 Title: Xenial update to 4.4.130 stable release Status in linux package in Ubuntu: Invalid 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.130 upstream stable 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.130 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768474/+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 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+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 1755132] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-05-02 05:24 EDT--- IBM Bugzilla status closed, Fix Released by Canonical, and verified by IBM -- 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/1755132 Title: KVM: s390: add vcpu stat counters for many instruction Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: The overall instruction counter is larger than the sum of the single counters. We should try to catch all instruction handlers to make this match the summary counter. Let us add sck,tb,sske,iske,rrbe,tb,tpi,tsch,lpsw,pswe and remove other unused ones. Available since kerne. 4.16 rc1 commit-id : a37cb07a30f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1755132/+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 1766201] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2018-05-02 05:36 EDT--- State: Open by: stccdenv on 02 May 2018 04:33:30 Hi Linux Team, Is there any status on this dev sr0 issue that we are encountering even after upgrading to the mainline kernel 4.17.0-041700rc2-generic. -- 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/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/log/nts_linux-hjmh_180418_0703.tbz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06 devops4p07: /tmp/ctsupt/ctsnap.devops4p07.04180601.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.devops4p07.04180601.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/tmp/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.x
[Kernel-packages] [Bug 1766603] Re: linux-lts-trusty: 3.13.0-146.195~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: 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: 1766601 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Wednesday, 02. May 2018 10:03 UTC ** Description changed: 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: 1766601 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Wednesday, 02. May 2018 10:03 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1766603 Title: linux-lts-trusty: 3.13.0-146.195~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1766601 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/1766603/+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 1762693] Re: No network with e1000e driver on 4.13.0-38-generic
> This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results.
Sorry, I no longer can :(
Kai-Heng's test build worked fine for me, but another artful kernel
update without the fix then broke my networking again. After that, I
upgraded to bionic.
--
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/1762693
Title:
No network with e1000e driver on 4.13.0-38-generic
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Committed
Status in linux-oem source package in Artful:
Invalid
Bug description:
===SRU Justification===
[Impact]
e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
The regression was introduced by patches in LP: #1730550.
[Fix]
Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
e1000e now reports correct link status.
[Test]
With the extra commit, the e1000e starts to working again.
[Regression Potential]
Low.
It says:
Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
So it's pretty clear this patch is to fix the regression.
It's in upstream linux-stable, so only Arftul needs this patch.
===Original Bug Report===
When my computer boots with the most recent kernel 4.13.0-38-generic, I don't
have a working network connection. ethtool reports that my network interface
doesn't have a connection:
martin@dogmeat ~ % cat ethtool.txt
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
drv probe link
Link detected: no
dmesg contains suspicious e1000e error messages:
martin@dogmeat ~ % tail -n 40 dmesg.txt
[ 20.211715] Could not find valid key in user session keyring for sig
specified in mount option: [459a10809c211381]
[ 20.211716] One or more global auth toks could not properly register; rc =
[-2]
[ 20.211717] Error parsing options; rc = [-2]
[ 25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 51.244686] ahci :00:17.0: port does not support device sleep
[ 56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[ 99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[ 104.038668] e1000e
[Kernel-packages] [Bug 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code
On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>> wrote:
>> > On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
>> >> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
>> >> wrote:
>> >>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>> wrote:
>> > Hi Rafael,
>> >
>> > A kernel bug report was opened against Ubuntu [0]. After a kernel
>> > bisect, it was found that reverting the following two commits resolved
>> > this bug:
>> >
>> > 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space
>> > restoration")
>> > 0847684cfc5f("PCI / PM: Simplify device wakeup settings code")
>> >
>> > This is a regression introduced in v4.13-rc1 and still exists in
>> > mainline. The bug causes the battery to drain when the system is
>> > powered down and unplugged, which does not happed prior to these two
>> > commits.
>> What system and what do you mean by "powered down"? How much time
>> does it take for the battery to drain now?
>> >>> By powered down, the bug reporter is saying physically powered off and
>> >>> unplugged. The system is a HP laptop:
>> >>>
>> >>> dmi.chassis.vendor: HP
>> >>> dmi.product.family: 103C_5335KV HP Notebook
>> >>> dmi.product.name: HP Notebook
>> >>> vendor_id: GenuineIntel
>> >>> cpu family: 6
>> >>>
>> >>>
>> > The bisect actually pointed to commit de3ef1e, but reverting
>> > these two commits fixes the issue.
>> >
>> > I was hoping to get your feedback, since you are the patch author. Do
>> > you think gathering any additional data will help diagnose this issue,
>> > or would it be best to submit a revert request?
>> First, reverting these is not an option or you will break systems
>> relying on them now. 4.13 is three releases back at this point.
>>
>> Second, your issue appears to be related to the suspend/shutdown path
>> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
>> change in pci_enable_wake() causes the problem to happen. Can you try
>> to revert this one alone and see if that helps?
>> >>> A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
>> >>> tested. However, the test kernel still exhibited the bug.
>> >> So essentially the bisection result cannot be trusted.
>> >
>> > We performed some more testing and confirmed just a revert of the
>> > following commit resolves the bug:
>> >
>> > 0847684cfc5f0 ("PCI / PM: Simplify device wakeup settings code")
>>
>> Thanks for confirming this!
>>
>> > Can you think of any suggestions to help debug further?
>>
>> The root cause of the regression is likely the change in
>> pci_enable_wake() removing the device_may_wakeup() check from it.
>>
>> Probably, one of the drivers in the platform calls pci_enable_wake()
>> directly from its ->shutdown() callback and that causes the device to
>> be set up for system wakeup which in turn causes the power draw while
>> the system is off to increase.
>>
>> I would look at the PCI drivers used on that platform to find which of
>> them call pci_enable_wake() directly from ->shutdown() and I would
>> make these calls conditional on device_may_wakeup().
>
> I took a quick look with
>
> git grep -E "pci_enable_wake\(.*[^0]\);|device_may_wakeup"
>
> and didn't notice any pci_enable_wake() callers that called
> device_may_wakeup() first.
I've just look at a bunch of network drivers doing that.
It looks like I may need to restore __pci_enable_wake() with an extra
"runtime" argument for internal use.
Joseph, can you ask the reporter to test the Bjorn's patch, please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745646
Title:
Battery drains when laptop is off (shutdown)
Status in Linux:
Unknown
Status in acpi package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in acpi source package in Artful:
New
Status in linux source package in Artful:
In Progress
Status in acpi source package in Bionic:
Confirmed
Status in linux source package in Bionic:
In Progress
Bug description:
I am using hp AY008tx laptop , and many other laptop users (HP) are also
facing the same issue . The problem don't occur when i install windows 10 .
Now, only ubuntu is installed.
i am using latest bios insyde20 rev 5.(latest)
WOL disabled and no usb device connected
checked my battery .
it don't happen when i remove battery and plug it again after shutdown.
tried laptop_mode_tools and tpl too
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: linux (Ubuntu Bionic) Status: Invalid => 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/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New 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 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+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 1768496] [NEW] test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
Public bug reported: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug arm64 artful uec-images -- 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in linux package in Ubuntu: Incomplete Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768496/+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 1768496] 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 1768496 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 -- 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in linux package in Ubuntu: Incomplete Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768496/+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 1768496] Re: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
** Summary changed: - test_260_config_arm_pan from kernel_security_test failed on Xenial ARM64 system + test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system ** Description changed: - It looks like this test should be skipped on Xenial (kernel < 4.15) + It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. + Ensure PAN for arm processors is set ... (skipped: + CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL - Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL - - == - FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) - Ensure PAN for arm processors is set - -- - Traceback (most recent call last): - File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan - self.assertEqual(expected, self._test_config(config_name)) - AssertionError: False != True + == + FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) + Ensure PAN for arm processors is set + -- + Traceback (most recent call last): + File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan + self.assertEqual(expected, self._test_config(config_name)) + AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 2 09:54 seq - crw-rw 1 root audio 116, 33 May 2 09:54 timer + total 0 + crw-rw 1 root audio 116, 1 May 2 09:54 seq + crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: - linux-restricted-modules-4.13.0-39-generic N/A - linux-backports-modules-4.13.0-39-generic N/A - linux-firmware 1.169.3 + linux-restricted-modules-4.13.0-39-generic N/A + linux-backports-modules-4.13.0-39-generic N/A + linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in linux package in Ubuntu: Incomplete Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: comm
[Kernel-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
The scan is forced to be done synchronously, however the ipr driver is available and is loaded much earlier in the install process, thus it should not significantly affect the overall install time. One may be able to notice the difference a bit more with a fully- automated preseed install. ** Changed in: debian-installer (Ubuntu) Status: Invalid => 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/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: ---Problem Description--- Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based HDD/RAID arrays Tried with current bionic and current bionic-proposed installers wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e ---uname output--- uname -a Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:05:20 UTC 2018 ppc64le GNU/Linux Machine Type = 8247-22L (S822L) ---boot type--- Network boot ---bootloader--- petitboot shell ---Kernel cmdline used to launch install--- #cat /proc/cmdline ---Bootloader protocol--- http ---Install repository type--- Internet repository ---Install repository Location--- US ---Point of failure--- Problem during post-install (stage 2) configuration or other problem seen after reboot ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? ? ?? ? ? ??? moves; selects; activates buttons ~ # lsmod | grep -i ipr ipr 148677 0 ~ # modinfo ipr filename: /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko version:2.6.4 license:GPL description:IBM Power RAID SCSI Adapter Driver author: Brian King srcversion: 05BB872A11F65B3A73AB352 alias: pci:v1014d04DAsv1014sd04FBbc*sc*i* alias: pci:v1014d04DAsv1014sd04FCbc*sc*i* alias: pci:v1014d034Asv1014sd04C9bc*sc*i* alias: pci:v1014d034Asv1014sd04C8bc*sc*i* alias: pci:v1014d034Asv1014sd04C7bc*sc*i* alias: pci:v1014d034Asv1014sd049Cbc*sc*i* alias: pci:v1014d034Asv1014sd049Bbc*sc*i* alias: pci:v1014d034Asv1014sd049Abc*sc*i* alias: pci:v1014d034Asv1014sd0499bc*sc*i* alias: pci:v1014d034Asv1014sd0475bc*sc*i* alias: pci:v1014d034Asv1014sd0474bc*sc*i* alias: pci:v1014d034Asv1014sd04CAbc*sc*i* alias: pci:v1014d034Asv1014sd046Dbc*sc*i* alias: pci:v1014d034Asv1014sd03FEbc*sc*i* alias: pci:v1014d034Asv1014sd03FFbc*sc*i* alias: pci:v1014d034Asv1014sd03FCbc*sc*i* alias: pci:v1014d034Asv1014sd03FBbc*sc*i* alias: pci:v1014d034Asv1014sd035Ebc*sc*i* alias:
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Hello, I have the same issue with my laptop (very annoying). I will try to upgrade to 18.04, see if it fixes, and, if not, try on s-breedveld solution. $ sudo lshw [sudo] Mot de passe de alex : Désolé, essayez de nouveau. [sudo] Mot de passe de alex : tignasse description: Ordinateur portable produit: Skylake Platform (System SKUNumber) fabriquant: Intel Corporation version: 0.1 numéro de série: System Serial Number bits: 64 bits fonctionnalités: smbios-3.0 dmi-3.0 smp vsyscall32 configuration: boot=normal chassis=laptop family=Skylake System sku=System SKUNumber uuid=00020003-0004-0005-0006-000700080009 *-core description: Carte mère produit: WhiteTip Mountain1 Fab2 fabriquant: Topstar identifiant matériel: 0 version: RVP7 numéro de série: 1 emplacement: Part Component *-firmware description: BIOS fabriquant: American Megatrends Inc. identifiant matériel: 0 version: 5.11 date: 11/06/2015 taille: 64KiB capacité: 6080KiB fonctionnalités: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-cache:0 description: L1 cache identifiant matériel: 3d emplacement: L1 Cache taille: 64KiB capacité: 64KiB fonctionnalités: synchronous internal write-back data configuration: level=1 *-cache:1 description: L1 cache identifiant matériel: 3e emplacement: L1 Cache taille: 64KiB capacité: 64KiB fonctionnalités: synchronous internal write-back instruction configuration: level=1 *-cache:2 description: L2 cache identifiant matériel: 3f emplacement: L2 Cache taille: 512KiB capacité: 512KiB fonctionnalités: synchronous internal write-back unified configuration: level=2 *-cache:3 description: L3 cache identifiant matériel: 40 emplacement: L3 Cache taille: 4MiB capacité: 4MiB fonctionnalités: synchronous internal write-back unified configuration: level=3 *-cpu description: CPU produit: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz fabriquant: Intel Corp. identifiant matériel: 41 information bus: cpu@0 version: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz numéro de série: To Be Filled By O.E.M. emplacement: U3E1 taille: 730MHz capacité: 4005MHz bits: 64 bits horloge: 100MHz fonctionnalités: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti retpoline intel_pt rsb_ctxsw spec_ctrl tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq configuration: cores=2 enabledcores=2 threads=4 *-memory description: Mémoire Système identifiant matériel: 42 emplacement: Carte mère taille: 16GiB *-bank:0 description: SODIMM DDR3 Synchrone 1600 MHz (0,6 ns) produit: CT204864BF160B.M16 fabriquant: Conexant (Rockwell) identifiant matériel: 0 numéro de série: 22102813 emplacement: ChannelA-DIMM0 taille: 16GiB bits: 64 bits horloge: 1600MHz (0.6ns) *-bank:1 description: Project-Id-Version: @(#) $Id$Report-Msgid-Bugs-To: PO-Revision-Date: 2016-09-03 00:48+Last-Translator: Lyonel Vincent Language-Team: MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2017-10-12 17:02+X-Generator: Launchpad (build 18474)Project-Id-Version: @(#) $Id$Report-Msgid-Bugs-To: PO-Revision-Date: 2016-09-03 00:48+Last-Translator: Lyonel Vincent Language-Team: MIME-Version: 1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2017-10-12 17:02+X-Generator: Launchpad (build 18474) [vide] identifiant matériel: 1 emplacement: ChannelB-DIMM0 *-pci descripti
[Kernel-packages] [Bug 1768497] [NEW] Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370
Public bug reported: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - XPS 9370 Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 + Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 -- 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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: New Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>> wrote:
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
Hi Rafael,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following two commits resolved
this bug:
0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space
restoration")
0847684cfc5f("PCI / PM: Simplify device wakeup settings code")
This is a regression introduced in v4.13-rc1 and still exists in
mainline. The bug causes the battery to drain when the system is
powered down and unplugged, which does not happed prior to these two
commits.
>>> What system and what do you mean by "powered down"? How much time
>>> does it take for the battery to drain now?
>> By powered down, the bug reporter is saying physically powered off and
>> unplugged. The system is a HP laptop:
>>
>> dmi.chassis.vendor: HP
>> dmi.product.family: 103C_5335KV HP Notebook
>> dmi.product.name: HP Notebook
>> vendor_id: GenuineIntel
>> cpu family: 6
>>
>>
The bisect actually pointed to commit de3ef1e, but reverting
these two commits fixes the issue.
I was hoping to get your feedback, since you are the patch author. Do
you think gathering any additional data will help diagnose this issue,
or would it be best to submit a revert request?
>>> First, reverting these is not an option or you will break systems
>>> relying on them now. 4.13 is three releases back at this point.
>>>
>>> Second, your issue appears to be related to the suspend/shutdown path
>>> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
>>> change in pci_enable_wake() causes the problem to happen. Can you try
>>> to revert this one alone and see if that helps?
>> A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
>> tested. However, the test kernel still exhibited the bug.
> So essentially the bisection result cannot be trusted.
We performed some more testing and confirmed just a revert of the
following commit resolves the bug:
0847684cfc5f0 ("PCI / PM: Simplify device wakeup settings code")
>>> Thanks for confirming this!
>>>
Can you think of any suggestions to help debug further?
>>> The root cause of the regression is likely the change in
>>> pci_enable_wake() removing the device_may_wakeup() check from it.
>>>
>>> Probably, one of the drivers in the platform calls pci_enable_wake()
>>> directly from its ->shutdown() callback and that causes the device to
>>> be set up for system wakeup which in turn causes the power draw while
>>> the system is off to increase.
>>>
>>> I would look at the PCI drivers used on that platform to find which of
>>> them call pci_enable_wake() directly from ->shutdown() and I would
>>> make these calls conditional on device_may_wakeup().
>> I took a quick look with
>>
>> git grep -E "pci_enable_wake\(.*[^0]\);|device_may_wakeup"
>>
>> and didn't notice any pci_enable_wake() callers that called
>> device_may_wakeup() first.
> I've just look at a bunch of network drivers doing that.
>
> It looks like I may need to restore __pci_enable_wake() with an extra
> "runtime" argument for internal use.
>
> Joseph, can you ask the reporter to test the Bjorn's patch, please?
Yes, I'll get him a test kernel and respond with the results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745646
Title:
Battery drains when laptop is off (shutdown)
Status in Linux:
Unknown
Status in acpi package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in acpi source package in Artful:
New
Status in linux source package in Artful:
In Progress
Status in acpi source package in Bionic:
Confirmed
Status in linux source package in Bionic:
In Progress
Bug description:
I am using hp AY008tx laptop , and many other laptop users (HP) are also
facing the same issue . The problem don't occur when i install windows 10 .
Now, only ubuntu is installed.
i am using latest bios insyde20 rev 5.(latest)
WOL disabled and no usb device connected
checked my battery .
it don't happen when i remove battery and plug it again after shutdown.
tried laptop_mode_tools and tpl too
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: li
[Kernel-packages] [Bug 1768496] Re: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
** Also affects: qa-regression-testing 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1768496/+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 1768497] 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 1768497 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: artful -- 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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768496] Re: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
** Description changed: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True + + Also, this CONFIG is available in 4.13 kernel: + $ grep ARM64_SW_TTBR0_PAN /boot/config-4.13.0-39-generic + CONFIG_ARM64_SW_TTBR0_PAN=y + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True Also, this CONFIG is available in 4.13 kernel: $ grep ARM64_SW_TTBR0_PAN /boot/config-4.13.0-39-generic CONFIG_ARM64_SW_TTBR0_PAN=y ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1768496/+sub
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New 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 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+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 1768497] Re: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370
apport information ** Tags added: apport-collected bionic ** Description changed: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: santiago 1756 F pulseaudio + /dev/snd/controlC1: santiago 1756 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-02-22 (69 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) + MachineType: Dell Inc. XPS 13 9370 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/21/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.1 + dmi.board.name: 0F6P3V + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9370 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132019/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.
[Kernel-packages] [Bug 1768497] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132020/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132027/+files/ProcEnviron.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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132024/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132022/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132025/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132028/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132031/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132030/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132023/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132026/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132033/+files/WifiSyslog.txt ** 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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132021/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132029/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768497] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1768497/+attachment/5132032/+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/1768497 Title: Upgrade from 17.10 to 18.04 lost native 3D hardware acceleration for intel UHD 620, laptop is XPS 9370 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10 Some outputs which might be useful: __ sudo lspci -nnk | grep -i vga -A3 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Dell UHD Graphics 620 [1028:07e6] Kernel driver in use: i915 Kernel modules: i915 glxinfo | grep llv Device: llvmpipe (LLVM 6.0, 256 bits) (0x) OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes befpre desktop environment shows up (it was working in 17.10). Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: santiago 1756 F pulseaudio /dev/snd/controlC1: santiago 1756 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-22 (69 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2446979d-5a7e-47f0-8993-0072227049ff ro resume=/dev/nvme0n1p4 resume_offset=28704768 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768497/+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 1768526] [NEW] Include nfp driver in linux-modules
Public bug reported: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: + SRU Justification: + -- + [Impact] - * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. -An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra -packages are available, the nfp.ko module cannot be installed. In particular this means the driver for -any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through -cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. + * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. + An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra + packages are available, the nfp.ko module cannot be installed. In particular this means the driver for + any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through + cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. -In contrast the driver for the i40e is provided in the linux-modules package and thus guests can -access their VFs in the scenario described above. + In contrast the driver for the i40e is provided in the linux-modules package and thus guests can + access their VFs in the scenario described above. -Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather -than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between -users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. + Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather + than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between + users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. -This is a packaging update request and included no request to change the kernel source code, -thus no backports are requred. + This is a packaging update request and included no request to change the kernel source code, + thus no backports are requred. [Test Case] - * Install system using Canonical cloud images + * Install system using Canonical cloud images - * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; - - * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, -that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. + * Observer that + /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is + missing; + + * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, + that the nfp driver is not loaded and no netdevs are present for the Ne
[Kernel-packages] [Bug 1768526] 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 1768526 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 -- 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/1768526 Title: Include nfp driver in linux-modules Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+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 1763429] Re: Lenovo Yoga 720 does not shutdown with wifi enabled
Unfortunately the new Ubuntu kernel did not fix the issue, it only worked fine during some reboots. I now tried mainline v4.16.6 and v4.17-rc3, both did not fix the issue neither. -- 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/1763429 Title: Lenovo Yoga 720 does not shutdown with wifi enabled Status in linux package in Ubuntu: Incomplete Bug description: Whenever I try to shutdown or reboot the system while the internal wifi card is enabled, the systems hangs (system does not switch to command line mode, only possible to reboot using Syrq-Key+B, even Sysrq+O does not work). When I disable the wifi card using network manager before shutting down it works fine. The system runs in UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1448 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 12 17:36:34 2018 InstallationDate: Installed on 2018-04-09 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=3ba7e23d-37e2-4bef-b60a-c7509a7b487c ro reboot=cold RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN22WW(V1.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN22WW(V1.07):bd06/22/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763429/+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
Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs
This kernel did make it so I could not reproduce it on demand using ethtool -G however it broke so many other things I could not leave it running to see if it fixed spontaneous hangs. Strangely it broke nfs-kernel-server on the i7-6850k machine but not the i7-6700k machine. I did much stare and compare to make sure they were configured the same. This forced me to back out this kernel. But in addition to NFS, the nouveau drivers needed on the i7-6850k machine had some bug that would pixelize much of the screen in a semi-random fashion. Also for whatever reason x2goserver would not work properly with that kernel. On the i7-6700k machines, one I had to restart lightdm several times to get it to actually start, it did not start on boot up. On another I was unable to get lightdm to start at all and only console graphics worked, and for some reason they were in yellow instead of white. The i7-6700k machines are using the internal graphics of the i7-6700k processor clocked real slow to minimize the impact on heat budget. So on the kernel-developers's PPA I saw another test kernel, 4.15.0-21, I installed it, it also made ethtool -G not induce Ethernet hang but on the i7-6850 it's already hung once spontaneously: [ 4112.809034] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH <4f> TDT <6f> next_to_use <6f> next_to_clean<4e> buffer_info[next_to_clean]: time_stamp <1003a2221> next_to_watch<4f> jiffies <1003a2d80> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <7c00> PHY Extended Status<3000> PCI Status <10> [ 4114.793198] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH <4f> TDT <6f> next_to_use <6f> next_to_clean<4e> buffer_info[next_to_clean]: time_stamp <1003a2221> next_to_watch<4f> jiffies <1003a3540> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <7c00> PHY Extended Status<3000> PCI Status <10> [ 4116.008748] [ cut here ] [ 4116.008750] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out [ 4116.008765] WARNING: CPU: 8 PID: 59 at /build/linux-QLn4bB/linux-4.15.0/net/s ched/sch_generic.c:323 dev_watchdog+0x21d/0x230 [ 4116.008765] Modules linked in: tcp_diag inet_diag vhost_net vhost tap xt_CHEC KSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv 4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT n f_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptab le_filter devlink rpcsec_gss_krb5 nfsv4 nfs fscache msr bridge stp llc binfmt_mi sc nls_iso8859_1 quota_v2 quota_tree intel_rapl x86_pkg_temp_thermal intel_power clamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hda_codec_hdmi aes_x86_64 input_leds crypto_simd glue_helper cryptd snd_hda_codec_realtek snd_hda_codec_generic snd_seq_midi snd_seq_midi_e vent snd_hda_intel snd_hda_codec snd_hda_core snd_rawmidi snd_hwdep snd_seq snd_ pcm snd_seq_device [ 4116.008792] snd_timer intel_cstate eeepc_wmi snd asus_wmi sparse_keymap wmi_ bmof lpc_ich intel_rapl_perf intel_wmi_thunderbolt shpchp soundcore mei_me mei m ac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp l ibiscsi scsi_transport_iscsi nct6775 hwmon_vid coretemp parport_pc ppdev nfsd au th_rpcgss nfs_acl lockd grace sunrpc lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor async_t x xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash d m_log hid_generic usbhid hid raid10 nouveau video i2c_algo_bit ttm drm_kms_helpe r mxm_wmi syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops ahci drm ptp liba hci pps_core wmi [ 4116.008825] CPU: 8 PID: 59 Comm: ksoftirqd/8 Not tainted 4.15.0-21-lowlatency #22-Ubuntu [ 4116.008825] Hardware name: ASUS All Series/X99-E, BIOS 1801 08/11/2017 [ 4116.008827] RIP: 0010:dev_watchdog+0x21d/0x230 [ 4116.008827] RSP: 0018:a9b8c64cbd60 EFLAGS: 00010282 [ 4116.008828] RAX: RBX: RCX: 0006 [ 4116.008829] RDX: 0007 RSI: 0096 RDI: 8e863f416490 [ 4116.008829] RBP: a9b8c64cbd
[Kernel-packages] [Bug 1767452] Re: kernel oops when I undocked
Same. -- 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/1767452 Title: kernel oops when I undocked Status in linux-signed package in Ubuntu: Confirmed Bug description: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth 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 overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd e1000e glue_helper cryptd syscopyarea psmouse sysfillrect sysimgblt nvme ptp fb_sys_fops pps_core thunderbolt nvme_core drm
[Kernel-packages] [Bug 1725859] Re: zfs frequently hangs (up to 30 secs) during sequential read
I've tried to simulate this with very slow media and can't yet reproduce this issue. Can you play the DVD image and also run the following command in another terminal: iostat 1 300 > iostat.log this will capture 5 minutes of activity. please then attach the log to the bug report. -- 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/1725859 Title: zfs frequently hangs (up to 30 secs) during sequential read Status in zfs-linux package in Ubuntu: Incomplete Bug description: Updated to artful (17.10) yesterday. Trying to read (play video) from mirrored ZFS disks from an external USB 3 enclosure. Zpool is defined as: root@hetty:/home/crlb# zpool status pool: storage state: ONLINE scan: resilvered 20K in 0h0m with 0 errors on Fri Oct 20 18:38:49 2017 config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 errors: No known data errors root@hetty:/home/crlb# Found that I could re-create the problem with: rsync -av --progress Also found that: dd if=/dev/sdX of=/dev/null status=progress bs=1024 count=1000 Where "X" is either "b" or "c" does not hang. Installed: root@hetty:/home/crlb# apt list --installed | grep -i zfs libzfs2linux/artful,now 0.6.5.11-1ubuntu3 amd64 [installed,automatic] zfs-zed/artful,now 0.6.5.11-1ubuntu3 amd64 [installed,automatic] zfsutils-linux/artful,now 0.6.5.11-1ubuntu3 amd64 [installed] root@hetty:/home/crlb# Help please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1725859/+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 1763429] Bug is in upstream
tag kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763429 Title: Lenovo Yoga 720 does not shutdown with wifi enabled Status in linux package in Ubuntu: Incomplete Bug description: Whenever I try to shutdown or reboot the system while the internal wifi card is enabled, the systems hangs (system does not switch to command line mode, only possible to reboot using Syrq-Key+B, even Sysrq+O does not work). When I disable the wifi card using network manager before shutting down it works fine. The system runs in UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1448 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 12 17:36:34 2018 InstallationDate: Installed on 2018-04-09 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=3ba7e23d-37e2-4bef-b60a-c7509a7b487c ro reboot=cold RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN22WW(V1.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN22WW(V1.07):bd06/22/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763429/+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 1763823] Re: Update firmware for 18.04 hwe kernel
Checked contents of binary packages and verified that all expected new firmware files are present. ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1763823 Title: Update firmware for 18.04 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: A 4.15-based hwe-edge kernel has been introduced into xenial. However some of the firmware files it requires are missing from xenial's linux-firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in xenial. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1763823/+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 1763429] Bug is in upstream
tag kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763429 Title: Lenovo Yoga 720 does not shutdown with wifi enabled Status in linux package in Ubuntu: Incomplete Bug description: Whenever I try to shutdown or reboot the system while the internal wifi card is enabled, the systems hangs (system does not switch to command line mode, only possible to reboot using Syrq-Key+B, even Sysrq+O does not work). When I disable the wifi card using network manager before shutting down it works fine. The system runs in UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1448 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 12 17:36:34 2018 InstallationDate: Installed on 2018-04-09 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=3ba7e23d-37e2-4bef-b60a-c7509a7b487c ro reboot=cold RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN22WW(V1.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN22WW(V1.07):bd06/22/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763429/+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 1761751] Re: Black screen on 18.04 + AMD RX460
Is it HDMI from the board to HDMI on the monitor? I'd like to rule out any use of an adapter or HDMI-to-DVI cable. What monitor is this? Is the monitor detected? What do you see in the 'status', 'enabled', 'dpms', and 'modes' files in /sys/class/drm/card0-HDMI-A-1/ ? -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
kaihengfeng, I will download and test with your kernel today. --Galvin -- 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1e/0x20 May 01 10:05:04 galvin-T570 kernel: bus_add_driver+
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
I tested with linux-image- unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb and was unable to duplicate the issue. As a result, per jsalisbury's request, I will tag this issue 'kernel-fixed-upstream'. --Galvin ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_devic
[Kernel-packages] [Bug 1768474] Re: Xenial update to 4.4.130 stable release
** Description changed:
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.130 upstream
stable 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.130 stable release shall be
applied:
-
+* Linux 4.4.130
+* s390/uprobes: implement arch_uretprobe_is_alive()
+* s390/cio: update chpid descriptor after resource accessibility event
+* cdrom: information leak in cdrom_ioctl_media_changed()
+* scsi: mptsas: Disable WRITE SAME
+* ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
+* net: af_packet: fix race in PACKET_{R|T}X_RING
+* tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
+* net: fix deadlock while clearing neighbor proxy table
+* tipc: add policy for TIPC_NLA_NET_ADDR
+* llc: fix NULL pointer deref for SOCK_ZAPPED
+* llc: hold llc_sap before release_sock()
+* sctp: do not check port in sctp_inet6_cmp_addr
+* vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
+* pppoe: check sockaddr length in pppoe_connect()
+* packet: fix bitfield update race
+* team: fix netconsole setup over team
+* team: avoid adding twice the same option to the event list
+* 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
+* bonding: do not set slave_dev npinfo before slave_enable_netpoll in
bond_enslave
+* s390: correct module section names for expoline code revert
+* s390: correct nospec auto detection init order
+* s390: add sysfs attributes for spectre
+* s390: report spectre mitigation via syslog
+* s390: add automatic detection of the spectre defense
+* s390: move nobp parameter functions to nospec-branch.c
+* s390/entry.S: fix spurious zeroing of r0
+* s390: do not bypass BPENTER for interrupt system calls
+* s390: Replace IS_ENABLED(EXPOLINE_*) with IS_ENABLED(CONFIG_EXPOLINE_*)
+* s390: introduce execute-trampolines for branches
+* s390: run user space and KVM guests with modified branch prediction
+* s390: add options to change branch prediction behaviour for the kernel
+* s390/alternative: use a copy of the facility bit mask
+* s390: add optimized array_index_mask_nospec
+* s390: scrub registers on kernel entry and KVM exit
+* KVM: s390: wire up bpb feature
+* s390: enable CPU alternatives unconditionally
+* s390: introduce CPU alternatives
+* Revert "ath10k: send (re)assoc peer command when NSS changed"
+* jbd2: fix use after free in kjournald2()
+* ath9k_hw: check if the chip failed to wake up
+* Input: drv260x - fix initializing overdrive voltage
+* r8152: add Linksys USB3GIGV1 id
+* staging: ion : Donnot wakeup kswapd in ion system alloc
+* perf: Return proper values for user stack errors
+* x86/tsc: Prevent 32bit truncation in calc_hpet_ref()
+* cifs: do not allow creating sockets except with SMB1 posix exensions
--
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/1768474
Title:
Xenial update to 4.4.130 stable release
Status in linux package in Ubuntu:
Invalid
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.130 upstream
stable 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.130 stable release shall be
applied:
* Linux 4.4.130
* s390/uprobes: implement arch_uretprobe_is_alive()
* s390/cio: update chpid descriptor after resource accessibility event
* cdrom: information leak in cdrom_ioctl_media_changed()
* scsi: mptsas: Disable WRITE SAME
* ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
* net: af_packet: fix race in PACKET_{R|T}X_RING
* tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
* net: fix deadlock while clearing neighbor proxy table
* tipc: add policy for TIPC_NLA_NET_ADDR
* ll
[Kernel-packages] [Bug 1768292] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132147/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1e/
[Kernel-packages] [Bug 1768292] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132148/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: dr
[Kernel-packages] [Bug 1768292] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132149/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_att
[Kernel-packages] [Bug 1768292] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132160/+files/WifiSyslog.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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
apport information ** Tags added: apport-collected ** Description changed: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1e/0x20 May 01 10:05:04 galvin-T570 kernel: bus_add_driver+0x1c7/0x270 May 01 10:05:04 galvin-T570 kernel: ? 0xc028c000 May 01 10:05:04 galvin-T570 kernel: driver_register+0x60/0xe0 May 01 10:05:04 galvin-T570 kernel: ? 0xc028c000 May 01 10:05:04 galvin-T570 kernel: __pci_register_driver+0x5a/0x60 May 01 10:05:04 galvin-T570 kernel: nhi_init+0x2d/0x1000 [thunderbolt] May 01 10:05:0
[Kernel-packages] [Bug 1768292] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132150/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1
[Kernel-packages] [Bug 1768292] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132154/+files/ProcEnviron.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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driv
[Kernel-packages] [Bug 1768292] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132152/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driv
[Kernel-packages] [Bug 1768292] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132153/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570
[Kernel-packages] [Bug 1768292] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132158/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0
[Kernel-packages] [Bug 1768292] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132157/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_a
[Kernel-packages] [Bug 1768292] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132156/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driv
[Kernel-packages] [Bug 1768292] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132159/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0
[Kernel-packages] [Bug 1768292] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132151/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1
[Kernel-packages] [Bug 1768292] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1768292/+attachment/5132155/+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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel:
[Kernel-packages] [Bug 1768526] Re: Include nfp driver in linux-modules
The code impact is likely adding the line: drivers/net/ethernet/netronome/* to https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/control.d/generic .inclusion-list -- 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/1768526 Title: Include nfp driver in linux-modules Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+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 1767452] Re: kernel oops when I undocked
Good news! the 4.17.0-rc3 kernel *fixed this issue*! You can get it here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3/ I only tried undocking once so far but hey, I was able to undock and redock and there was no oops in dmesg. I will likely try again later throughout the day for various meetings. Will update here if I have any problems. -- 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/1767452 Title: kernel oops when I undocked Status in linux-signed package in Ubuntu: Confirmed Bug description: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth 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 overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid acpi_pad sch_fq_codel par
[Kernel-packages] [Bug 1766300] Re: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1766300 Title: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-azure source package in Trusty: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Artful: New Status in linux-azure source package in Artful: New Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: New Bug description: On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv- fcopy-daemon fails to start. This means that boot is degraded by default: $ systemctl list-units --failed --no-legend hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon $ systemctl is-system-running degraded which makes detecting other failures much harder to automate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-cloud-tools-common 4.15.0-15.16 ProcVersionSignature: User Name 4.15.0-1004.4-azure 4.15.15 Uname: Linux 4.15.0-1004-azure x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A Date: Mon Apr 23 16:27:47 2018 Dependencies: IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1004-azure root=UUID=fda9466a-9068-447f-8572-6d8d310eabd3 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-1004-azure N/A linux-backports-modules-4.15.0-1004-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 44FD5ABF-DE16-AD4A-B2E0-6E70167950AF dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766300/+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 1768583] [NEW] Touchpad is not detected in 'Asus GM501GS'
Public bug reported: I bought a new laptop Asus GM501GS, and the touch-pad is not working. I tried adding i8042.reset, i8042.nohup, etc. And nothing worked. Besides, when installed Ubuntu, the touch-pad also stopped working in BIOS and Windows. When I delete Ubuntu partition and fresh install Windows again. Touch- pad starts working properly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 19:48:44 2018 InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1768583/+attachment/5132231/+files/dmesg -- 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/1768583 Title: Touchpad is not detected in 'Asus GM501GS' Status in linux-signed package in Ubuntu: New Bug description: I bought a new laptop Asus GM501GS, and the touch-pad is not working. I tried adding i8042.reset, i8042.nohup, etc. And nothing worked. Besides, when installed Ubuntu, the touch-pad also stopped working in BIOS and Windows. When I delete Ubuntu partition and fresh install Windows again. Touch- pad starts working properly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 19:48:44 2018 InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768583/+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 1762468] Re: Cryptoswap not working in Bionic
-update- https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1310058 that is. -- 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/1762468 Title: Cryptoswap not working in Bionic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have cryptoswap set up both with the 2 GB default swap file and an 8 GB swap partition with 8 GB of ram. However, the system does not use this swap when it should. For example, if I run a little test code which attempts to allocate 10 GB of memory in 1 GB chuncks, the system hangs with no obvious use of swap. E.g. running top shows no swap use before the hang. However, if I replace cryptoswap by standard swap, it works as expected: allocates the requested memory and exits, using swap. Of course, my disk is slow, so this takes some time but it does work. I originally noticed this problem when compiling a very large application. The system would hang on ld. I've checked hardware using memtest and stress. No problems. This took me days to track down but I'm 99% certain now that the problem is with cryptoswap. If I compile with cryptoswap: hang. If I compile with standard swap: no problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: weinberg 2425 F pulseaudio /dev/snd/controlC0: weinberg 2425 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 11:57:23 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+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 1759791] Re: NFS + sec=krb5 is broken
Bug in hwe-edge kernel 4.15.0.15.40 posted also here https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1768545 please fix there too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759791 Title: NFS + sec=krb5 is broken Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am testing the development branch of Bionic Beaver. With the latest update to kernel 4.15.0-13 my nfs-mounts in a university network are broken. > sudo mount -vvv -t nfs4 my_server:/my/share /nfs -osoft,sec=krb5 > mount.nfs4: timeout set for Mon Mar 26 16:29:56 2018 > mount.nfs4: trying text-based options 'soft,sec=krb5,nfsvers=4.0,addr=10.162.229.2,clientaddr=10.152.249.189' > mount.nfs4: mount(2): Input/output error > mount.nfs4: mount system call failed > kernel: NFS: nfs4_discover_server_trunking unhandled error -5. Exiting with error EIO > kernel: RPC: couldn't encode RPC header, exit EIO > kernel: gss_marshal: gss_get_mic FAILED (851968) Known good version: linux-image-4.15.0-10 I think it is the same bug like in https://bugzilla.redhat.com/show_bug.cgi?id=1558977 The bug was introduced in the mainline kernel 4.15.4 with commit "[46e8d06e423c4f35eac7a8b677b713b3ec9b0684] crypto: hash - prevent using keyed hashes without setting key" This bug should be fixed before releasing ubuntu18.04 by either reverting the commit or using a fixed mainline kernel. --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1340 F pulseaudio /dev/snd/controlC0: gdm1340 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-22 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046a:b091 Cherry GmbH Bus 001 Device 002: ID 0bf8:101e Fujitsu Siemens Computers Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU ESPRIMO D757 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=463c4c1b-7771-40dd-833f-f4d68a5fd914 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UnreportableReason: Der Bericht gehört zu einem nicht installierten Paket. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 10/12/2017 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.14.0 for D3531-A1x dmi.board.name: D3531-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3531-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.14.0forD3531-A1x:bd10/12/2017:svnFUJITSU:pnESPRIMOD757:pvr:rvnFUJITSU:rnD3531-A1:rvrS26361-D3531-A1:cvnFUJITSU:ct3:cvr: dmi.product.family: ESPRIMO-FTS dmi.product.name: ESPRIMO D757 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759791/+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 1762468] Re: Cryptoswap not working in Bionic
At the risk of saying something completely unrelated; any change this is a regression of #1310058 where the UUID got overwritten? It came back a few times around 2015, leading me to believe that the devs don't actually use this method, and might not test for this scenario, making a regression possible. -- 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/1762468 Title: Cryptoswap not working in Bionic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have cryptoswap set up both with the 2 GB default swap file and an 8 GB swap partition with 8 GB of ram. However, the system does not use this swap when it should. For example, if I run a little test code which attempts to allocate 10 GB of memory in 1 GB chuncks, the system hangs with no obvious use of swap. E.g. running top shows no swap use before the hang. However, if I replace cryptoswap by standard swap, it works as expected: allocates the requested memory and exits, using swap. Of course, my disk is slow, so this takes some time but it does work. I originally noticed this problem when compiling a very large application. The system would hang on ld. I've checked hardware using memtest and stress. No problems. This took me days to track down but I'm 99% certain now that the problem is with cryptoswap. If I compile with cryptoswap: hang. If I compile with standard swap: no problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: weinberg 2425 F pulseaudio /dev/snd/controlC0: weinberg 2425 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 11:57:23 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+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 1768545] [NEW] NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
You have been subscribed to a public bug: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New -- NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel https://bugs.launchpad.net/bugs/1768545 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 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- 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/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+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
Re: [Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I'm not sure if you asked for the contents of these files from a working or non-working kernel, but I'll take the working kernel since that's obviously a lot easier. The monitor, Dell U2415, is connected via its input source "HDMI (MHL) 2". The monitor name "DELL U2415" shows up in the edid file. status: connected enabled: enabled dpms: On modes: 1920x1200 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1600x1200 1280x1024 1280x1024 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 // David On 2018-05-02 16:11, Harry Wentland wrote: > Is it HDMI from the board to HDMI on the monitor? I'd like to rule out > any use of an adapter or HDMI-to-DVI cable. > > What monitor is this? > > Is the monitor detected? > > What do you see in the 'status', 'enabled', 'dpms', and 'modes' files in > /sys/class/drm/card0-HDMI-A-1/ ? > -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1768545] 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 1768545 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 -- 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/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+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 1745646] Re: Battery drains when laptop is off (shutdown)
Hi Gopal, I built a test kernel with the patch requested by upstream. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1745646 Can you test this kernel and see if it resolves this bug? 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Status in acpi source package in Bionic: Confirmed Status in linux source package in Bionic: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
It looks like the commit needed to fix this is f3aefb6a7066e24bfea7fcf1b07907576de69d63, which is in the bionic's linux kernel 4.15.0-20.21 (as commit 17dd0448ee23bbd898c2a9463eb0d0890b29ca02). The corresponding linux-hwe and linux-hwe-edge kernels are in xenial-proposed, going through the kernel Stable Release Updates process. Confirming that the kernel in proposed indeed fixes the issue would be appreciated. Thanks! -- 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/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+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 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
ok i will check linux-hwe-edge kernels in xenial-proposed, stay tuned -- 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/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+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 1768496] Re: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
Thanks, the test was FAILing on artful/arm64 precisely because it was expecting not to find CONFIG_ARM64_SW_TTBR0_PAN set in the 4.13 kernel config, and it was. I have fixed up the qrt script in https://git.launchpad.net/qa-regression-testing/commit/?id=631ed1d195a7a9499caf3e4b5807ba2e423810e0 . Thanks! ** Changed in: qa-regression-testing Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True Also, this CONFIG is available in 4.13 kernel: $ grep ARM64_SW_TTBR0_PAN /boot/config-4.13.0-39-generic CONFIG_ARM64_SW_TTBR0_PAN=y ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1768496/+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 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1767133 Title: linux-image-4.15.0-20-generic install after upgrade from xenial breaks Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Some upgrades from xenial to bionic break. [Test Case] Change sources.list from xenial to bionic, then apt install linux-image-4.15.0-20-generic. [Regression Potential] The kernel may be uninstallable if there is no linux-base with the appropriate version in the archive. When installing the linux-image-4.15.0-20-generic kernel from bionic on xenial breaks because of the unversioned Depends on linux-base. /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.15.0-20-generic (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-image-4.15.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) If the trigger is called, when some meta packages are installed, it won't happen. If all packages are upgraded, it's possible linux-base is going to be upgraded first, so the problem won't happen either. So, not all upgrades will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767133/+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 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: 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 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Wednesday, 02. May 2018 17:06 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: 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 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Wednesday, 02. May 2018 17:06 UTC - kernel-stable-phase:Promoted to proposed + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: Confirmed 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: New 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 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- 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/1767397/+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 1766629] Re: linux-image packages need to Breaks flash-kernel << 3.90ubuntu2
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1766629 Title: linux-image packages need to Breaks flash-kernel << 3.90ubuntu2 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Due to the fact that we are no longer guaranteed to produce an initrd from our postinst, flash-kernel can fail on upgrade when it attempts to operate (incorrectly, because it's not smart) on the wrong kernel, and fails to find the initrd we've not yet made. This is worked around in flash-kernel 3.90ubuntu2, but all linux-image packages need to Breaks on << that version to ensure upgrade ordering. This should only apply to kernels which build on arm64 or armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766629/+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 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Committed Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://hel
[Kernel-packages] [Bug 1767930] Re: ASUS T300F Touchpad only works sometimes and no pertinent setting under Mouse & Touchpad
Firstly, thank you so much for the reply and I have read several articles for how to do that test the latest kernel thing you have told me since I am really new basically to so many things in this computer world. So, I followed the method from the internet to download 4 files from that mainline kernel page you posted. And run that 'sudo dpkg -i *.deb' command but I got some severe error that it even impacted the system update that a No-Entry-road traffic sign appears next to wifi icon in the top menu bar saying "An error occured... The error message was:'Error: BrokenCount > 0'" Here's what happened when I did what I said above in the terminal: # Start of the output benjamin@benjamin-T300FA:~/Desktop/Kernel-v4.17$ sudo dpkg -i *.deb [sudo] password for benjamin: (Reading database ... 282458 files and directories currently installed.) Preparing to unpack linux-headers-4.17.0-041700rc3_4.17.0-041700rc3.201804300800_all.deb ... Unpacking linux-headers-4.17.0-041700rc3 (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Preparing to unpack linux-headers-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-headers-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Preparing to unpack linux-image-unsigned-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-image-unsigned-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postrm ... removing pending trigger Preparing to unpack linux-modules-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-modules-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Setting up linux-headers-4.17.0-041700rc3 (4.17.0-041700rc3.201804300800) ... dpkg: dependency problems prevent configuration of linux-headers-4.17.0-041700rc3-generic: linux-headers-4.17.0-041700rc3-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.17.0-041700rc3-generic (--install): dependency problems - leaving unconfigured Setting up linux-modules-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) ... Setting up linux-image-unsigned-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) ... /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postinst: 50: /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-unsigned-4.17.0-041700rc3-generic (--install): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-headers-4.17.0-041700rc3-generic linux-image-unsigned-4.17.0-041700rc3-generic # end of the output But thanks to the internet again, I found a way to fix the error happened above by running command "sudo apt-get -f install" Then I later learn that what that "fc" at the end of the kernel code 4.17 means, so I went to download the last final version kernel 4.16.6 to give it a shot. But the result was just as same as above. Here's what happened: # Start of the terminal output benjamin@benjamin-T300FA:~/Desktop/Kernel-v4.16.6$ sudo dpkg -i *.deb [sudo] password for benjamin: Selecting previously unselected package linux-headers-4.16.6-041606. (Reading database ... 271321 files and directories currently installed.) Preparing to unpack linux-headers-4.16.6-041606_4.16.6-041606.201804300418_all.deb ... Unpacking linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-headers-4.16.6-041606-generic. Preparing to unpack linux-headers-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-headers-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-image-unsigned-4.16.6-041606-generic. Preparing to unpack linux-image-unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-image-unsigned-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-modules-4.16.6-041606-generic. Preparing to unpack linux-modules-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Setting up linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... dpkg: dependency problems prevent configuration of linux-headers-4.16.6-041606-generic: linux-headers-4.16.6-041606-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.16.6-041606-generic (--install): dependency problems - leaving unconfigured Setting up linux-modules-4.16.6-041606-generic (4.16
[Kernel-packages] [Bug 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
4.15.0-20-generic from proposed fixes the issue please push this version forward -- 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/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+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 1761751] Re: Black screen on 18.04 + AMD RX460
Thanks, mind posting the same for the non-working kernel? I'm curious if the problem is 1) we don't detect the display 2) we don't enable the display 3) we enable the display but wrong -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1762844] boslcp3g3 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g3 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132340/+files/boslcp3g3.dumpxml -- 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/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
