[Kernel-packages] [Bug 1798363]
The same error 5.0.0-05rc5-generic Ubuntu 18.10 ZenBook 13 UX331UAL dmesg | grep -i i2c_hid [0.984305] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [0.984317] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0 [0.984318] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator [ 306.130804] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) [ 3257.587678] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) [ 3401.698609] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things 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/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+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 1815344] [NEW] Random unrecoverable freezes on Ubuntu 18.10
Public bug reported: I reported this bug on a Samsung laptop. The same happened when using a toshiba laptop. When I open the chrome, the cursor has frozen and the screen turns off. No key combination worked and I had to force my laptop off. In the system log the error appeared at 12.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-15-generic 4.18.0-15.16 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ht 1985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Feb 10 12:59:48 2019 HibernationDevice: RESUME=UUID=6e0c43c9-f6a3-446c-a049-f4e3612debc9 InstallationDate: Installed on 2018-04-01 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: TOSHIBA Satellite A215 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=a482a589-677f-407b-b072-db9669f6f3ce ro quiet splash acpi=noirq vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-22 (140 days ago) dmi.bios.date: 01/25/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.00 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd01/25/2010:svnTOSHIBA:pnSatelliteA215:pvrPSAFGU-07101J:rvnATI:rnSB600:rvrRev1:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite A215 dmi.product.version: PSAFGU-07101J dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Attachment added: "log_bug" https://bugs.launchpad.net/bugs/1815344/+attachment/5237421/+files/log_bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815344 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: New Bug description: I reported this bug on a Samsung laptop. The same happened when using a toshiba laptop. When I open the chrome, the cursor has frozen and the screen turns off. No key combination worked and I had to force my laptop off. In the system log the error appeared at 12.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-15-generic 4.18.0-15.16 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ht 1985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Feb 10 12:59:48 2019 HibernationDevice: RESUME=UUID=6e0c43c9-f6a3-446c-a049-f4e3612debc9 InstallationDate: Installed on 2018-04-01 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: TOSHIBA Satellite A215 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=a482a589-677f-407b-b072-db9669f6f3ce ro quiet splash acpi=noirq vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-22 (140 days ago) dmi.bios.date: 01/25/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.00 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd01/25/2010:svnTOSHIBA:pnSatelliteA215:pvrPSAFGU-07101J:rvnATI:rnSB600:rvrRev1:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite A215 dmi.product.version: PSAFGU-07101J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://l
[Kernel-packages] [Bug 1815344] 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/1815344 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Confirmed Bug description: I reported this bug on a Samsung laptop. The same happened when using a toshiba laptop. When I open the chrome, the cursor has frozen and the screen turns off. No key combination worked and I had to force my laptop off. In the system log the error appeared at 12.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-15-generic 4.18.0-15.16 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ht 1985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Feb 10 12:59:48 2019 HibernationDevice: RESUME=UUID=6e0c43c9-f6a3-446c-a049-f4e3612debc9 InstallationDate: Installed on 2018-04-01 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: TOSHIBA Satellite A215 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=a482a589-677f-407b-b072-db9669f6f3ce ro quiet splash acpi=noirq vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-22 (140 days ago) dmi.bios.date: 01/25/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.00 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd01/25/2010:svnTOSHIBA:pnSatelliteA215:pvrPSAFGU-07101J:rvnATI:rnSB600:rvrRev1:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite A215 dmi.product.version: PSAFGU-07101J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815344/+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 1813873] Re: Userspace break as a result of missing patch backport
Hi, Still present in latest i386 Bionic 18.04.02 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1815225] Re: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts
Sorry, one last thing. If this issue is not an issue in later versions than 14.04 LTS, due to later-introduced hot patching for example (so that restarts are never required for updates), that would be considered a reasonable solution, and I would just upgrade to Version 16 or 18 as needed. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815225 Title: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts Status in linux package in Ubuntu: Confirmed Bug description: First, please forgive me if I do not report this issue correctly. I'm new here and don't generally live in the Launchpad world. (I've tried this at askUbuntu.com, and it was suggested I come here.) In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB hard drive running Ubuntu 14.04 LTS. Having the system exactly the way I want it, I used the application "Systemback" to install the system on a (fast) 128 GB USB drive, which, being bootable, worked exactly the same as if I booted from the hard drive. So I started using the faster 128 USB drive exclusively. Now typically, Software Updater, if not requiring a restart, updated the running USB drive just fine. But one day, after Software Updater did an update that required a restart, this happened: the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 bootloader on the laptop's hard drive got broken, to the point where neither was bootable, taking me to the dreaded "grub rescue" command line when trying to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system on it, and was able to install it from there to both the laptop's hard drive and the other now-ruined USB drive to bring them back to a pre-broken, normal existence.) With that background, I ask: Can Ubuntu's updates that require restarts merely work with the drive that was booted from, and not any affect any others (including an unmounted hard drive that was not booted from) ? If so, then anyone could get a Linux the way they want that they can take anywhere, bootable from any computer, AND update-able from any computer, bypassing all need for hard drives of any sort. No longer would people need to even buy laptops with hard drives or even operating systems. They could simply buy a smaller, cheaper, hard- drive-less and OS-less device that runs merely by plugging an Ubuntu Linux USB drive into it as "the system". Thank you very much for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-165-generic 3.13.0-165.215 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noname 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 8 12:12:35 2019 HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69 InstallationDate: Installed on 2018-12-31 (39 days ago) InstallationMedia: IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. ME051 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-165-generic N/A linux-backports-modules-3.13.0-165-generic N/A linux-firmware 1.127.24 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2018-12-31 (39 days ago) WifiSyslog: dmi.bios.date: 12/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TD535 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd12/22/2005:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0TD535:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: ME051 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815225/+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 1815225] Re: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts
Sorry... I should have said if this is no longer an issue in later **32-bit** versions... because hot patching might must be for 64 bit versions, which wouldn't help in this case. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815225 Title: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts Status in linux package in Ubuntu: Confirmed Bug description: First, please forgive me if I do not report this issue correctly. I'm new here and don't generally live in the Launchpad world. (I've tried this at askUbuntu.com, and it was suggested I come here.) In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB hard drive running Ubuntu 14.04 LTS. Having the system exactly the way I want it, I used the application "Systemback" to install the system on a (fast) 128 GB USB drive, which, being bootable, worked exactly the same as if I booted from the hard drive. So I started using the faster 128 USB drive exclusively. Now typically, Software Updater, if not requiring a restart, updated the running USB drive just fine. But one day, after Software Updater did an update that required a restart, this happened: the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 bootloader on the laptop's hard drive got broken, to the point where neither was bootable, taking me to the dreaded "grub rescue" command line when trying to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system on it, and was able to install it from there to both the laptop's hard drive and the other now-ruined USB drive to bring them back to a pre-broken, normal existence.) With that background, I ask: Can Ubuntu's updates that require restarts merely work with the drive that was booted from, and not any affect any others (including an unmounted hard drive that was not booted from) ? If so, then anyone could get a Linux the way they want that they can take anywhere, bootable from any computer, AND update-able from any computer, bypassing all need for hard drives of any sort. No longer would people need to even buy laptops with hard drives or even operating systems. They could simply buy a smaller, cheaper, hard- drive-less and OS-less device that runs merely by plugging an Ubuntu Linux USB drive into it as "the system". Thank you very much for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-165-generic 3.13.0-165.215 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noname 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 8 12:12:35 2019 HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69 InstallationDate: Installed on 2018-12-31 (39 days ago) InstallationMedia: IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. ME051 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-165-generic N/A linux-backports-modules-3.13.0-165-generic N/A linux-firmware 1.127.24 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2018-12-31 (39 days ago) WifiSyslog: dmi.bios.date: 12/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TD535 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd12/22/2005:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0TD535:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: ME051 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815225/+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 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
** Description changed: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. - - WORKAROUND: Disable XHC1 prior to sleeping via: - # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To ma
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
** Description changed: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. + + WORKAROUND: Disable XHC1 prior to sleeping: + # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name:
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
I am seeing this on an updated Cosmic with a Dell Inspiron 5570. Kernel version is presently 4.18.0-15.16. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1809843] Re: sky2 ethernet card link not up after suspend
In terminal try echo "options sky2 disable_msi=1" | sudo tee /etc/modprobe.d/sky2.conf sudo modprobe -r sky2 sudo modprobe sky2 Then test it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809843 Title: sky2 ethernet card link not up after suspend Status in linux package in Ubuntu: Confirmed Bug description: Issue is as described by the user 'kris' in #1798921 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921). Sometimes when bringing my laptop up from suspended state my Ethernet card shows link connection and activity via port LEDs but ethtool indicates the link is not up. This does not happen every time I resume from suspend, about one in 5 times. When it does happen, the following additional message is present in my dmesg output: [ 686.804877] do_IRQ: 1.37 No irq handler for vector The lspci -vvnn output for the Ethernet card is: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10) Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet Controller [1025:028e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34, in the hopes that this specific card will be added to the relevant MSI quirks table. If I do not suffer from the same issue as kris in the above linked issue, I will be happy to provide any additional information, test fixes etc. I would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if possible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: maridius 2260 F...m pulseaudio /dev/snd/controlC0: maridius 2260 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862 InstallationDate: Installed on 2015-09-01 (1212 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gateway P-79 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-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 vboxusers _MarkForUpload: True dmi.bios.date: 09/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 79.07.00 dmi.board.name: Godzilla-N10 dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A: dmi.product.name: P-79 dmi.product.version: 0100 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+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 1774443] Re: wireless hardblocked and wireless enable button not functional
Yes, the issue still persists in 4.19.20 and 5.0-rc5 On Fri, Feb 8, 2019, 9:55 AM Kai-Heng Feng wrote: > Does this still happen on latest mainline kernel? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1774443 > > Title: > wireless hardblocked and wireless enable button not functional > > Status in linux package in Ubuntu: > Confirmed > Status in network-manager package in Ubuntu: > New > > Bug description: > Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and > ubuntu. In Windows, system boots with wireless disabled and then > pressing the wireless enable button twice enables WiFi. > > In ubuntu, system boots with wireless disabled and wireless enable > button has no functionality either directly or in combination with the > fn-key. > > Module hp_wmi may be the culprit? But disabling this has no effect on > hardblock. > > reference forum post for more detailed info: > > https://ubuntuforums.org/showthread.php?t=2392934&p=13772159#post13772159 > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: network-manager 1.2.6-0ubuntu0.16.04.2 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.17 > Architecture: amd64 > CurrentDesktop: Unity > Date: Thu May 31 10:32:38 2018 > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > InstallationDate: Installed on 2018-05-19 (11 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > IpRoute: >default via 172.16.96.1 dev eno1 proto static metric 100 >169.254.0.0/16 dev eno1 scope link metric 1000 >172.16.96.0/19 dev eno1 proto kernel scope link src 172.16.119.109 > metric 100 >192.17.90.180 via 172.16.96.1 dev eno1 proto dhcp metric 100 > NetworkManager.state: >[main] >NetworkingEnabled=true >WirelessEnabled=true >WWANEnabled=true > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes > SourcePackage: network-manager > UpgradeStatus: No upgrade log present (probably fresh install) > nmcli-con: >NAMEUUID TYPE > TIMESTAMP TIMESTAMP-REAL AUTOCONNECT > AUTOCONNECT-PRIORITY READONLY DBUS-PATH > ACTIVE DEVICE STATE ACTIVE-PATH > >Wired connection 1 0357c159-f43c-38f9-8b6f-91bb641d1712 > 802-3-ethernet 1527780471 Thu 31 May 2018 10:27:51 AM CDT yes > 4294966297no/org/freedesktop/NetworkManager/Settings/0 > yes eno1activated > /org/freedesktop/NetworkManager/ActiveConnection/1 > nmcli-dev: >DEVICE TYPE STATEDBUS-PATH > CONNECTION CON-UUID CON-PATH > >eno1ethernet connected > /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 > 0357c159-f43c-38f9-8b6f-91bb641d1712 > /org/freedesktop/NetworkManager/ActiveConnection/1 >wlp8s0 wifi unavailable > /org/freedesktop/NetworkManager/Devices/1 -- -- > -- > >lo loopback unmanaged > /org/freedesktop/NetworkManager/Devices/0 -- -- > -- > nmcli-nm: >RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING > WIFI-HW WIFI WWAN-HW WWAN >running 1.2.6connected started full enabled > enabled disabled enabled enabled > --- > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: naww 1928 F pulseaudio > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.04 > HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381 > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > InstallationDate: Installed on 2018-05-19 (32 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > IpRoute: >default via 192.168.42.129 dev enp0s20u3 proto static metric 100 >169.254.0.0/16 dev enp0s20u3 scope link metric 1000 >192.168.42.0/24 dev enp0s20u3 proto kernel scope link src > 192.168.42.168 metric 100 > MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC > NetworkManager.state: >[main] >NetworkingEnabled=true >WirelessEnabled=true >WWANEnabled=true > Package: network-manager 1.2.6-0ubuntu0.16.04.2 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic > root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7 > ProcVersi
[Kernel-packages] [Bug 1539852] Re: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen
massimiliano, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539852 Title: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen Status in linux package in Ubuntu: Expired Bug description: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen which is probably all bluetooth devices on this floor of this apartment house. I have no idea what Bluetooth chipset I have, the only information I found with googling and various system information tools is "realtek". I am hoping that either Apport includes that information or you could tell me how do I dig out that information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaela1961 F pulseaudio /dev/snd/controlC1: mikaela1961 F pulseaudio CurrentDesktop: MATE Date: Sat Jan 30 09:38:26 2016 HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2 InstallationDate: Installed on 2015-12-12 (48 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:3414 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic.efi.signed root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi= RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JX.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JX.209:bd10/31/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539852/+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 1813873] Re: Userspace break as a result of missing patch backport
Hi Joe, can you please paste the output of "uname -a" from your system that is presenting this issue? Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1521123] Re: hvcs vterm driver doesn't cleanup it's tty kref allocation on close
** Tags removed: severity-high
** Tags added: severity-low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521123
Title:
hvcs vterm driver doesn't cleanup it's tty kref allocation on close
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Amartey S. Pearson - 2015-04-08
16:07:04 ==
---Problem Description---
hvcs vterm driver doesn't cleanup it's tty kref allocation on close
As a result, if the vterm device is used, closed, then hot-plug
removed, the original device (/dev/hvcsX) will never be re-used as the
.destruct method never gets called.
In the hvcs_close method, it should call tty_port_put. This in theory
would get handled by the _cleanup method, but the _close method nulls
the tty->driver_data, therefore making the _cleanup method a noop.
I made the following change which fixed the issue for me - allowed
.destruct to be called on DLPAR remove of the adapter.
*** hvcs.c2015-04-08 14:46:44.058208878 -0500
--- hvcs.c.old2015-04-08 14:45:33.726199732 -0500
***
*** 1240,1246
tty->driver_data = NULL;
free_irq(irq, hvcsd);
- tty_port_put(&hvcsd->port);
return;
} else if (hvcsd->port.count < 0) {
printk(KERN_ERR "HVCS: vty-server@%X open_count: %d"
--- 1240,1245
Contact Information = Amartey Pearson (apear...@us.ibm.com), Steven Royer
(sero...@us.ibm.com)
---uname output---
Linux ip9-114-251-60 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:18:35 UTC
2015 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = 8247-22L
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1) Create a virtual serial device from the HMC - dynamically (make sure you
have rsct etc. installed for DLPAR support). In the example below, we created
a device that provides a console to lpar 6.
chhwres -m --id -r virtualio --rsubtype serial -o
a -a adapter_type=client,remote_lpar_id=6,remote_slot_num=0
2) From your linux partition, you should now see a console device available.
You can use the handy '/sbin/hvcsadmin' tool to see the console.
# hvcsadmin -console 6
vty-server@3003 partition:6 slot:0 /dev/hvcs0 vterm-state:0
Here we can see that /dev/hvcs0 got used for lpar 6
3) Now open the device. We'll use 'socat' here, but you can use
pretty much anything (screen, etc). Once open, hit Ctl+] to exit
socat STDIO,raw,echo=0,escape=0x1d /dev/hvcs0
4) Now check your hvcsadmin -console 6 again. the vterm-state will show 1.
Let's close it. and verify it got closed (per the vterm_state)
# hvcsadmin -close /dev/hvcs0
# hvcsadmin -console 6
vty-server@3003 partition:6 slot:0 /dev/hvcs0 vterm-state:0
5) Now let's remove the device alltogether. Go back to the HMC to do
this. Here we will remove slot # 3 (because that's what we created
above - hence the 300<3> value).
chhwres -m --id -r virtualio --rsubtype serial -o
r -s 3
6) Verify you no longer have a console device on your linux lpar...this will
not print anything out.
# hvcsadmin -console 6
7) Now go ahead and re-add the device with the same command as you
ran in step #1
8) Now let's see what device it allocated. If this were behaving correctly,
it would re-allocate /dev/hvcs0, but as you'll see, it allocates /dev/hvcs1
instead.
# hvcsadmin -console 6
vty-server@3003 partition:6 slot:0 /dev/hvcs1 vterm-state:0
9) You can keep repeating these until you run out of hvcsX devices. Note
that if you skipped the 'open' step, and simply removed the device then
re-created it, the bug would not occur.
If things are working correctly, you should see the following dmesg output:
[ 5287.993312] HVCS: vty-server@3003 added to the vio bus.
[ 5287.993326] rpadlpar_io: slot U8247.22L.2125D7A-V1-C3 added
[ 5393.109677] HVCS: vty-server@3003 connection opened.
[ 5402.237382] HVCS: Closed vty-server@3003 and partner vty@3000:6
connection.
[ 5412.637292] HVCS: Destroyed hvcs_struct for vty-server@3003. <-
This is missing with the current driver
[ 5412.637298] HVCS: vty-server@3003 removed from the vio bus.
[ 5412.637355] rpadlpar_io: slot U8247.22L.2125D7A-V1-C3 removed
[ 5417.069910] HVCS: vty-server@3003 added to the vio bus.
[ 5417.069921] rpadlpar_io: slot U8247.22L.2125D7A-V1-C3 added
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for Amartey Pearson (apear...@us.ibm.com), Steven
Royer (sero...@us.ibm.com):
-Attach sysctl -a output output to the bug.
== Comment: #10 - Thierry Fauck -
2015-11-30 04:55:37 ==
To manage notifications about this bug go to
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
No package containing the fix for 18.04 has been released yet, only 18.10. It is therefore expected that 18.04.X still displays the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1813873] Re: Userspace break as a result of missing patch backport
I am running 18.04 with linux-image-generic-hwe-18.04 installed. I can confirm that the issue has been resolved with the latest kernel which is 4.18.0-15-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1488426] Re: High CPU usage of kworker/ksoftirqd
FYI still happening to me on 18.04 with HWE kernel, similar behavior as #38: kworker with steady high cpu usage after un-docking, re-docking didn't solve it tho. kernel: 4.18.0-15-generic hardware: Thinkpad x270, Thinkpad Ultra Dock, network: enp0s31f6 (dock eth) and wlp3s0 up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488426 Title: High CPU usage of kworker/ksoftirqd Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: kworker consuming 71.5% cpu resource ksoftirqd consuming 28.9% cpu resource It leads to power consumption issue and sometimes leads to BT does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1488426/+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 1814983] Re: zfs poor sustained read performance from ssd pool
echo 1 > /proc/sys/vm/drop_caches # still slow
echo 2 > /proc/sys/vm/drop_caches # goes faster
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814983
Title:
zfs poor sustained read performance from ssd pool
Status in zfs-linux package in Ubuntu:
New
Bug description:
Hello,
I'm seeing substantially slower read performance from an ssd pool than
I expected.
I have two pools on this computer; one ('fst') is four sata ssds, the
other ('srv') is nine spinning metal drives.
With a long-running ripgrep process on the fst pool, performance
started out really good and grew to astonishingly good (iirc ~30kiops,
as measured by zpool iostat -v 1). However after a few hours the
performance has dropped to 30-40 iops. top reports an arc_reclaim and
many arc_prune processes to be consuming most of the CPU time.
I've included a screenshot of top, some output from zpool iostat -v 1,
and arc_summary, with "===" to indicate the start of the next
command's output:
===
top (memory in gigabytes):
top - 16:27:53 up 70 days, 16:03, 3 users, load average: 35.67, 35.81, 35.58
Tasks: 809 total, 19 running, 612 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 58.1 sy, 0.0 ni, 39.2 id, 2.6 wa, 0.0 hi, 0.0 si, 0.0
st
GiB Mem : 125.805 total,0.620 free, 96.942 used, 28.243 buff/cache
GiB Swap:5.694 total,5.688 free,0.006 used. 27.840 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1523 root 20 00.0m 0.0m 0.0m R 100.0 0.0 290:52.26
arc_reclaim
4484 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:18.79 arc_prune
6225 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:11.92 arc_prune
7601 root 20 00.0m 0.0m 0.0m S 56.2 0.0 2:50.25 arc_prune
30891 root 20 00.0m 0.0m 0.0m S 56.2 0.0 1:33.08 arc_prune
3057 root 20 00.0m 0.0m 0.0m S 55.9 0.0 9:00.95 arc_prune
3259 root 20 00.0m 0.0m 0.0m R 55.9 0.0 3:16.84 arc_prune
24008 root 20 00.0m 0.0m 0.0m S 55.9 0.0 1:55.71 arc_prune
1285 root 20 00.0m 0.0m 0.0m R 55.6 0.0 3:20.52 arc_prune
5345 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:15.99 arc_prune
30121 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:35.50 arc_prune
31192 root 20 00.0m 0.0m 0.0m S 55.6 0.0 6:17.16 arc_prune
32287 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:28.02 arc_prune
32625 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:27.34 arc_prune
22572 root 20 00.0m 0.0m 0.0m S 55.3 0.0 10:02.92 arc_prune
31989 root 20 00.0m 0.0m 0.0m R 55.3 0.0 1:28.03 arc_prune
3353 root 20 00.0m 0.0m 0.0m R 54.9 0.0 8:58.81 arc_prune
10252 root 20 00.0m 0.0m 0.0m R 54.9 0.0 2:36.37 arc_prune
1522 root 20 00.0m 0.0m 0.0m S 53.9 0.0 158:42.45 arc_prune
3694 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:20.79 arc_prune
13394 root 20 00.0m 0.0m 0.0m R 53.9 0.0 10:35.78 arc_prune
24592 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:54.19 arc_prune
25859 root 20 00.0m 0.0m 0.0m S 53.9 0.0 1:51.71 arc_prune
8194 root 20 00.0m 0.0m 0.0m S 53.6 0.0 0:54.51 arc_prune
18472 root 20 00.0m 0.0m 0.0m R 53.6 0.0 2:08.73 arc_prune
29525 root 20 00.0m 0.0m 0.0m R 53.6 0.0 1:35.81 arc_prune
32291 root 20 00.0m 0.0m 0.0m S 53.6 0.0 1:28.00 arc_prune
3156 root 20 00.0m 0.0m 0.0m R 53.3 0.0 3:17.68 arc_prune
[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1076.86 -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) -- 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/1814651 Title: linux-aws: 4.4.0-1076.86 -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: Invalid 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 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-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-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814651/+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 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1814651 Title: linux-aws: 4.4.0-1076.86 -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: Invalid 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 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-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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814651/+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 1814755] Re: linux-raspi2: 4.18.0-1010.12 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 4.18.0-1010.12 -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) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1814755 Title: linux-raspi2: 4.18.0-1010.12 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814755/+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 1814755] Re: linux-raspi2: 4.18.0-1010.12 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:32 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1814755 Title: linux-raspi2: 4.18.0-1010.12 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814755/+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 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.18.0-1008.8 -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) -- 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/1814760 Title: linux-kvm: 4.18.0-1008.8 -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: Invalid 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 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814760/+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 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:36 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1814760 Title: linux-kvm: 4.18.0-1008.8 -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: Invalid 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 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-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814749 phase: Packaging phase-changed: Friday, 08. February 2019 01:36 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814760/+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 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)
Ok, now we finally know it is about qemu&kernel patches - I'll add tasks for that. Still haven't seen any xen references, setting that to incomplete. But given how new it is I'd punt this from 19.04 to 19.10 where things in kernel&qemu will have matured and be safer to use. If you are not ok with this please outline important use cases that will be inhibited. All changes are "just" adding definitions, no actual code added - but I'm somewhat afraid of hidden dependencies - especially since we have no associated testcase and it would need special (very new) hardware t be tested. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Triaged ** Tags added: qemu-19.10 ** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: xen (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/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 4.20/Qemu-3.10 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+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 1782206] 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 1782206 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Triaged Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 4.20/Qemu-3.10 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+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 1814749] Re: linux: 4.18.0-16.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814749 Title: linux: 4.18.0-16.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: 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 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 (linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge) derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 (linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Friday, 08. February 2019 16:03 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814749/+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
