[Kernel-packages] [Bug 1806817] Re: PKCS#7 signature not signed with a trusted key
Sounds like bug 1798863. Please run this command to send us more system info: apport-collect 1806817 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-prime (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1806817 Title: PKCS#7 signature not signed with a trusted key Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Incomplete Bug description: It's hard to report this bug on a laptop with this driver installed, so I'm reporting this with on my laptop with a much newer NVIDIA driver (but not recommended). My laptop, Lenovo Z40, has NVIDIA GeForce GT820M. With nvidia-340 driver installed it won't boot to SDDM (also tried with LightDM). Opening up another TTY is useless because the same message "PKCS#7 signature not signed with a trusted key" keeps getting spammed. I had to go to recovery to switch to Intel graphics. [CODE] $ lspci 03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) [/CODE] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806817/+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 1788336] Re: Failed to install nfs-kernel-server package on KVM kernels
Re-open the task in ubuntu-kernel-test, as this is still affecting the kernel SRU. ** Changed in: ubuntu-kernel-tests Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788336 Title: Failed to install nfs-kernel-server package on KVM kernels Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: New Bug description: When trying to install the nfs-kernel-server package on a KVM node running with X/X-KVM kernel, it will fail with service dependency issue. This is affecting the ubuntu_vfat_stress and ubuntu_ramfs_stress test. $ sudo apt-get install nfs-kernel-server Reading package lists... Done Building dependency tree Reading state information... Done nfs-kernel-server is already the newest version (1:1.2.8-9ubuntu12.1). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up nfs-kernel-server (1:1.2.8-9ubuntu12.1) ... A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. nfs-server.service couldn't start. locale: Cannot set LC_ALL to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript nfs-kernel-server, action "start" failed. ● nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: inactive (dead) Aug 22 03:27:46 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:46 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:27:49 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:49 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:27:50 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:50 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:29:41 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:29:41 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:29:42 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:29:42 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. dpkg: error processing package nfs-kernel-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nfs-kernel-server E: Sub-process /usr/bin/dpkg returned an error code (1) Log from journalctl -xe: http://paste.ubuntu.com/p/CxrWqGc2YT/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1031-kvm 4.4.0-1031.37 ProcVersionSignature: User Name 4.4.0-1031.37-kvm 4.4.134 Uname: Linux 4.4.0-1031-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 22 03:28:11 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788336/+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 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM
ubuntu_nbd_smoke_test on kernel01 passed with this fix, thanks! ** Changed in: ubuntu-kernel-tests Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806013 Title: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This test can pass if you run it manually on s390x zVM. But it will fail when you try to run it with the smoke test suite on jenkins. And this issue was only spotted on this s390x zVM (kernel01) Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-21931 Date: Fri Nov 30 03:13:05 EST 2018 Host: kernel01 Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 636227 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 5.1G 1.2G 82% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 1.8G 18G 10% /home testpool.3622624G 0 24G 0% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 0 24G 0% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 0 24G 0% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 0 24G 0% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 0 24G 0% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd tcp6 0 0 ::: :::*LISTEN 21955/nbd-server mount on /dev/nbd0 failed disconnect, sock, done stderr: mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
[Kernel-packages] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged
** Tags added: originate-from-1805326 somerville -- 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/1806818 Title: Fix Intel I210 doesn't work when ethernet cable gets plugged Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Plugging ethernet cable cannot wake up Intel I210 when it's runtime suspended. It's because the PME is not enabled. [Fix] PCI core doesn't enable PME because the driver explicitly saves its PCI state before runtime suspend routine. Don't save PCI state fixes the issue. [Test] PME is correctly enabled, and cable plugging starts to work. [Regression Potential] Minimal. The fix limits to on device, and it's specific to runtime power management. Other functionalities are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806818/+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 1806428] Re: linux: 3.13.0-164.214 -proposed tracker
** 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 1806429 (linux-lts-trusty) derivatives: -- swm properties -- phase: Packaging phase-changed: Monday, 03. December 2018 15:04 UTC reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded -- 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/1806428 Title: linux: 3.13.0-164.214 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806429 (linux-lts-trusty) derivatives: -- swm properties -- phase: Packaging phase-changed: Monday, 03. December 2018 15:04 UTC reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806428/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Adding to the above #78, when I start the system, and before logging into ubuntu 18.04 LTS with my username and password. I opened up the console view (tty4). While shutdown down from there and reboot also works fine. I recieve no messages of cpu worker stuck as described above. I think its some other service which hangs the cpu workers(cpu resource deadlock) which starts after logging into the system for the first time. Since its a new laptop I have not installed apps or services to start with init.d and also I have put no triggers for /etc/rc* bluetooth/screen settings. After this I tried installing nvidia drivers for gtx 1050 ti from nvidia site run file I downloaded and it gave an error for nouveau kernel driver. So I turned it off by nvidia's installer helper for this and updated ramfs and did a reboot. No issues for me now, for shutdown/reboot or random system hang after successfully running nvidia graphics. ** Attachment added: "IMG_20181205_023037_HHT.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/5219288/+files/IMG_20181205_023037_HHT.jpg -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12
[Kernel-packages] [Bug 1774531] Re: [Dell Inspiron 7577] shutdown/reboot hangs
Adding to the above #4, when I start the system, and before logging into ubuntu 18.04 LTS with my username and password. I opened up the console view (tty4). While shutdown down from there and reboot also works fine. I recieve no messages of cpu worker stuck as described above. I think its some other service which hangs the cpu workers(cpu resource deadlock) which starts after logging into the system for the first time. Since its a new laptop I have not installed apps or services to start with init.d and also I have put no triggers for /etc/rc* bluetooth/screen settings. After this I tried installing nvidia drivers for gtx 1050 ti from nvidia site run file I downloaded and it gave an error for nouveau kernel driver. So I turned it off by nvidia's installer helper for this and updated ramfs and did a reboot. No issues for me now, for shutdown/reboot or random system hang after successfully running nvidia graphics. -- 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/1774531 Title: [Dell Inspiron 7577] shutdown/reboot hangs Status in linux package in Ubuntu: Expired Bug description: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 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/+bug/1774531/+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 1747850] Re: test_130_config_debug_rodata in ubuntu_qrt_kernel_security failed on Trusty ARM64
The original bug report was closed due to its quality and it's been tear-down into small pieces in multiple bug reports. Please don't close bug like this. This issue still exist if you looked into the Trusty ARM64 test report: http://10.246.72.4/test-results/3.13.0-163.213-generic/ms10-35-mcdivittB0-kernel__3.13.0-163.213__2018-11-17_00-06-00/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-security.py.DEBUG.html ** Changed in: qa-regression-testing Status: Invalid => Confirmed ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Changed in: ubuntu-kernel-tests Status: Invalid => 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/1747850 Title: test_130_config_debug_rodata in ubuntu_qrt_kernel_security failed on Trusty ARM64 Status in QA Regression Testing: Confirmed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This was reported in bug 163 I think it's better it tear it down into pieces. FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest) CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled -- Traceback (most recent call last): File "./test-kernel-security.py", line 642, in test_072_config_debug_rodata self.assertEqual(self._test_config(option), expected) AssertionError: False != True ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-141-generic 3.13.0-141.190 ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39 Uname: Linux 3.13.0-141-generic aarch64 NonfreeKernelModules: signpost 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.14.1-0ubuntu3.27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Feb 7 06:59:02 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-141-generic N/A linux-backports-modules-3.13.0-141-generic N/A linux-firmware 1.127.24 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/qa-regression-testing/+bug/1747850/+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 1806428] Re: linux: 3.13.0-164.214 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-164.214 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1806428 Title: linux: 3.13.0-164.214 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806429 (linux-lts-trusty) derivatives: -- swm properties -- phase: Packaging phase-changed: Monday, 03. December 2018 15:04 UTC reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806428/+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 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804588 Title: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF. Short idle: 6 Long idle: 2 S2I: 4.8 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the new Intel NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 2.8W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804588/+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 1806569] Re: linux: 4.4.0-141.167 -proposed tracker
** 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 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Tuesday, 04. December 2018 09:01 UTC reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded -- 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/1806569 Title: linux: 4.4.0-141.167 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Tuesday, 04. December 2018 09:01 UTC reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+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 1806818] 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 1806818 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/1806818 Title: Fix Intel I210 doesn't work when ethernet cable gets plugged Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Plugging ethernet cable cannot wake up Intel I210 when it's runtime suspended. It's because the PME is not enabled. [Fix] PCI core doesn't enable PME because the driver explicitly saves its PCI state before runtime suspend routine. Don't save PCI state fixes the issue. [Test] PME is correctly enabled, and cable plugging starts to work. [Regression Potential] Minimal. The fix limits to on device, and it's specific to runtime power management. Other functionalities are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806818/+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 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
** Changed in: ubuntu-kernel-tests Status: Invalid => Fix Released -- 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/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in ubuntu-kernel-tests: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: Fix Released Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: Fix Released Bug description: SRU Request: [Impact] After bionic/linux-azure commit 4fbb658dd8ce96384852ceae18b0b09034de7b36 (UBUNTU: [Config] azure: CONFIG_HOTPLUG_CPU=n) the lttng_tracer module cannot find some symbols and cannot be loaded. kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) This is caused by lttng-modules incorrectly handling the case when CONFIG_HOTPLUG_CPU is not enabled. [Test Case] Install linux-azure >= 4.15.0-1014, install lttng-modules-dkms and run the autotest ubuntu_lttng_smoke_test testcase (or just 'sudo lttng list --kernel'). [Fix] commit 894ce5dc825733d1ccab25b1aede9ce0be2a7c4e (Fix: do not use CONFIG_HOTPLUG_CPU for the new hotplug API) commit 1ee63d8d1b0aaf30564d3879d8e9282d0ddfef1b (Cleanup: comment about CONFIG_HOTPLUG_CPU ifdef) [Regression Potential] Very low. The two patches can be cleanly cherry-picked from the upstream commits. The first one that really fixed the issue just changes a single #ifdef to compile a piece of code when CONFIG_HOTPLUG_CPU is not defined. The second one just updates some comments on the code to make them consistent with the changes. [Original Description] This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module
[Kernel-packages] [Bug 1805085] Re: Fix and issue that LG I2C touchscreen stops working after reboot
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805085 Title: Fix and issue that LG I2C touchscreen stops working after reboot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Committed Bug description: [Impact] LG I2C touchscreen stops working after reboot. [Fix] Disable runtime PM for the touchscreen, which doesn't work well with consecutive ON/SLEEP commands. [Test] The touchscreen works well after reboot, when runtime PM is disabled. [Regression Potential] None. This is a new device and the fix is limited to this particular device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805085/+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 1802813] Re: Fix "incomplete report" noise after S3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1802813 Title: Fix "incomplete report" noise after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Bug description: [Impact] I2C HID devices may keep spewing out error "i2c_hid_get_input: incomplete report (30/2)" after system S3. [Fix] It a regression caused by commit ac75a041048b, backport commmit ef6eaf27274c to fix it. Input report length 2 is a valid length. [Test] With the fix the issue can no longer be observed on Alps touchpads. [Regression Potential] None. Input report lenght 2 is valid per spec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802813/+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 1805081] Re: Add pointstick support for Cirque Touchpad
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805081 Title: Add pointstick support for Cirque Touchpad Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Cirque Touchpad works but its pointstick doesn't work. [Test] With the fix the pointstick starts working. [Fix] Need to use MT_CLS_WIN_8_DUAL to let PTP driver use pointstick as a mouse. [Regression Potential] None. This is a new device and the fix is limited to this particular device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805081/+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 1747847] Re: Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR not functional on Trusty ARM64
The original bug report was closed due to its quality and it's been
tear-down into small pieces in multiple bug reports.
Please don't close bug like this.
** Changed in: qa-regression-testing
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: ubuntu-kernel-tests
Status: Invalid => 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/1747847
Title:
Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR
not functional on Trusty ARM64
Status in QA Regression Testing:
Confirmed
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
This was reported in bug 163
I think it's better it tear it down into pieces.
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1832, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1795, in _test_aslr
self._test_aslr_all(area, expected, "unlimited stack %s" % area)
File "./test-kernel-security.py", line 1772, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1765, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1134, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: unlimited stack libs native:
Got exit code 1, expected 0
Command: './aslr', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0x22f130
0x22f130
0x22f130
FAIL: ASLR not functional (libs always at 0x22f130)
==
FAIL: test_021_aslr_dapper_mmap (__main__.KernelSecurityTest)
ASLR of mmap
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1817, in test_021_aslr_dapper_mmap
self._test_aslr('mmap', expected)
File "./test-kernel-security.py", line 1795, in _test_aslr
self._test_aslr_all(area, expected, "unlimited stack %s" % area)
File "./test-kernel-security.py", line 1772, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1765, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1134, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: unlimited stack mmap native:
Got exit code 1, expected 0
Command: './aslr', 'mmap', '--verbose'
Output:
Checking ASLR of mmap:
0x200018e010
0x200018e010
0x200018e010
FAIL: ASLR not functional (mmap always at 0x200018e010)
==
FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
ASLR of vdso
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
self._test_aslr('vdso', expected)
File "./test-kernel-security.py", line 1795, in _test_aslr
self._test_aslr_all(area, expected, "unlimited stack %s" % area)
File "./test-kernel-security.py", line 1772, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1765, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1134, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: unlimited stack vdso native:
Got exit code 1, expected 0
Command: './aslr', 'vdso', '--verbose'
Output:
Checking ASLR of vdso:
0x21c000
0x21c000
0x21c000
FAIL: ASLR not functional (vdso always at 0x21c000)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-141-generic 3.13.0-141.190
ProcVersionSignature: User Name
[Kernel-packages] [Bug 1802248] Re: Disable LPM for Raydium Touchscreens
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802248 Title: Disable LPM for Raydium Touchscreens Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Committed Bug description: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802248/+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 1806818] [NEW] Fix Intel I210 doesn't work when ethernet cable gets plugged
Public bug reported: [Impact] Plugging ethernet cable cannot wake up Intel I210 when it's runtime suspended. It's because the PME is not enabled. [Fix] PCI core doesn't enable PME because the driver explicitly saves its PCI state before runtime suspend routine. Don't save PCI state fixes the issue. [Test] PME is correctly enabled, and cable plugging starts to work. [Regression Potential] Minimal. The fix limits to on device, and it's specific to runtime power management. Other functionalities are not affected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806818 Title: Fix Intel I210 doesn't work when ethernet cable gets plugged Status in linux package in Ubuntu: New Bug description: [Impact] Plugging ethernet cable cannot wake up Intel I210 when it's runtime suspended. It's because the PME is not enabled. [Fix] PCI core doesn't enable PME because the driver explicitly saves its PCI state before runtime suspend routine. Don't save PCI state fixes the issue. [Test] PME is correctly enabled, and cable plugging starts to work. [Regression Potential] Minimal. The fix limits to on device, and it's specific to runtime power management. Other functionalities are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806818/+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 1789581] Re: ubuntu_ecryptfs test hang on Cosmic
Ecryptfs is not supported since Bionic, test blacklisted with Cosmic. Change the status to won't fix. ** Changed in: linux (Ubuntu) Status: Expired => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789581 Title: ubuntu_ecryptfs test hang on Cosmic Status in linux package in Ubuntu: Won't Fix Bug description: The test will hang with: tests/run_one.sh -K -t lp-994247.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f ext2 With 100% reproducible rate. It looks like this is related to a package upgrade, not the kernel itself: The following NEW packages will be installed: fontconfig-config fonts-dejavu-core libcairo2 libfontconfig1 libipt1 libpixman-1-0 libxcb-render0 libxcb-shm0 libxrender1 python-cairo python3-cairo The following packages will be upgraded: bzip2 curl dpkg gdb gdbserver gir1.2-glib-2.0 grep init init-system-helpers iproute2 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32 libcurl3-gnutls libcurl4 libdb5.3 libgirepository-1.0-1 libglib2.0-data liblxc-common liblxc1 libnss-systemd libpam-systemd libssl1.1 libsystemd0 libudev1 libuv1 libx11-6 libx11-data libxml2 locales multiarch-support openssl python-apt-common python-gi python3-apt python3-debian python3-distupgrade python3-gi python3-twisted python3-twisted-bin systemd systemd-sysv ubuntu-release-upgrader-core udev unattended-upgrades The hang issue happens after a dist-upgrade with -proposed enabled, packages above is the upgrade candidate. Steps: 1. Deploy a node with Cosmic 2. Run the following commands: sudo apt-get install git python-minimal gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ecryptfs/control 3. Enable -proposed, run dist-upgrade and reboot 4. Repeat step 2. The first round will pass without any problem, but the test will hang with step 4. Which package is causing this issue is still unknown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: User Name 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 29 08:11 seq crw-rw 1 root audio 116, 33 Aug 29 08:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 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 Aug 29 08:37:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=a343a3f9-f1b0-426d-bfb0-3ecdb1aa2635 ro RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789581/+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 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793451 Title: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == Justification == When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with VM_LOCKED flag only. There is a hole in mlock_fixup() which increase mm->locked_vm twice even the two operations are on the same vma and both with VM_LOCKED flags. The issue can be reproduced by following code: mlock2(p, 1024 * 64, MLOCK_ONFAULT); //VM_LOCKED|VM_LOCKONFAULT mlock(p, 1024 * 64); //VM_LOCKED Then check the increase VmLck field in /proc/pid/status(to 128k). When vma is set with different vm_flags, and the new vm_flags is with VM_LOCKED, it is not necessarily be a "new locked" vma. There is a dedicated reproducer, the "mlock203" test in ubuntu_ltp_syscalls, you can see the failure for all the Ubuntu 4.4 kernel: <<>> tag=mlock203 stime=1537369891 cmdline="mlock203" contacts="" analysis=exit <<>> tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s mlock203.c:63: FAIL: Locking one memory again increased VmLck Summary: passed 0 failed 1 skipped 0 warnings 0 == Fix == b155b4fd (mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT)) A test kernel for Xenial / Xenial-KVM could be found here: http://people.canonical.com/~phlin/kernel/lp-1793451-mlock203/ == Regression Potential == Low, this patch prevents mm->locked_vm from increment just by adding an extra check to see if the old vm_flags is already VM_LOCKED. == Test Case == Run the mlock203 test in ubuntu_ltp_syscalls test suite. And it will pass with the patched kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78 ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144 Uname: Linux 4.4.0-1068-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 20 06:44:13 2018 Ec2AMI: ami-0e32ec5bc225539f5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1793451/+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 1806569] Re: linux: 4.4.0-141.167 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-141.167 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1806569 Title: linux: 4.4.0-141.167 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Tuesday, 04. December 2018 09:01 UTC reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+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 1798583] Re: the new Steam Controller driver breaks it on Steam
Please test this kernel: https://people.canonical.com/~khfeng/lp1806247/ -- 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/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+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 1798921] Re: sky2 ethernet card don't work after returning from suspension
So there are three different issue: Podesta's (original bug reporter): increase D3 delay can workaround the issue. Kris': non-maskable MSI issued IRQ before device resume, we probably need a DMI quirk table to let affected platforms use INTx. WoL: Does it ever work in previous kernel versions? Anyway please file a new bugs for separate issues. I'll upstream a fix for Podesta's issue as he's the original bug reporter. -- 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+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 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM
Retesting this on kernel01. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806013 Title: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: This test can pass if you run it manually on s390x zVM. But it will fail when you try to run it with the smoke test suite on jenkins. And this issue was only spotted on this s390x zVM (kernel01) Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-21931 Date: Fri Nov 30 03:13:05 EST 2018 Host: kernel01 Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 636227 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 5.1G 1.2G 82% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 1.8G 18G 10% /home testpool.3622624G 0 24G 0% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 0 24G 0% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 0 24G 0% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 0 24G 0% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 0 24G 0% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd tcp6 0 0 ::: :::*LISTEN 21955/nbd-server mount on /dev/nbd0 failed disconnect, sock, done stderr: mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error
[Kernel-packages] [Bug 1774531] Re: [Dell Inspiron 7577] shutdown/reboot hangs
I have faced this issue but maybe with different logs(pfa log statement). My laptop is dell 7757 i7 7700+nvidia 1050ti mobile 8gb ram 128gb ssd and 1tb sata, dual boot ubuntu 18.04.1LTS with 4.15 kernel + windows 10 home(although not using much). Sata raid on enabled in dell bios. Earlier tried with sata operation as ahcp. Both gave errors as same. Currently running video mode is xorg session. I was trying to install nvidia drivers(nvidia.run file from nvidia website) but everytime I do or such a computational task comes, this error comes up. Shutdown/reboot also hangs for eternity and have to hard shutdown. Random system hang or trackpad hang is also usual. Tried apci=off in grub, which fix the issues but my i7 runs single core only which is unacceptable. ** Attachment added: "IMG_20181205_023037_HHT.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774531/+attachment/5219265/+files/IMG_20181205_023037_HHT.jpg -- 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/1774531 Title: [Dell Inspiron 7577] shutdown/reboot hangs Status in linux package in Ubuntu: Expired Bug description: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 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/+bug/1774531/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
Would it be possible to do a kernel bisection between 4.4.0-138 and 4.4.0-139? -- 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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1796094] Re: Livepatch failed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1796094 Title: Livepatch failed Status in linux package in Ubuntu: Expired Bug description: apply-failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_33_36_generic_44 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 wrz 5 12:10 seq crw-rw+ 1 root audio 116, 33 wrz 5 12:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 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: Date: Thu Oct 4 15:37:06 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=95e22705-c020-4957-b87d-c3d208a53f15 InstallationDate: Installed on 2018-09-05 (29 days ago) InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=9f187778-61da-48dc-bece-1d20b3d8f11c ro RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-05 (29 days ago) dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSL-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSL-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796094/+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 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Expired Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 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 This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+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 1806270] Re: can not make use of software center package linux-image-3.13.0-117-generic (not installed) failed to install/upgrade: subprocess new pre-installation script ret
i will try and use those links . thank you for your help On 12/4/18, Juhani Numminen wrote: > Perhaps the info on these wiki pages might help: > https://help.ubuntu.com/community/PAE/PentiumM > https://help.ubuntu.com/community/PAE > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1806270 > > Title: >can not make use of software center package linux- > image-3.13.0-117-generic (not installed) failed to install/upgrade: > subprocess new pre-installation script returned error exit status 1 > > Status in linux-lts-trusty package in Ubuntu: > New > > Bug description: > i tryed to update to 14.04 but had message regarding the kernel wont > work without pae, and now i cant do anything to load software > > ProblemType: Package > DistroRelease: Ubuntu 12.04 > Package: linux-image-3.13.0-117-generic (not installed) > ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 > Uname: Linux 3.13.0-32-generic i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version > k3.13.0-32-generic. > ApportVersion: 2.0.1-0ubuntu17.15 > AptOrdering: >linux-image-3.13.0-117-generic: Install >linux-image-3.13.0-117-generic: Configure >linux-image-generic-lts-trusty: Configure >linux-generic-lts-trusty: Configure > Architecture: i386 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: bill 1580 F pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10' > Mixer name : 'Conexant Cx20468-31' > Components : 'AC97a:43585430' > Controls : 24 > Simple ctrls : 16 > CurrentDmesg: >[ 95.481086] lib80211_crypt: registered algorithm 'WEP' >[ 95.574164] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready >[ 366.225046] audit_printk_skb: 126 callbacks suppressed >[ 366.225054] type=1400 audit(1543776759.650:75): apparmor="DENIED" > operation="capable" profile="/usr/sbin/cupsd" pid=962 comm="cupsd" > capability=36 capname="block_suspend" > Date: Sun Dec 2 10:56:21 2018 > DpkgTerminalLog: >Unpacking linux-image-3.13.0-117-generic (from > .../linux-image-3.13.0-117-generic_3.13.0-117.164~precise1_i386.deb) ... >This kernel does not support a non-PAE CPU. >dpkg: error processing > /var/cache/apt/archives/linux-image-3.13.0-117-generic_3.13.0-117.164~precise1_i386.deb > (--unpack): > subprocess new pre-installation script returned error exit status 1 > DuplicateSignature: package:linux-image-3.13.0-117-generic:(not > installed):subprocess new pre-installation script returned error exit status > 1 > ErrorMessage: subprocess new pre-installation script returned error exit > status 1 > HibernationDevice: RESUME=UUID=daa06961-beb7-4f46-9fa3-f64cd7de4cd9 > InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 > (20140807.1) > Lsusb: >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: Acer TravelMate 4000 > MarkForUpload: True > PccardctlIdent: >Socket 0: > no product info available > PccardctlStatus: >Socket 0: > no card > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic > root=UUID=9b32c568-87cd-4496-bfe2-626072f60421 ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc 1.99-21ubuntu3.20 > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux-lts-trusty > Title: package linux-image-3.13.0-117-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 1 > UpgradeStatus: Upgraded to precise on 2018-11-24 (8 days ago) > WifiSyslog: > > dmi.bios.date: 08/06/2004 > dmi.bios.vendor: ACER > dmi.bios.version: 3A06 > dmi.board.name: TravelMate 4000 > dmi.board.vendor: Acer > dmi.board.version: Rev 1.0 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: Rev.1 > dmi.modalias: > dmi:bvnACER:bvr3A06:bd08/06/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1: > dmi.product.name: TravelMate 4000 > dmi.product.version: Rev 1 > dmi.sys.vendor: Acer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1806270/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty
[Kernel-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly
** 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+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 1805085] Re: Fix and issue that LG I2C touchscreen stops working after reboot
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/1805085 Title: Fix and issue that LG I2C touchscreen stops working after reboot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Committed Bug description: [Impact] LG I2C touchscreen stops working after reboot. [Fix] Disable runtime PM for the touchscreen, which doesn't work well with consecutive ON/SLEEP commands. [Test] The touchscreen works well after reboot, when runtime PM is disabled. [Regression Potential] None. This is a new device and the fix is limited to this particular device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805085/+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 1805081] Re: Add pointstick support for Cirque Touchpad
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/1805081 Title: Add pointstick support for Cirque Touchpad Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Cirque Touchpad works but its pointstick doesn't work. [Test] With the fix the pointstick starts working. [Fix] Need to use MT_CLS_WIN_8_DUAL to let PTP driver use pointstick as a mouse. [Regression Potential] None. This is a new device and the fix is limited to this particular device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805081/+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 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
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/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or more logical CPUs kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] And it leads to wifi can't scan any APs, and leads to system hangs while suspending. [Fix] Below commit contained in v4.17 fix the issue. ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+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 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1805607 Title: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Committed Bug description: [Impact] It drains power more than 0.5 Watt after power off(S5) the machine with QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it won't pass E-star 7. [Fix] Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it. [Test] Verified on Dell machines, it works. [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805607/+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 1804604] Re: SRU: Fix thinkpad 11e 3rd boot hang
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/1804604 Title: SRU: Fix thinkpad 11e 3rd boot hang Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: [Impact] ThinkPad 11e 3rd boot hang in systemd loading. [Fix] When boot case acpi_lpss_resume() get called without a corresponding acpi_lpss_suspend() having been called. Thus force setting the flag during boot. [Test Case] Tested on Thinkpad 11e 3rd. Booting successfully. [Regression Potential] Low, upstream fix cherry-picked. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804604/+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 1781533] Re: SATA device is not going to DEVSLP
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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1781533 Title: SATA device is not going to DEVSLP Status in HWE Next: Triaged Status in OEM Priority Project: Triaged Status in linux-oem package in Ubuntu: Fix Committed Bug description: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leads to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Fix] Suggested from Intel and Dell to contains the following 4 commits, and all of 4 commits are in v4.19-rc1 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ https://patchwork.kernel.org/patch/10535781/ https://patchwork.kernel.org/patch/10535783/ [Test] Verified the power consumption on some new platforms, it improves the SATA HDD power consumption around 0.5w during long idle. [Regression Potential] Low, the DEVSLP function is already validated when shipped with SLP_S0 support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1802813] Re: Fix "incomplete report" noise after S3
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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1802813 Title: Fix "incomplete report" noise after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Bug description: [Impact] I2C HID devices may keep spewing out error "i2c_hid_get_input: incomplete report (30/2)" after system S3. [Fix] It a regression caused by commit ac75a041048b, backport commmit ef6eaf27274c to fix it. Input report length 2 is a valid length. [Test] With the fix the issue can no longer be observed on Alps touchpads. [Regression Potential] None. Input report lenght 2 is valid per spec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802813/+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 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)
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/1804588 Title: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF. Short idle: 6 Long idle: 2 S2I: 4.8 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the new Intel NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 2.8W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804588/+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 1805344] Re: SRU: Fix kernel xhci hang when resume from S3
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/1805344 Title: SRU: Fix kernel xhci hang when resume from S3 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On some thinkpad laptops, Realtek USB3.0 Card Reader [0bda:0328] reports wrong port status on Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, then kernel hang. [Fix] Restrict the USB2 resume status check in USB2 roothub to fix hang issue. [Test Case] Suspend/resume 30 times OK. [Regression Potential] Low, upstream fix cherry-picked. These 2 patches are already Cc: sta...@vger.kernel.org, cosmic and future kernel will get these 2 patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805344/+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 1805079] Re: click/pop noise in the headphone on several lenovo laptops
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/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+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 1802248] Re: Disable LPM for Raydium Touchscreens
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/1802248 Title: Disable LPM for Raydium Touchscreens Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Committed Bug description: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802248/+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 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle
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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1805775 Title: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Committed Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Western Digital PC SN720 NVMe SSD SDAPNTW-256G. Short idle: 5.3 Long idle: 3.0 S2I: 5.07 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the WD NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 1.66W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805775/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
4.4.0-140 does not solve the problem for me either (had to revert back to 4.4.0-138). The first time I tried 4.4.0-140 the system locked up, but there was no kernel crash stacktrace and I was able to use the Magic SysRq key combination to avoid a hardware reboot. The second time I tried 4.4.0-140 the system locked up, but I was not able to use Magic SysRq to avoid a hardware reboot. Yet the kernel crash logging changed, producing about three different stacktraces over the span of about 30 seconds (before the logs froze). Unfortunately the crash logs did not persist to disk. -- 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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1806534] Re: Fix USB2 device wrongly detected as USB1
** Tags removed: apport-collected -- 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/1806534 Title: Fix USB2 device wrongly detected as USB1 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] USB 2 device may come up as USB 1 if a connection to a USB 1 device is followed by another connection to a USB 2 device, the link will come up as USB 1 for the USB 2 device. [Test Case] Insert 2 USB devices and they shall appear on lsusb with correct address [Fix] 11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 Soc [Regression Risk] It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and PCI_VENDOR_ID_BROADCOM:0x9026. Low regression to other device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806534/+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 1804149] Comment bridged from LTC Bugzilla
--- Comment From finne...@us.ibm.com 2018-12-04 21:05 EDT--- (In reply to comment #13) > In bug 1782085 it looks like the bug stopped happening after upgrading to > version 4.15.0-23. Do you know if that is still the case with that older > system, or has the bug come back after upgrading to a newer kernel version? System associated with older 1782085 has been up 47 days on kernel 4.15.0-36-generic with no Oops Kernel panic i.e. root@ilzlnx4:~# date;uptime;uname -a Tue Dec 4 18:59:53 MST 2018 18:59:53 up 47 days, 6:41, 6 users, load average: 8.21, 7.63, 7.02 Linux ilzlnx4 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux root@ilzlnx4:~# History of prior kernels on older 1782085 system root@ilzlnx4:~# ls -lrt /boot | grep -i initrd -rw-r--r-- 1 root root 12520274 May 11 2017 initrd.img-4.4.0-59-generic.bk -rw-r--r-- 1 root root 12533717 Jan 8 2018 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 12533595 Jan 8 2018 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 12531125 Jan 8 2018 initrd.img-4.4.0-77-generic -rw-r--r-- 1 root root 12525524 Jan 8 2018 initrd.img-4.4.0-59-generic -rw-r--r-- 1 root root 12533634 Jan 8 2018 initrd.img-4.4.0-96-generic -rw-r--r-- 1 root root 12537400 Jan 9 2018 initrd.img-4.4.0-104-generic -rw-r--r-- 1 root root 13971222 Mar 14 2018 initrd.img-4.15.0-10-generic.bk -rw-r--r-- 1 root root 13998457 Jul 17 11:39 initrd.img-4.15.0-10-generic -rw-r--r-- 1 root root 8770182 Jul 17 11:39 initrd.img-4.4.0-112-generic -rw-r--r-- 1 root root 14291350 Jul 17 11:39 initrd.img-4.15.0-15-generic -rw-r--r-- 1 root root 14360370 Oct 17 01:11 initrd.img-4.15.0-23-generic lrwxrwxrwx 1 root root 28 Oct 18 12:16 initrd.img.old -> initrd.img-4.15.0-23-generic lrwxrwxrwx 1 root root 28 Oct 18 12:16 initrd.img -> initrd.img-4.15.0-36-generic -rw-r--r-- 1 root root 14321575 Oct 18 12:16 initrd.img-4.15.0-36-generic root@ilzlnx4:~# -- 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/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi
[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
I experienced the problem 100% of the time on 4.4.0-139. However, unlike Jan, I just tried 4.4.0-140 and the problem is gone. I will continue monitoring my system to see if it reappears. -- 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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1756315] Re: fstrim and discard operations take too long to complete - Ubuntu 16.04
I ran into this issue on 14.04 and 16.04 as well. Ubuntu 18.04 does not seem to be affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1756315 Title: fstrim and discard operations take too long to complete - Ubuntu 16.04 Status in linux-aws package in Ubuntu: Confirmed Bug description: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 D root 1693 1682 2 80 0 - 3182 blkdev 07:54 pts/100:00:03 mkfs.xfs /dev/md0 root@ip-172-31-24-66:~# cat /proc/1693/wchan blkdev_issue_discard Process stuck with function --> blkdev_issue_discard To manage notifications about this bug go to:
[Kernel-packages] [Bug 1756315] Re: fstrim and discard operations take too long to complete - Ubuntu 16.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1756315 Title: fstrim and discard operations take too long to complete - Ubuntu 16.04 Status in linux-aws package in Ubuntu: Confirmed Bug description: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 D root 1693 1682 2 80 0 - 3182 blkdev 07:54 pts/100:00:03 mkfs.xfs /dev/md0 root@ip-172-31-24-66:~# cat /proc/1693/wchan blkdev_issue_discard Process stuck with function --> blkdev_issue_discard To manage notifications about this bug go to:
[Kernel-packages] [Bug 1806766] Re: [Regression] crashkernel fails on HiSilicon D05
** Description changed: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ - sudo tee /etc/default/grub.d/kdump-tools.cfg + sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger + On failure: + [2.362261] [ cut here ] + [2.362263] [CRTC:29:crtc-0] vblank wait timed out + [2.362294] WARNING: CPU: 0 PID: 143 at drivers/gpu/drm/drm_atomic_helper.c:1386 drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper] + [2.362295] Modules linked in: hibmc_drm(+) ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm hisi_sas_v2_hw(+) hisi_sas_main ehci_platform libsas scsi_transport_sas + [2.362309] CPU: 0 PID: 143 Comm: systemd-udevd Tainted: G C 4.19.0-7-generic #8-Ubuntu + [2.362310] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50 06/01/2018 + [2.362312] pstate: 6045 (nZCv daif +PAN -UAO) + [2.362324] pc : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper] + [2.362335] lr : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper] + [2.362336] sp : 0a2fb1f0 + [2.362337] x29: 0a2fb1f0 x28: 0001 + [2.362339] x27: x26: 0001 + [2.362342] x25: 0038 x24: 8000208c5800 + [2.362344] x23: x22: 0001 + [2.362346] x21: 80001eebb818 x20: 800025b18600 + [2.362349] x19: x18: 0001 + [2.362351] x17: x16: + [2.362353] x15: x14: 09848708 + [2.362355] x13: 0074 x12: 09a12000 + [2.362357] x11: 0986d000 x10: 09a122f8 + [2.362359] x9 : 0001 x8 : 09a15104 + [2.362361] x7 : x6 : 004ce5700bb7 + [2.362363] x5 : 00ff x4 : + [2.362365] x3 : x2 : + [2.362367] x1 : 0b15ae454042e100 x0 : + [2.362370] Call trace: + [2.362381] drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper] + [2.362392] drm_atomic_helper_commit_tail+0x68/0x80 [drm_kms_helper] + [2.362402] commit_tail+0x7c/0x80 [drm_kms_helper] + [2.362413] drm_atomic_helper_commit+0xd8/0x150 [drm_kms_helper] + [2.362440] drm_atomic_commit+0x54/0x60 [drm] + [2.362451] restore_fbdev_mode_atomic+0x184/0x1f8 [drm_kms_helper] + [2.362461] restore_fbdev_mode+0x48/0x190 [drm_kms_helper] + [2.362472] drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 [drm_kms_helper] + [2.362482] drm_fb_helper_set_par+0x34/0x60 [drm_kms_helper] + [2.362488] fbcon_init+0x3ac/0x4f0 + [2.362491] visual_init+0xb8/0x110 + [2.362492] do_bind_con_driver+0x1ec/0x3a8 + [2.362494] do_take_over_console+0x148/0x208 + [2.362495] do_fbcon_takeover+0x70/0xd8 + [2.362497] fbcon_event_notify+0x838/0x8a8 + [2.362501] notifier_call_chain+0x5c/0x98 + [2.362502] blocking_notifier_call_chain+0x64/0x88 + [2.362504] fb_notifier_call_chain+0x30/0x40 + [2.362506] register_framebuffer+0x22c/0x328 + [2.362516] __drm_fb_helper_initial_config_and_unlock+0x210/0x408 [drm_kms_helper] + [2.362526] drm_fb_helper_initial_config+0x4c/0x58 [drm_kms_helper] + [2.362530] hibmc_fbdev_init+0x88/0x190 [hibmc_drm] + [2.362534] hibmc_pci_probe+0x228/0x3c8 [hibmc_drm] + [2.362537] local_pci_probe+0x44/0xa8 + [2.362539] pci_device_probe+0x194/0x1a8 + [2.362541] really_probe+0x21c/0x3b8 + [2.362543] driver_probe_device+0xe4/0x138 + [2.362544] __driver_attach+0xe4/0x150 + [2.362545] bus_for_each_dev+0x84/0xd8 + [2.362547] driver_attach+0x30/0x40 + [2.362548] bus_add_driver+0x1a8/0x288 + [2.362550] driver_register+0x64/0x110 + [2.362551] __pci_register_driver+0x58/0x68 + [2.362555] hibmc_init+0x30/0x1000 [hibmc_drm] + [2.362557] do_one_initcall+0x54/0x1d8 + [2.362560] do_init_module+0x60/0x1f0 + [2.362561] load_module+0x15d0/0x18b8 + [2.362563] __se_sys_finit_module+0xa0/0xf8 + [2.362565] __arm64_sys_finit_module+0x24/0x30 + [2.362567] el0_svc_common+0x94/0xe8 + [2.362568] el0_svc_handler+0x38/0x78 + [2.362570] el0_svc+0x8/0xc + [2.362571] ---[ end trace 8031150f72d9 ]--- + [Fix] 2 upstream patch series are required to fix this: - https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html + https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: -
[Kernel-packages] [Bug 1802812] Re: Ubuntu 18.04 (4.15.0-38-generic) 'suspend' seizing up and requiring a forced shutdown
*** This bug is a duplicate of bug 1801743 *** https://bugs.launchpad.net/bugs/1801743 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1802812 Title: Ubuntu 18.04 (4.15.0-38-generic) 'suspend' seizing up and requiring a forced shutdown Status in linux package in Ubuntu: Confirmed Bug description: Today after a fresh install of the latest 18.04 LTS on my dell precision m4800; my laptop fails when i try to suspend. Either i choose to suspend via fn+f1, or closing the lid, or using the comman line; first i have a black screen and then the system seizes up. (not on sleep state) esc, power button, ctrl+alt+f1,f2 etc. nothing works. I have to force power off by holding the power button. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: suleyman 1201 F pulseaudio /dev/snd/controlC0: suleyman 1201 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 05:09:25 2018 HibernationDevice: RESUME=UUID=d4445414-6a4b-43fe-8d99-ec6cf57b951a InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision M4800 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=bd1aa1f5-5a41-4d1c-a57b-83ef5e861879 ro acpi_osi=Linux mem_sleep_default=deep RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd02/01/2018:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: suleyman 1201 F pulseaudio /dev/snd/controlC0: suleyman 1201 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=d4445414-6a4b-43fe-8d99-ec6cf57b951a InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision M4800 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=bd1aa1f5-5a41-4d1c-a57b-83ef5e861879 ro acpi_osi=Linux mem_sleep_default=deep ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd02/01/2018:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802812/+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 1806247] Re: hid-steam in linux 4.18 causes trouble with steam games
Thanks for pointing out #1798583. I concur that this tracking is the same issue and reviewing my search results, I didn't discover the existing issue report due to the '_' in 'hid_steam' vs 'hid-steam', sorry for the duplicate. -- 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/1806247 Title: hid-steam in linux 4.18 causes trouble with steam games Status in linux package in Ubuntu: Confirmed Bug description: Good day, Reported on Valve's issue tracker [1] and upstream [2]. There is a functional regression with the introduction of the hid-steam kernel module and using the Steam Controller with some Steam games. In the bug reports there is a proposed fix which has been accepted upstream [3] and backported to 4.19 [4]. Unfortunately, 4.18 was EOL'd before this patch could land, and is expected to affect both Ubuntu 18.10's kernel and the upcoming 18.04.2 hwe kernel. Please consider applying this patch [3] to your 4.18 builds. Best regards, kisak [1] https://github.com/ValveSoftware/steam-for-linux/issues/5645 [2] https://bugzilla.kernel.org/show_bug.cgi?id=201571 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=385a4886778f6d6e61eff1d4d295af332d7130e1 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=fb87a92b43961c89bf4a115d8a700885d8959cb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247/+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 1806766] 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 1806766 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 ** Changed in: linux (Ubuntu Cosmic) 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/1806766 Title: [Regression] crashkernel fails on HiSilicon D05 Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 2 upstream patch series are required to fix this: https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: https://lkml.org/lkml/2018/9/21/1066 There were also some follow-on fixes to deal with ARM-specific problems associated with this usage: https://www.spinics.net/lists/arm-kernel/msg685751.html [Regression Risk] The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806766/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I have faced this issue but maybe with different logs(pfa log statement). My laptop is dell 7757 i7 7700+nvidia 1050ti mobile 8gb ram 128gb ssd and 1tb sata, dual boot ubuntu 18.04.1LTS with 4.15 kernel + windows 10 home(although not using much). Sata raid on enabled in dell bios. Earlier tried with sata operation as ahcp. Both gave errors as same. Currently running video mode is xorg session. I was trying to install nvidia drivers(nvidia.run file from nvidia website) but everytime I do or such a computational task comes, this error comes up. Shutdown/reboot also hangs for eternity and have to hard shutdown. Random system hang or trackpad hang is also usual. Tried apci=off in grub, which fix the issues but my i7 runs single core only which is unacceptable. ** Attachment added: "IMG_20181205_023037_HHT.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/5219129/+files/IMG_20181205_023037_HHT.jpg -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] []
[Kernel-packages] [Bug 1806766] [NEW] [Regression] crashkernel fails on HiSilicon D05
Public bug reported: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 2 upstream patch series are required to fix this: https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: https://lkml.org/lkml/2018/9/21/1066 There were also some follow-on fixes to deal with ARM-specific problems associated with this usage: https://www.spinics.net/lists/arm-kernel/msg685751.html [Regression Risk] The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/1806766 Title: [Regression] crashkernel fails on HiSilicon D05 Status in linux package in Ubuntu: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 2 upstream patch series are required to fix this: https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: https://lkml.org/lkml/2018/9/21/1066 There were also some follow-on fixes to deal with ARM-specific problems associated with this usage: https://www.spinics.net/lists/arm-kernel/msg685751.html [Regression Risk] The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806766/+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 1788035] Re: nvme: avoid cqe corruption
I'm investigating this issue, and built a kernel with the following two
patches:
a)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7776db1ccc1
b) A debug patch present in
http://lists.infradead.org/pipermail/linux-nvme/2017-February/008498.html
The idea of the first patch, which was merged upstream in Linux 4.12, is to
poll the completion
queue of the device in the event of a timeout - if it succeeds, means that the
device didn't post a completion, so could be an adapter issue.
The idea of the 2nd patch is just to provide debug information in case of a
mismatch in the choice
of the blk-mq hw queue in nvme driver - it's a debug patch proposed in the
mailing list to address a similar bug report in the past.
The kernel with the debug patches is available in PPA - to install it,
one can follow the below instructions:
a) sudo add-apt-repository ppa:gpiccoli/test-nvme-182638
b) sudo apt-get update
c) sudo apt-get install linux-image-4.4.0-1073-aws
After installation is complete, please reboot the instance and after it's
restarted,
check "uname -rv" output, which should be:
"4.4.0-1073-aws #83+hf182638v20181129b1-Ubuntu SMP Fri Nov 30 17:09:30
UTC 2018"
Please notice this is a test kernel, shouldn't be used in any production
environment, nor is
officially supported in any form.
Anybody that can test this, much appreciated. Please post the complete dmesg
after/if the issue is triggered.
Thanks,
Guilherme
--
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/1788035
Title:
nvme: avoid cqe corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
To address customer-reported NVMe issue with instance types (notably
c5 and m5) that expose EBS volumes as NVMe devices, this commit from
mainline v4.6 should be backported to Xenial:
d783e0bd02e700e7a893ef4fa71c69438ac1c276 nvme: avoid cqe corruption
when update at the same time as read
dmesg sample:
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, aborting
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 9 QID 1 timeout, aborting
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 21 QID 2 timeout, aborting
[Wed Aug 15 01:11:32 2018] nvme :00:1f.0: I/O 10 QID 1 timeout, aborting
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, reset
controller
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 21 QID 2
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887751
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887751
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 2
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887767
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887767
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 2
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887769
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887769
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 8 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 9 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
41943136
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 10 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
6976
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 24 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 25 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 2 QID 0
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x7
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: fffc
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
96
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): metadata I/O error: block 0x5000687
("xlog_iodone") error 5 numblks 64
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_do_force_shutdown(0x2) called
from line 1197 of file
[Kernel-packages] [Bug 1806270] Re: can not make use of software center package linux-image-3.13.0-117-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returne
Perhaps the info on these wiki pages might help: https://help.ubuntu.com/community/PAE/PentiumM https://help.ubuntu.com/community/PAE -- 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/1806270 Title: can not make use of software center package linux- image-3.13.0-117-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux-lts-trusty package in Ubuntu: New Bug description: i tryed to update to 14.04 but had message regarding the kernel wont work without pae, and now i cant do anything to load software ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-117-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.15 AptOrdering: linux-image-3.13.0-117-generic: Install linux-image-3.13.0-117-generic: Configure linux-image-generic-lts-trusty: Configure linux-generic-lts-trusty: Configure Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1580 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10' Mixer name : 'Conexant Cx20468-31' Components : 'AC97a:43585430' Controls : 24 Simple ctrls : 16 CurrentDmesg: [ 95.481086] lib80211_crypt: registered algorithm 'WEP' [ 95.574164] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 366.225046] audit_printk_skb: 126 callbacks suppressed [ 366.225054] type=1400 audit(1543776759.650:75): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=962 comm="cupsd" capability=36 capname="block_suspend" Date: Sun Dec 2 10:56:21 2018 DpkgTerminalLog: Unpacking linux-image-3.13.0-117-generic (from .../linux-image-3.13.0-117-generic_3.13.0-117.164~precise1_i386.deb) ... This kernel does not support a non-PAE CPU. dpkg: error processing /var/cache/apt/archives/linux-image-3.13.0-117-generic_3.13.0-117.164~precise1_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 DuplicateSignature: package:linux-image-3.13.0-117-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=daa06961-beb7-4f46-9fa3-f64cd7de4cd9 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer TravelMate 4000 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b32c568-87cd-4496-bfe2-626072f60421 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 1.99-21ubuntu3.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-trusty Title: package linux-image-3.13.0-117-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2018-11-24 (8 days ago) WifiSyslog: dmi.bios.date: 08/06/2004 dmi.bios.vendor: ACER dmi.bios.version: 3A06 dmi.board.name: TravelMate 4000 dmi.board.vendor: Acer dmi.board.version: Rev 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnACER:bvr3A06:bd08/06/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1: dmi.product.name: TravelMate 4000 dmi.product.version: Rev 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1806270/+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 1806412] Re: EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: comm REINDEX: bad extra_isize 8306 (inode size 256)
I leave this here: https://bugzilla.kernel.org/show_bug.cgi?id=201685 -- Cristian Aravena Romero (caravena) ** Bug watch added: Linux Kernel Bug Tracker #201685 https://bugzilla.kernel.org/show_bug.cgi?id=201685 -- 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/1806412 Title: EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: comm REINDEX: bad extra_isize 8306 (inode size 256) Status in linux package in Ubuntu: Confirmed Bug description: Hello, [ 96.230966] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: comm REINDEX: bad extra_isize 8306 (inode size 256) [ 96.259863] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663570: comm REINDEX: bad extra_isize 3912 (inode size 256) [ 96.328165] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663571: comm REINDEX: bad extra_isize 2 (inode size 256) [ 96.372998] EXT4-fs error (device sda7): ext4_iget:4851: inode #8663572: comm REINDEX: checksum invalid [ 96.451608] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663573: comm REINDEX: bad extra_isize 3288 (inode size 256) [ 96.549207] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663574: comm REINDEX: bad extra_isize 38448 (inode size 256) [ 96.584675] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663575: comm REINDEX: bad extra_isize 67 (inode size 256) [ 96.628344] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663576: comm REINDEX: bad extra_isize 34544 (inode size 256) [ 96.754517] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663577: comm REINDEX: bad extra_isize 16592 (inode size 256) [ 96.916746] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663578: comm REINDEX: bad extra_isize 29555 (inode size 256) [ 101.261135] EXT4-fs error: 55 callbacks suppressed Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-7-generic 4.19.0-7.8 ProcVersionSignature: Ubuntu 4.19.0-7.8-generic 4.19.5 Uname: Linux 4.19.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2623 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 11:32:18 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-7-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-7-generic N/A linux-backports-modules-4.19.0-7-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806412/+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 1806755] Re: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
I am still running cosmic, since no secure and functional Kernel is out for disco at the moment. -- 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/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: Confirmed Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 187761] Re: Need a way to disable selected modules with a kernel flag
I have a usecase for disabling kernel modules: I need to disable uas when booting (or at least after booting) a livecd: All my usb3 to SATA adapters load uas.ko when plugged, then promptly malfunction. They work when plugged into a usb2 port. Deleting uas.ko breaks usb hotplug. I am assuming that usb storage will actually work without uas. -- 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/187761 Title: Need a way to disable selected modules with a kernel flag Status in linux package in Ubuntu: In Progress Bug description: Binary package hint: linux-image Bug #90271 and bug #187671 describe situations where Live CDs and install CDs fail to work because a broken kernel module causes a hang before user has a say. The error may be in an optional kernel module (such as sound card driver or memory card reader) but the end user has no way to prevent kernel from loading a possibly known broken module. Vanilla kernels from kernel.org support flag disablemodules (e.g. disablemodules=8139too,sdhci prevents linux kernel from loading 8139too.ko or sdhci.ko) but such flag does not seem to work with Ubuntu. This is a feature request to enable such a flag. It is not needed for normal use but in case of rare hardware exposing a bug in a kernel module not having such a flag prevents one from booting Ubuntu. (I'd prefer booting without network adapter or memory card reader to not booting at all). This issue also causes slowdowns such as bug #187671 which cannot proceed until bug #90271 is fixed because testing possible fixes for the bug is really hard until the other kernel module has been fixed. (This is because both bugs affect the same laptop hardware and both kernel modules cause a kernel hang.) I'd consider disablemodules flag similar to acpi flag - it should not be needed but still we need it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187761/+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 1806479] Re: Multiple failures in distrobution 18.10
Regarding the first error that you mention: Err:17 http://ppa.launchpad.net/webupd8team/indicator-kdeconnect/ubuntu cosmic Release 404 Not Found [IP: 91.189.95.83 80] That is because that particular PPA (personal package archive) is not available for Ubuntu 18.10. The webupd8 team only releases it for some older Ubuntu versions. So please disable that software source. The second message that you commented on is apparently due to Google Earth repository, and you can report it to Google. That looks safe to ignore anyway. Let's see if that "check connection" message goes away when you disable the webupd8team indicator-kdeconnect PPA. ** Changed in: linux (Ubuntu) Status: Confirmed => New ** Package changed: linux (Ubuntu) => 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/1806479 Title: Multiple failures in distrobution 18.10 Status in Ubuntu: New Bug description: When I try sudo apt-get update I get the following errors: Ign:16 https://dl.bintray.com/resin-io/debian stable InRelease Err:17 http://ppa.launchpad.net/webupd8team/indicator-kdeconnect/ubuntu cosmic Release 404 Not Found [IP: 91.189.95.83 80] and E: The repository 'http://ppa.launchpad.net/webupd8team/indicator-kdeconnect/ubuntu cosmic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386' My system is an AMD 64-bit processor. When I try to report the bug I get the following errors: E: The repository 'http://ppa.launchpad.net/webupd8team/indicator-kdeconnect/ubuntu cosmic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386' which shows that the .css file has a bug. When I try Software Updater it complains that my internet connect is faulty. The Ubuntu 18.10 drivers may be faulty, but the internet connection is good. And of course there are the bugs in Ubuntu 18.04 and upstream kernel and 18.10 when trying to use large external drives. Plus the previously reported and ignored memory leak in Caja. Plus the error with hyperspec: Downloading the hyperspec from the Internet --2018-12-03 15:28:10-- ftp://ftp.lispworks.com/pub/software_tools/reference/HyperSpec-7-0.tar.gz => ‘/root/tmp/HyperSpec-7-0.tar.gz’ Resolving ftp.lispworks.com (ftp.lispworks.com)... 92.243.11.64 Connecting to ftp.lispworks.com (ftp.lispworks.com)|92.243.11.64|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/software_tools/reference ... done. ==> SIZE HyperSpec-7-0.tar.gz ... 2032830 ==> PASV ... couldn't connect to 92.243.11.64 port 65193: No route to host Unable to download and can't ask whether to try again. dpkg: error processing package hyperspec (--configure): installed hyperspec package post-installation script subprocess returned error exit status 1 Note the invalid http port number (65193)! 18.10 is not yet ready for prime time. 18.04 was but apparently is no longer supported. Many of these bugs are trivial and are easily fixed. Others show design flaws in Ubuntu that need to be addressed and are much harder to fix. Plus hfsplus has stopped working for no known reason. I need it just long enough to get my data off the drive so I can reformat it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3060 F pulseaudio /dev/snd/controlC0: robert 3060 F pulseaudio CurrentDesktop: MATE Date: Mon Dec 3 15:12:47 2018 InstallationDate: Installed on 2018-11-30 (3 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions:
[Kernel-packages] [Bug 1806755] Re: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
** 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/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: Confirmed Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1806755] 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 1806755 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/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: Incomplete Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1787775] Re: touchpad not working on lenovo yoga 530
Is there anything i may try to get this working or is there any information that i can give to make diagnosis more easy? I already tried building the kernel from linux-source package matching my version and installing the dkms stuff but had no luck so far. Any guesses? -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1806755] [NEW] All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
Public bug reported: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: New Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1806751] 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/1806751
Title:
package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
installing 18.4 over 16.8
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-42-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3220 Analog [ALC3220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: george 1835 F pulseaudio
/dev/snd/controlC0: george 1835 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfb32 irq 45'
Mixer name : 'Realtek ALC3220'
Components : 'HDA:10ec0280,102805d2,0013'
Controls : 25
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 46'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10de094c,00100100'
Controls : 21
Simple ctrls : 3
Date: Tue Dec 4 12:39:55 2018
ErrorMessage: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=298e362b-64c7-442b-9eb9-dd4ac8caecf7
InstallationDate: Installed on 2017-06-17 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: Dell Inc. Precision T3610
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago)
dmi.bios.date: 02/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/28/2014:svnDellInc.:pnPrecisionT3610:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T3610
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806751/+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 1755490] Please test proposed package
Hello Dariusz, or anyone else affected, Accepted hwdata into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/hwdata/0.249-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Committed Status in hwdata source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Hello Dariusz, or anyone else affected, Accepted gnome-desktop3 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- desktop3/3.8.4-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-desktop3 (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-trusty ** Changed in: hwdata (Ubuntu Trusty) Status: In Progress => Fix Committed -- 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/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Committed Status in hwdata source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1806751] Re: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: installed linux-headers-4.15.0-42-generic package post-installation script subproces
that was 18.04 over 16.04
--
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/1806751
Title:
package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
installing 18.4 over 16.8
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-42-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3220 Analog [ALC3220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: george 1835 F pulseaudio
/dev/snd/controlC0: george 1835 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfb32 irq 45'
Mixer name : 'Realtek ALC3220'
Components : 'HDA:10ec0280,102805d2,0013'
Controls : 25
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 46'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10de094c,00100100'
Controls : 21
Simple ctrls : 3
Date: Tue Dec 4 12:39:55 2018
ErrorMessage: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=298e362b-64c7-442b-9eb9-dd4ac8caecf7
InstallationDate: Installed on 2017-06-17 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: Dell Inc. Precision T3610
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago)
dmi.bios.date: 02/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/28/2014:svnDellInc.:pnPrecisionT3610:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T3610
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806751/+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 1806751] [NEW] package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: installed linux-headers-4.15.0-42-generic package post-installation script subproc
Public bug reported:
installing 18.4 over 16.8
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-42-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3220 Analog [ALC3220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: george 1835 F pulseaudio
/dev/snd/controlC0: george 1835 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfb32 irq 45'
Mixer name : 'Realtek ALC3220'
Components : 'HDA:10ec0280,102805d2,0013'
Controls : 25
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 46'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10de094c,00100100'
Controls : 21
Simple ctrls : 3
Date: Tue Dec 4 12:39:55 2018
ErrorMessage: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=298e362b-64c7-442b-9eb9-dd4ac8caecf7
InstallationDate: Installed on 2017-06-17 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Precision T3610
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago)
dmi.bios.date: 02/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/28/2014:svnDellInc.:pnPrecisionT3610:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T3610
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-package 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/1806751
Title:
package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
installing 18.4 over 16.8
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-42-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3220 Analog [ALC3220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: george 1835 F pulseaudio
/dev/snd/controlC0: george 1835 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfb32 irq 45'
Mixer name : 'Realtek ALC3220'
Components : 'HDA:10ec0280,102805d2,0013'
Controls : 25
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 46'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10de094c,00100100'
Controls : 21
Simple ctrls : 3
Date: Tue Dec 4 12:39:55 2018
ErrorMessage: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=298e362b-64c7-442b-9eb9-dd4ac8caecf7
InstallationDate: Installed on 2017-06-17 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: Dell Inc. Precision T3610
ProcFB: 0 nouveaufb
[Kernel-packages] [Bug 1785912] Re: Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV
I have the same problem. Using Lenovo Ideapad 720s 4k screen, i7-8550U; Intel UHD Graphics 620 I have tried to install: - Ubuntu 18.04.1 - Ubuntu 18.10 - Elementary OS 5.0 - Fedora (latest version) Just need to install Windows then ... -- 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/1785912 Title: Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV Status in linux package in Ubuntu: Incomplete Bug description: Horrible screen flicker from login screen and after login. 18.04.1 LTS. I have two similar laptops, both Lenovo Ideapad 720s 13IKB, model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine. model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen flashing. Neither have the problem in Windows (ie hardware fine) I installed the standard Ubuntu 18.04 on each of them (same USB Key, few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the problem. Flickering visible on video here: https://photos.app.goo.gl/HCN73q1nQfgstgVBA I've used ubuntu-bug so I believe you have all the details of the machine. The install came straight from your standard 18.04 download. Any changes are due to me trying to fix this (not much prev exp of kernel params etc) Things tried but which didn't work were: - enable huc/guc (got it to load - it's now visible in the attached dmesg - but didn't help.) - enable_rc6=0 (just stopped sleep / resume working) - edp_vswing=2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Tue Aug 7 23:09:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39af] InstallationDate: Installed on 2018-08-06 (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 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:210d Acer, Inc Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 i915.enable_guc_loading=1 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6MCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81BV dmi.product.version: Lenovo ideapad 720S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912/+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 1770256] Re: linux packages should own /usr/lib/linux/triggers
** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1770256 Title: linux packages should own /usr/lib/linux/triggers Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: Rather than randomly mkdir/rmdir'ing /usr/lib/linux/triggers all of the binary packages that use triggers should contain this directory. This will allow dpkg to reference count the directory and detect left over files correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770256/+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 1805244] Re: linux-azure: 4.18.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.18.0-1006.6 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Stakeholder signoff not verified - promote-to-updates: Stakeholder signoff not verified - stakeholder-signoff: Waiting for signoff + promote-to-security: Ready to copy + promote-to-updates: Ready to copy -- 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/1805244 Title: linux-azure: 4.18.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1006.6 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805244/+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 1806021] Re: linux-azure: 4.15.0-1035.36 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1034.35 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: 1803592 phase: Promoted to proposed phase-changed: Saturday, 01. December 2018 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Stakeholder signoff not verified - promote-to-updates: Stakeholder signoff not verified + promote-to-security: Ready to copy + promote-to-updates: Ready to copy snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel - stakeholder-signoff: Waiting for signoff -- 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/1806021 Title: linux-azure: 4.15.0-1035.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35 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: 1803592 phase: Promoted to proposed phase-changed: Saturday, 01. December 2018 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806021/+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 1806380] Re: linux-buildinfo: pull out ABI information into its own package
** Changed in: linux (Ubuntu Bionic) Status: New => 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/1806380 Title: linux-buildinfo: pull out ABI information into its own package Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: We have an increasing amount of ABI information which is currently exposed via the primary binary packages. Little to none of this is relevant to the end-user and does not deserve to use up space on their system. Also the kernel developer who needs to update this data does not want to downloads 10s of Megabytes of binary packages to extract this information. Pull it all out and generate all data that would require the actual binaries at kernel build time, package all of this information into a new linux-buildinfo package for consumption. This package is not installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806380/+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 1806034] Re: linux-azure: 4.15.0-1035.36~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1035.36~16.04.1 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 22:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Stakeholder signoff not verified - promote-to-updates: Stakeholder signoff not verified + promote-to-security: Ready to copy + promote-to-updates: Ready to copy snap-release-to-beta: Snap not in beta channel snap-release-to-edge: Snap not in edge channel - stakeholder-signoff: Waiting for signoff -- 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/1806034 Title: linux-azure: 4.15.0-1035.36~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1035.36~16.04.1 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 22:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy snap-release-to-beta: Snap not in beta channel snap-release-to-edge: Snap not in edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806034/+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 1806395] Re: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
dmesg 4.18.20-041820-generic: [ 6314.257569] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.262609] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.272098] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.281645] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.291288] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.300927] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.310640] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.320165] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.329682] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 6314.339269] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [...] ** Attachment added: "dmesg_4.18.20-041820-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806395/+attachment/5219083/+files/dmesg_4.18.20-041820-generic.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/1806395 Title: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.337762] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:19:29 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806395/+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 1806063] Re: linux-azure: 4.15.0-1035.36~14.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1035.36~14.04.2 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Stakeholder signoff not verified - promote-to-updates: Stakeholder signoff not verified - stakeholder-signoff: Waiting for signoff + promote-to-security: Ready to copy + promote-to-updates: Ready to copy -- 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/1806063 Title: linux-azure: 4.15.0-1035.36~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1035.36~14.04.2 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806063/+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 1806380] Re: linux-buildinfo: pull out ABI information into its own package
** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => 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/1806380 Title: linux-buildinfo: pull out ABI information into its own package Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: We have an increasing amount of ABI information which is currently exposed via the primary binary packages. Little to none of this is relevant to the end-user and does not deserve to use up space on their system. Also the kernel developer who needs to update this data does not want to downloads 10s of Megabytes of binary packages to extract this information. Pull it all out and generate all data that would require the actual binaries at kernel build time, package all of this information into a new linux-buildinfo package for consumption. This package is not installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806380/+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 1805244] Re: linux-azure: 4.18.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- 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/1805244 Title: linux-azure: 4.18.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1006.6 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Stakeholder signoff not verified promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805244/+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 1806034] Re: linux-azure: 4.15.0-1035.36~16.04.1 -proposed tracker
Tests complete. Please publish. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- 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/1806034 Title: linux-azure: 4.15.0-1035.36~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1035.36~16.04.1 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 22:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Stakeholder signoff not verified promote-to-updates: Stakeholder signoff not verified snap-release-to-beta: Snap not in beta channel snap-release-to-edge: Snap not in edge channel stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806034/+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 1806021] Re: linux-azure: 4.15.0-1035.36 -proposed tracker
Tests complete. Please publish. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- 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/1806021 Title: linux-azure: 4.15.0-1035.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35 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: 1803592 phase: Promoted to proposed phase-changed: Saturday, 01. December 2018 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Stakeholder signoff not verified promote-to-updates: Stakeholder signoff not verified snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806021/+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 1806063] Re: linux-azure: 4.15.0-1035.36~14.04.2 -proposed tracker
Tests complete. Please publish. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- 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/1806063 Title: linux-azure: 4.15.0-1035.36~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1035.36~14.04.2 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: 1803592 phase: Promoted to proposed phase-changed: Friday, 30. November 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Stakeholder signoff not verified promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806063/+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 1806106] Re: Inconsistent/slow file transfer speed TO Ubuntu 18.04
Fixed after latest update and removal of old kernels. -- 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/1806106 Title: Inconsistent/slow file transfer speed TO Ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: When trying to transfer a file from Windows 10 to Ubuntu 18.04 over samba, transfer speed fluctuates up and down between 20MB/s and 110MB/s. When transfering from Ubuntu to Windows 10 speed is steady at 90MB/s (instead of 110MB due to a bug that I've already reported) Iperf3 shows consistent speeds without any fluctuation. I'm quite disappointed because there was no such problem a few weeks before. I'm guessing that this may have been an update that broke it. It's unlikely that I wouldn't have noticed it, because I was troubleshooting another issue related to transfer speeds. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-09 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A69 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 RfKill: Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: B250M MORTAR ARCTIC (MS-7A69) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A69 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806106/+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 1806397] Re: acer_wmi: Unsupported machine has AMW0_GUID1, unable to load
Anthony Wong (anthonywong), Hotkeys work 'all' right for the kernel "Ubuntu 4.18.0-11.12-generic 4.18.12". Best regards, -- Cristian Aravena Romero (caravena) -- 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/1806397 Title: acer_wmi: Unsupported machine has AMW0_GUID1, unable to load Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 17.265418] acer_wmi: Unsupported machine has AMW0_GUID1, unable to load Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:24:35 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806397/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
Hi, I have the same problem. I can perfectly use this key on a usb2 port. The usb3 port is working, i can use pendrive on this port. The outputs when the key is plugged on usb3 are: 1) dmesg [40261.131061] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd [40261.152025] usb 2-1: New USB device found, idVendor=0bda, idProduct=8153 [40261.152035] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [40261.152042] usb 2-1: Product: USB 10/100/1000 LAN [40261.152048] usb 2-1: Manufacturer: Realtek [40261.152053] usb 2-1: SerialNumber: 0100 [40261.283522] usb 2-1: reset SuperSpeed USB device number 6 using xhci_hcd [40261.345831] r8152 2-1:1.0 eth0: v1.09.9 [40261.407779] r8152 2-1:1.0 enx9cebe85eac03: renamed from eth0 [40261.433452] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready [40261.437807] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready [40261.471953] usb 2-1: USB disconnect, device number 6 [40261.472042] r8152 2-1:1.0 enx9cebe85eac03: Stop submitting intr, status -108 2) lspci 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 3) lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic 4) uname -a Linux xxx-inspiron 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 5) lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp. Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:58c2 Realtek Semiconductor Corp. Bus 001 Device 024: ID 045e:0797 Microsoft Corp. Optical Mouse 200 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- 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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not
[Kernel-packages] [Bug 1806247] Re: hid-steam in linux 4.18 causes trouble with steam games
** 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/1806247 Title: hid-steam in linux 4.18 causes trouble with steam games Status in linux package in Ubuntu: Confirmed Bug description: Good day, Reported on Valve's issue tracker [1] and upstream [2]. There is a functional regression with the introduction of the hid-steam kernel module and using the Steam Controller with some Steam games. In the bug reports there is a proposed fix which has been accepted upstream [3] and backported to 4.19 [4]. Unfortunately, 4.18 was EOL'd before this patch could land, and is expected to affect both Ubuntu 18.10's kernel and the upcoming 18.04.2 hwe kernel. Please consider applying this patch [3] to your 4.18 builds. Best regards, kisak [1] https://github.com/ValveSoftware/steam-for-linux/issues/5645 [2] https://bugzilla.kernel.org/show_bug.cgi?id=201571 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=385a4886778f6d6e61eff1d4d295af332d7130e1 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=fb87a92b43961c89bf4a115d8a700885d8959cb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247/+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 1798583] Re: the new Steam Controller driver breaks it on Steam
Kernel team are addressing this in bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247 This might be able to be marked as a dupe. -- 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/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+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 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM
Fix committed, commit http://kernel.ubuntu.com/git/ubuntu/autotest- client-tests.git/commit/?id=9aba531dcecbd1505ac9bac3736f2124af942d34 This makes the server export detection more robust, tested on xenial, bionic, cosmic and disco, amd64/i386/ppc64el. Hopefully this will address all weird mount failures. ** Changed in: ubuntu-kernel-tests 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/1806013 Title: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: This test can pass if you run it manually on s390x zVM. But it will fail when you try to run it with the smoke test suite on jenkins. And this issue was only spotted on this s390x zVM (kernel01) Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-21931 Date: Fri Nov 30 03:13:05 EST 2018 Host: kernel01 Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 636227 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 5.1G 1.2G 82% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 1.8G 18G 10% /home testpool.3622624G 0 24G 0% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 0 24G 0% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 0 24G 0% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 0 24G 0% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 0 24G 0% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 0 24G 0% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd tcp6 0 0 ::: :::*LISTEN 21955/nbd-server mount on /dev/nbd0 failed disconnect, sock, done stderr: mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mount: wrong fs type, bad option, bad superblock on
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
I have a similar workaround as Rekby, only as a pm-action hook. https://gitlab.com/snippets/1786967 -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1804738] Re: package libnvidia-ifr1-410 410.78-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz', which is d
This bug was fixed in the package nvidia-graphics-drivers-410 - 410.78-0ubuntu2 --- nvidia-graphics-drivers-410 (410.78-0ubuntu2) disco; urgency=medium * debian/rules: - Prevent pkgbinarymangler from symlinking docs (LP: #1804738). -- Alberto Milone Tue, 04 Dec 2018 15:48:16 +0100 ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1804738 Title: package libnvidia-ifr1-410 410.78-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libnvidia- ifr1-410/changelog.Debian.gz', which is different from other instances of package libnvidia-ifr1-410:i386 Status in nvidia-graphics-drivers-410 package in Ubuntu: Fix Released Bug description: get this error while upgrading the nvidia packages: libnvidia-gl-410 : Breaks: libnvidia-gl-410:i386 (!= 410.78-0ubuntu1) but 410.73-0ubuntu0~gpu18.10.1 is installed libnvidia-gl-410:i386 : Breaks: libnvidia-gl-410 (!= 410.73-0ubuntu0~gpu18.10.1) but 410.78-0ubuntu1 is installed libnvidia-ifr1-410 : Breaks: libnvidia-ifr1-410:i386 (!= 410.78-0ubuntu1) but 410.73-0ubuntu0~gpu18.10.1 is installed libnvidia-ifr1-410:i386 : Breaks: libnvidia-ifr1-410 (!= 410.73-0ubuntu0~gpu18.10.1) but 410.78-0ubuntu1 is installed apt --fix-broken install also results in error: dpkg: error processing archive /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz', which is different from other instances of package libnvidia-ifr1-410:i386 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-410_410.78-0ubuntu1_i386.deb /var/cache/apt/archives/libnvidia-ifr1-410_410.78-0ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I have ubuntu 19.04 installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libnvidia-ifr1-410 410.78-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Nov 23 07:47:44 2018 DuplicateSignature: package:libnvidia-ifr1-410:410.78-0ubuntu1 Unpacking libnvidia-gl-410:i386 (410.78-0ubuntu1) over (410.73-0ubuntu0~gpu18.10.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-bZAul7/10-libnvidia-gl-410_410.78-0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libnvidia-gl-410/changelog.Debian.gz', which is different from other instances of package libnvidia-gl-410:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz', which is different from other instances of package libnvidia-ifr1-410:i386 InstallationDate: Installed on 2018-04-29 (207 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.7, Python 3.7.1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.8.0~alpha2ubuntu1 SourcePackage: nvidia-graphics-drivers-410 Title: package libnvidia-ifr1-410 410.78-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libnvidia-ifr1-410/changelog.Debian.gz', which is different from other instances of package libnvidia-ifr1-410:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-410/+bug/1804738/+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 1806323] modified.conffile..etc.fwupd.daemon.conf.txt
apport information ** Attachment added: "modified.conffile..etc.fwupd.daemon.conf.txt" https://bugs.launchpad.net/bugs/1806323/+attachment/5219051/+files/modified.conffile..etc.fwupd.daemon.conf.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/1806323 Title: libfu_plugin_dell.so w/dell TB16 Dock blanks the display Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-19 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+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 1806323] Re: libfu_plugin_dell.so w/dell TB16 Dock blanks the display
I foolishly sent logs from the wrong machine. Please ignore the logs from machine "hauser" and use the logs from the machine "gene-pc". -- 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/1806323 Title: libfu_plugin_dell.so w/dell TB16 Dock blanks the display Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-19 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+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 1806323] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1806323/+attachment/5219049/+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/1806323 Title: libfu_plugin_dell.so w/dell TB16 Dock blanks the display Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-19 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+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 1806323] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1806323/+attachment/5219050/+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/1806323 Title: libfu_plugin_dell.so w/dell TB16 Dock blanks the display Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-19 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+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 1806323] Re: libfu_plugin_dell.so w/dell TB16 Dock blanks the display
apport information ** Description changed: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-11-19 (15 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1806323/+attachment/5219048/+files/Dependencies.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/1806323 Title: libfu_plugin_dell.so w/dell TB16 Dock blanks the display Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15 laptop and a Dell TB16 dock. A few seconds after logging into the Gnome 3 UI, something in the UI starts the fwupd.service. About 2 seconds later, the display goes blank and does not come back. There is no obvious recovery short of killing all the user's processes, and then logging back in. A second login does not reproduce the problem, since the fwupd service is now running, and does not restart. However manually restarting the fwupd service causes the problem to recur. The problem does not occur if the "dell" module is blacklisted in /etc/fwupd/daemon.conf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwupd 1.0.6-2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:02:31 2018 InstallationDate: Installed on 2018-11-19 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-20 (197 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin
[Kernel-packages] [Bug 1806695] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1806695/+attachment/5218998/+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/1806695 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model: Lenovo ideapad 330-15ARR Model Name: 81D2 Ubuntu Version: 18.04 LTS cat /proc/version_signature Ubuntu 4.15.0-42.45-generic 4.15.18 The touchpad didn't worked from the beginning and seems to be not detected. /proc/bus/input/devices doesn't show it. Dmesg output: ~$ dmesg | grep -i i2c [1.268675] i2c /dev entries driver [1.454039] i2c_hid i2c-ELAN061E:00: i2c-ELAN061E:00 supply vdd not found, using dummy regulator ~$ dmesg | grep -i i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [1.252982] i8042: PNP detection disabled [1.267585] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.267589] serio: i8042 AUX port at 0x60,0x64 irq 12 [1.278595] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 and lspci -vnvn attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rednblk1643 F pulseaudio /dev/snd/controlC0: rednblk1643 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-03 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN44WW:bd08/16/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0E50510NODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806695/+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 1806695] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1806695/+attachment/5219009/+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/1806695 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model: Lenovo ideapad 330-15ARR Model Name: 81D2 Ubuntu Version: 18.04 LTS cat /proc/version_signature Ubuntu 4.15.0-42.45-generic 4.15.18 The touchpad didn't worked from the beginning and seems to be not detected. /proc/bus/input/devices doesn't show it. Dmesg output: ~$ dmesg | grep -i i2c [1.268675] i2c /dev entries driver [1.454039] i2c_hid i2c-ELAN061E:00: i2c-ELAN061E:00 supply vdd not found, using dummy regulator ~$ dmesg | grep -i i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [1.252982] i8042: PNP detection disabled [1.267585] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.267589] serio: i8042 AUX port at 0x60,0x64 irq 12 [1.278595] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 and lspci -vnvn attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rednblk1643 F pulseaudio /dev/snd/controlC0: rednblk1643 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-03 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN44WW:bd08/16/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0E50510NODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806695/+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 1806695] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1806695/+attachment/5219000/+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/1806695 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model: Lenovo ideapad 330-15ARR Model Name: 81D2 Ubuntu Version: 18.04 LTS cat /proc/version_signature Ubuntu 4.15.0-42.45-generic 4.15.18 The touchpad didn't worked from the beginning and seems to be not detected. /proc/bus/input/devices doesn't show it. Dmesg output: ~$ dmesg | grep -i i2c [1.268675] i2c /dev entries driver [1.454039] i2c_hid i2c-ELAN061E:00: i2c-ELAN061E:00 supply vdd not found, using dummy regulator ~$ dmesg | grep -i i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [1.252982] i8042: PNP detection disabled [1.267585] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.267589] serio: i8042 AUX port at 0x60,0x64 irq 12 [1.278595] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 and lspci -vnvn attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rednblk1643 F pulseaudio /dev/snd/controlC0: rednblk1643 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-03 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN44WW:bd08/16/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0E50510NODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806695/+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 1806695] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1806695/+attachment/5219010/+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/1806695 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model: Lenovo ideapad 330-15ARR Model Name: 81D2 Ubuntu Version: 18.04 LTS cat /proc/version_signature Ubuntu 4.15.0-42.45-generic 4.15.18 The touchpad didn't worked from the beginning and seems to be not detected. /proc/bus/input/devices doesn't show it. Dmesg output: ~$ dmesg | grep -i i2c [1.268675] i2c /dev entries driver [1.454039] i2c_hid i2c-ELAN061E:00: i2c-ELAN061E:00 supply vdd not found, using dummy regulator ~$ dmesg | grep -i i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [1.252982] i8042: PNP detection disabled [1.267585] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.267589] serio: i8042 AUX port at 0x60,0x64 irq 12 [1.278595] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 and lspci -vnvn attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rednblk1643 F pulseaudio /dev/snd/controlC0: rednblk1643 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-03 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN44WW:bd08/16/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0E50510NODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806695/+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
