[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Please answer all the above questions, and if you find it's still a problem in 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez) then please report the bug upstream here: https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773903] 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 1773903 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/1773903 Title: Touchpad dose not work at all Status in linux package in Ubuntu: Incomplete Bug description: I had to install Ubuntu 18.04 using "acpi=off" as the setup would not open without it . After installation the touch pad was not working at all . I have to use mouse as a pointing device . Please do help . Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773903/+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 1773906] [NEW] Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
Public bug reported: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU 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.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: New Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chas
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
More information:
This issue does not cause by single commit.
since "6b34bdd96 ("shared/gatt-client: Fix not removing services that had
disappeared", 2017-05-24)", this bug can be reproduced with low fail rate
(around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I don't reproduce this bug (maybe the reproduce rate is
very low.).
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
Bluetooth 3.0 mouses are automatically disconnected after connected
Status in OEM Priority Project:
Incomplete
Status in bluez package in Ubuntu:
Incomplete
Bug description:
The BT 3.0 mouse is disconnected automatically after connected with the
notebook.
The fail rate is around 9/10.
1. The bug only occurs on the machine with intel 8265 module.
I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
This bug can not be reproduced on the machine with Killer 1435.
2. This bug can be reproduced since bluez 5.46.
Using bluez 5.45, this bug can not be reproduced.
Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773905] [NEW] Support UVC1.5 Camera for Xenial
Public bug reported: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773903] [NEW] Touchpad dose not work at all
Public bug reported: I had to install Ubuntu 18.04 using "acpi=off" as the setup would not open without it . After installation the touch pad was not working at all . I have to use mouse as a pointing device . Please do help . Thank You. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773903 Title: Touchpad dose not work at all Status in linux package in Ubuntu: New Bug description: I had to install Ubuntu 18.04 using "acpi=off" as the setup would not open without it . After installation the touch pad was not working at all . I have to use mouse as a pointing device . Please do help . Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773903/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
Ok for Xenial (v4.4) kernel, there's one missing commit that adds UVC1.5 to device ID. The commit for this bug is still needed though. I'll send another SRU to backport the commit. ** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Another idea is to try installing 'linux-firmware', if not already, to ensure the wifi chip's firmware is up to date. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
In the meantime, please run 'apport-collect 1773897' on the problematic machine to send us more information about it. ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: oem-priority Status: New => Incomplete ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
You may also wish to try a preview of BlueZ 5.49 from here: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Please also attach the kernel log (dmesg) and the system log (journalctl -b) from the affected machine, capturing a period of time when the problem happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Sounds similar to bug 1771733 (which will hopefully expire) or bug 1651433 (which is also XPS 13). Fortunately I have multiple Logitech M337's here, so I will test them with various laptops over the coming days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
The attached file is the .snoop when I reproduced this bug. ** Attachment added: "hcitrace.snoop" https://bugs.launchpad.net/oem-priority/+bug/1773897/+attachment/5145809/+files/hcitrace.snoop ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1773581] Re: [Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43
I reverted the suspicious commit commit 2103fba9710ece54a38b2ae16359d59e904521b5 (HEAD -> refs/heads/master) Author: AceLan Kao Date: Mon May 28 23:09:37 2018 -0400 Revert "drm/i915/edp: Do not do link training fallback or prune modes on EDP" This reverts commit 116b5d52ac58a123903bfbb876c8024cfcd7b745. And here is the test kernel, please try and check if it helps, and please make sure you boot the machine with the correct kernel, this is unsigned version. Thanks. http://people.canonical.com/~acelan/bugs/lp1773581/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773581 Title: [Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43 Status in linux package in Ubuntu: Incomplete Bug description: After updating my Ubuntu 16.04 kernel from 4.13.0-41 to 4.13.0-43, I am seeing horizontal lines on the display. Rebooting into -41 makes them disappear. This is most likely the same problem as seen in 18.04 by another user: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204 (also see the attached photo there) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-43-generic 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 26 22:56:48 2018 InstallationDate: Installed on 2014-05-19 (1468 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwinkl 2305 F pulseaudio /dev/snd/controlC1: fwinkl 2305 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=00a4b15e-a4f1-4b35-9c8a-5ea33b1c6762 InstallationDate: Installed on 2014-05-19 (1468 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G NonfreeKernelModules: openafs Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ed5ec6cc-07cf-4e98-8b4e-efa0ba2d07a9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07ADU.029.141031.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-S01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07ADU.029.141031.PS:bd10/31/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP07ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-S01US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG SENS dmi.product.name: 900X3G dmi.product.version: P07ADU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773581/+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 1773897] [NEW] Bluetooth 3.0 mouses are automatically disconnected after connected
Public bug reported: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 ** Affects: oem-priority Importance: Critical Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+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 1509839] Re: segfault on start of live session in kactivitymanager / libqt5sql
[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/1509839 Title: segfault on start of live session in kactivitymanager / libqt5sql Status in linux package in Ubuntu: Expired Bug description: I've installed 15.10 Wily Werewolf to my USB stick via usb-creator and restart the laptop on boot, I'm asked for the language and if I want to install or try a live session I select try life session, the dialog disappears and the machine is frozen Next try: boot to selection dialog switch to console crtl+alt+F1 (takes a moment) issue alt+syreq+1 and alt+sysreq+t ... both answer "operation is disabled" switch back to X ctrl+alt+F7 & click try live session immediately switch back to console ctrl+alt+F1 watchdog detects hard lockup a few seconds later see attached screenshot reproduced also in beta1 of wily werewolf ... a month ago I imagine the beta was still starting, as for bug #1492840. But I've reformated the stick meanwhile and cannot really guarantee, that I didn't confuse the multiple ISO's I tried in short time. version information: kernel 4.2.0-16-generic #19-Ubuntu (4.1.0-3-generic #3-Ubuntu) libqt5sql.so 5.4.2 (both) currently running Kubuntu 15.04 on the same hardware --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu3331 F pulseaudio /dev/snd/controlC0: kubuntu3331 F pulseaudio CasperVersion: 1.365 DistroRelease: Ubuntu 15.10 LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Micro-Star International Co., Ltd. GE70 2OC\2OD\2OE Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1757IMS.520 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1757 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1757IMS.520:bd11/06/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE702OC\2OD\2OE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1757:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GE70 2OC\2OD\2OE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509839/+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 1759674] Re: Xenial fails to boot because of cryptsetup keyfiles.
[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/1759674 Title: Xenial fails to boot because of cryptsetup keyfiles. Status in linux package in Ubuntu: Expired Bug description: I always install fresh configurations apart from my working system, on logical volumes of my "victor" logical group. I always use four logical volumes per distribution : boot (clear), root (crypted), home (crypted) and usr (clear), naming them differently from a distribution to another one. Xenial logical volumes are archos (boot), odos (root), oikia (home) and trophe (usr). Only odos and oikia are concerned. To avoid typing cryptsetup keys, I rely on keyfiles. It turns out that, for reasons outside of this report, I did install grub on removable USB keys, and did not alter Windows booting procedure on my hard disk. I also record my key-files on that same device. This means that my USB key is always connected to my PC when I boot Ubuntu. My working system is Ubuntu Trusty with the 3.13.0.106-generic kernel. It does not suffer the bug I'm reporting (I discarted 3.13.0.108-generic for a reason I forgot, but it also works, as regards to the present report). Xenial does not boot, apparently because it hangs waiting for the USB device. The present bug is then a regression bug. I attached the output of "journalctl -xb" in which one can read (I translated french sentences in brakets[]) ### -- L'unité (unit) boot.mount a commencé à démarrer. [unit boot.mount started] mars 25 12:22:37 remi-Vostro-3550 systemd-udevd[666]: Process '/sbin/crda' failed with exit code 249. mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounting ext2 file system using the ext4 subsystem mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounted filesystem without journal. Opts: (null) mars 25 12:22:37 remi-Vostro-3550 systemd[1]: Mounted /boot. -- Subject: L'unité (unit) boot.mount a terminé son démarrage [unit boot.mount has finished] -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) boot.mount a terminé son démarrage, avec le résultat done.[unit boot.mount has finished and reported done] mars 25 12:23:58 remi-Vostro-3550 systemd[1]: dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device: Job dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device/start timed out. mars 25 12:23:58 remi-Vostro-3550 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device. -- Subject: L'unité (unit) dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device a échoué [unit dev-disk…-victor\x2dodos:1.device failed] -- Defined-By: systemd For testing purposes, I also installed a Xenial-B on a clear logical volume. I have being able, after boot of Xenial-B, to "cryptdisks_start" crypted logical volumes defined with the crypttab's "noauto" option. Removing the "noauto" option, without mounting the corresponding volumes with fstab, did not prevent Xenial-B to boot, but the same message as the one I mentionned ealier, appeared into the "journalctl -xb" output. I also discovered that cryptdisks_start fails if the USB key happens to be mounted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-106-generic 3.13.0-106.153 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remi 3564 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 28 22:15:20 2018 InstallationDate: Installed on 2014-05-30 (1397 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3550 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-106-generic root=/dev/mapper/victor-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.23 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.ve
[Kernel-packages] [Bug 1759807] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-timesyn:564]
[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/1759807 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd- timesyn:564] Status in linux package in Ubuntu: Expired Bug description: Dell XPS 15 9560 bug on startup ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1007 F pulseaudio rewkha 1411 F pulseaudio Date: Wed Mar 28 17:56:11 2018 Failure: oops InstallationDate: Installed on 2018-03-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=44b23c80-4a76-456b-ae80-537ac0e54727 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-timesyn:564] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759807/+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 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
I have tested both artful-proposed (4.13.0-44-generic #49-Ubuntu SMP Thu
May 24 09:57:43 UTC 2018 x86_64) and bionic-proposed (4.15.0-23-generic
#25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64) kernels, and they
behave correctly on my Latitude 5590.
** Tags removed: verification-needed-artful verification-needed-bionic
** Tags added: verification-done-artful verification-done-bionic
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764194
Title:
Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
black screen at boot. Specifying 'nomodeset' on the kernel command line works
around the problem.
Intel resolved the problem in upstream commit a3520b8992e5. This commit
is now in mainline as of 4.17.rc2. It has also been cc'd to upstream
stable.
== Fix ==
a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child
devices")
== Regression Potential ==
Low. This commit was also cc'd to upstream stable, so it recieved
additional upstream review.
Description:Ubuntu 16.04.4 LTS
Release:16.04
Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
laptops, originally running BIOS version 1.0.8. The install media and
the installed OS was running linux-generic-hwe kernel 4.13.0.
After upgrading BIOS to latest version 1.1.9, the kernel no longer
boots: right after loading the i915 drm driver, the screen goes black,
and the machine can only be reset or power cycled. This is true for
both the installation media, and the OS instance previously installed
to the disk and updated to the latest hwe kernel 4.13.0-38.
Specifying 'nomodeset' on the kernel command line works around the
problem by disabling the i915 drm driver functionality. In that case,
several display driver function are obviously missing (eg GLX &
xrandr).
The problem manifested itself even when using the drm upstream latest
git-head version. A custom built kernel was used to provide logs for this
upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=105549
The upstream Intel developers provided a patch, which was successfully tested
by both the original reporter and me.
https://patchwork.freedesktop.org/patch/216371/
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde
I backported this fix to ubuntu-xenial hwe git-head, and tested the
result successfully. I'd like this fix to be added to the ubuntu-
xenial linux-generic-hwe kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764194/+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 1772760] Re: Touchpad slows down and then stops working
I've been using the linux kernel 4.17.0-041700rc6-generic for 1 day and just now it happened again. So it is not fixed in that version of the kernel. ** Tags added: kernel-bug-exists-upstrea ** Tags removed: kernel-bug-exists-upstrea ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772760 Title: Touchpad slows down and then stops working Status in linux package in Ubuntu: Confirmed Bug description: Cannot find a reason, but sometimes once a day, sometimes twice a day, my touchpad starts to work slowly, like jumping, and after a few seconds, it completely stops working. At some point, I did something with Terminal and it started working, but cannot reproduce it. The only thing that seems to be really working is to Suspend laptop and come back in Ubuntu (or restart, but that means to close everything + it takes more time). While I wrote this text, it seems to have recovered by itself, it is working right now, but this is unreliable and cannot be used in production (what about stopping it during a presentation, cannot suspend in a meeting). Hopefully, it is some kernel problem, as I reported kernel package. 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 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 01:15:44 2018 InstallationDate: Installed on 2018-04-27 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: florin 2029 F...m pulseaudio /dev/snd/controlC0: florin 2029 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8 InstallationDate: Installed on 2018-04-27 (26 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 002: ID 13d3:5652 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE P50-C dmi.product.version: PSPUFE-001009G6 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772760/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
FWIW, v4.12.14 also works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
Confirmed
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
v4.12 Final works. v4.13-rc1 does not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
Confirmed
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1490130] Re: [Asus X455LD] Elantech touchpad stops working after suspend
** Tags added: bios-outdated-208 needs-upstream-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490130 Title: [Asus X455LD] Elantech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 4.0.8-040008-generic. touchpad is recognized as elantech version 4. everything was fine until my notebook go to suspend and resume without touchpad working. I tried : modprobe -r psmouse modprobe psmouse it only work before suspend. execute those commands after resume from suspend is not working. the last thing i tried is this. when i use this command before suspend : insmod /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko these appear in the dmesg: [ 820.207105] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) [ 820.70] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. [ 820.294698] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input146 but when i use the command after suspend, there is nothing any output in the dmesg. i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. but in windows 10, touchpad still active after suspend. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-20 (69 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.8-040008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackhole 1460 F pulseaudio /dev/snd/controlC1: blackhole 1460 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a InstallationDate: Installed on 2015-06-20 (129 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LDB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash i915.enable_ips=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LDB.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LDB 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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X455LDB 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/1490130/+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 1490130] Re: [Asus X455LD] Elantech touchpad stops working after suspend
I think the bug was fixed since the patch changed over time and now it looks for all ASUS laptops in order to skip selftests: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77b425399f6d5f1b04c58738bc10ca6decb10c9a Sergey Zolotarev, can you please test again with a recent kernel and tell us if the issue was fixed? It should work with every modern ASUS laptop, so everyone who commented in this bug, please test against a newer kernel release. 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/1490130 Title: [Asus X455LD] Elantech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 4.0.8-040008-generic. touchpad is recognized as elantech version 4. everything was fine until my notebook go to suspend and resume without touchpad working. I tried : modprobe -r psmouse modprobe psmouse it only work before suspend. execute those commands after resume from suspend is not working. the last thing i tried is this. when i use this command before suspend : insmod /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko these appear in the dmesg: [ 820.207105] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) [ 820.70] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. [ 820.294698] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input146 but when i use the command after suspend, there is nothing any output in the dmesg. i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. but in windows 10, touchpad still active after suspend. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-20 (69 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.8-040008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackhole 1460 F pulseaudio /dev/snd/controlC1: blackhole 1460 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a InstallationDate: Installed on 2015-06-20 (129 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LDB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash i915.enable_ips=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LDB.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LDB 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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X455LDB 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/1490130/+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 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
marvin: 1) Regarding the scaling and mouse issues, these are outside the scope of this report. Hence, feel free to file a separate report about each one by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information via a terminal: ubuntu-bug xorg 2) Regarding the scope of this report, could you please provide the missing information from https://wiki.ubuntu.com/Kernel/Debugging/Backlight? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1772964] Re: linux-kvm: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1772964 Title: linux-kvm: 4.4.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772964/+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 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1772966 Title: linux-aws: 4.4.0-1061.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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 -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New 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: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1772963 Title: linux-aws: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+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 1773676] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145642/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
Don't see the point in adding log files for a simple and obvious typo, but before code was added for this fix I believe I did generate before and after logs under bug ID #1710548. In any case I'm running kernels in which I've fixed the typo. Status changed to confirmed. ** 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/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: Confirmed Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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 1750038] Re: user space process hung in 'D' state waiting for disk io to complete
Created By: David Coronel (28/05/2018 4:28 PM)
Good day Sam, Jamie,
The kernel 4.4.0-128-generic #154 is now ready for testing by Nvidia:
linux | 4.4.0-128.154 | xenial-proposed | source
linux-image-4.4.0-128-generic | 4.4.0-128.154 | xenial-proposed | amd64, arm64,
armhf, i386, ppc64el, s390x
You have 5 working days from today to test and report results. If you
don't test this package, the patch will be reverted from the kernel.
You can find the instructions to test from -proposed here:
https://wiki.ubuntu.com/Testing/EnableProposed
Let me know if you have any questions.
Thank you,
David
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1750038
Title:
user space process hung in 'D' state waiting for disk io to complete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
[Fix]
Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is
upstream in:
ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback")
[Testcase]
See Test scenario in previous description.
A test kernel with this patch was tested heavily (>100hrs of test
suite) without issue.
[Regression Potential]
This changes memory allocation in NFS to use a different policy. This could
potentially affect NFS.
However, the patch is already in Artful and Bionic without issue.
The patch does not apply to Trusty.
== Previous Description ==
Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.
Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces
seems to be stuck in kmalloc allocation during cleanup of dirty NFS
pages.
All the subsequent operations on the NFS mounts are stuck and reboot
is required to rectify the situation.
[Test scenario]
1) Applications running in Docker environment
2) Application have cgroup limits --cpu-shares --memory -shm-limit
3) python and C++ based applications (torch and caffe)
4) Applications read big lmdb files and write results to NFS shares
5) use NFS v3 , hard and fscache is enabled
6) now swap space is configured
This prevents all other I/O activity on that mount to hang.
we are running into this issue more frequently and identified few
applications causing this problem.
As updated in the description, the problem seems to be happening when
exercising the stack
try_to_free_mem_cgroup_pages+0xba/0x1a0
we see this with docker containers with cgroup option --memory
.
whenever there is a deadlock, we see that the process that is hung has
reached the maximum cgroup limit, multiple times and typically cleans
up dirty data and caches to bring the usage under the limit.
This reclaim path happens many times and finally we hit probably a
race get into deadlock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+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 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
** Tags removed: regression-release ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1773676] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145645/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145640/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145650/+files/UdevLog.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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1772953] Re: linux-gcp: 4.13.0-1018.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 28. May 2018 18:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 28. May 2018 18:02 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1772953 Title: linux-gcp: 4.13.0-1018.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772953/+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 1773676] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145648/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145647/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145639/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145651/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145649/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145636/+files/BootDmesg.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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 28. May 2018 18:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 28. May 2018 18:03 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772963 Title: linux-aws: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+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 1773676] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145646/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145644/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] Re: Apport crashing on resume...
Missing log files appended per request ** 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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 28. May 2018 18:04 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 28. May 2018 18:04 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772966 Title: linux-aws: 4.4.0-1061.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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 -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
Same here, Asus N550JK with Nvidia 850M. After switch to Intel by Nvidia-prime and restart, I can see huge consumption, around 22W. When I disable nouveau completely, by disabling the Nvidia fallback service and then turning off the GPU using old bbswitch, I get 11W which is normal for this laptop with turned off GPU. So bbswitch still works, but vgaswitcheroo doesn't. Pity that bumblebee doesn't work anymore... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1772964] Re: linux-kvm: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded + kernel-stable-phase-changed:Monday, 28. May 2018 18:33 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 - phase: Uploaded - kernel-stable-phase-changed:Monday, 28. May 2018 18:33 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1772964 Title: linux-kvm: 4.4.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772964/+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 1773676] Re: Apport crashing on resume...
apport information ** Tags added: apport-collected ** Description changed: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS + --- + ApportVersion: 2.14.1-0ubuntu3.28 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: paul 2461 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 + InstallationDate: Installed on 2013-09-07 (1723 days ago) + InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) + MachineType: Gateway NE56R + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-149-generic N/A + linux-backports-modules-3.13.0-149-generic N/A + linux-firmware 1.127.24 + Tags: trusty + Uname: Linux 3.13.0-149-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/25/2012 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V2.11 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: EG50_HC_HR + dmi.board.vendor: Gateway + dmi.board.version: Type2 - Board Version + dmi.chassis.type: 10 + dmi.chassis.vendor: Insyde Corp. + dmi.chassis.version: V2.11 + dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: + dmi.product.name: NE56R + dmi.product.version: V2.11 + dmi.sys.vendor: Gateway ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145635/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:c
[Kernel-packages] [Bug 1773676] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145638/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1087010] Re: kworker uses 70-90% of a CPU core (hyperthreaded)
I dont't believe my laptop has a free fall sensor, didn't ever hear of such a thing. How do I check? It does have ExpressCache though. My vague hypothesis is that it has something to do with the ODD but i don't understand enough of this for being able to verify any of this without instructions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1087010 Title: kworker uses 70-90% of a CPU core (hyperthreaded) Status in linux package in Ubuntu: Triaged Bug description: I see high (70-90%) cpu usage from a kworker thread. Usually kworker/0:1 or kworker/0:2. This does not always happen. On some boots all is fine but once it shows, rebooting does not make it go away. WORKAROUND: Execute: echo "disable" > /sys/firmware/acpi/interrupts/gpe13 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-19-generic 3.5.0-19.30 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1965 F pulseaudio /dev/snd/pcmC0D0p: mio1965 F...m pulseaudio Date: Wed Dec 5 22:37:00 2012 HibernationDevice: RESUME=UUID=a371882c-0fe7-45e5-9adb-83da8374bc11 InstallationDate: Installed on 2012-10-10 (55 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=79674508-93de-43e0-b313-f6a9b480c606 ro crashkernel=384M-2G:64M,2G-:128M acpi_osi=Linux pcie_aspm=force i915.modeset=1 i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.semaphores=1 i915.powersave=1 snd_hda_intel.power_save_controller=1 snd_hda_intel.power_save=1 quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/mio not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-19-generic N/A linux-backports-modules-3.5.0-19-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-10-11 (55 days ago) dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 700Z7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1568 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=3f9af81f-77f0-4438-9a4b-6722de269cbb InstallationDate: Installed on 2018-05-09 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=7c436149-ab84-40d0-919f-032364393f9b ro quiet splash video=VGA1:d nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:
[Kernel-packages] [Bug 1773676] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145641/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145637/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1773676/+attachment/5145643/+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/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Confirmed Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS --- ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2461 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=411d104d-f8d0-48ec-be31-68d4beaa9c66 InstallationDate: Installed on 2013-09-07 (1723 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Gateway NE56R Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic.efi.signed root=UUID=351a862d-c262-4050-bdc7-92ed4952d853 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-12 (1173 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:svnGateway:pnNE56R:pvrV2.11:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11: dmi.product.name: NE56R dmi.product.version: V2.11 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773828] 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/1773828 Title: Bluetooth no se activa no encuentra adapatdores por lo que no se conecta Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth no se activa no encuentra adapatdores por lo que no se conecta ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dafne 1765 F pulseaudio CurrentDesktop: Unity Date: Mon May 28 10:55:41 2018 HibernationDevice: RESUME=UUID=79ddee5d-4d53-46b9-8258-e69c02b97184 InstallationDate: Installed on 2018-05-08 (20 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV/2470EV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=869404d4-cd20-440d-a400-128fbf32948d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07RBF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP270E4E-K06VE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07RBF:bd10/24/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV/2470EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E4E-K06VE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773828/+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 1773828] [NEW] Bluetooth no se activa no encuentra adapatdores por lo que no se conecta
Public bug reported: Bluetooth no se activa no encuentra adapatdores por lo que no se conecta ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dafne 1765 F pulseaudio CurrentDesktop: Unity Date: Mon May 28 10:55:41 2018 HibernationDevice: RESUME=UUID=79ddee5d-4d53-46b9-8258-e69c02b97184 InstallationDate: Installed on 2018-05-08 (20 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV/2470EV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=869404d4-cd20-440d-a400-128fbf32948d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07RBF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP270E4E-K06VE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07RBF:bd10/24/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV/2470EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E4E-K06VE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773828 Title: Bluetooth no se activa no encuentra adapatdores por lo que no se conecta Status in linux package in Ubuntu: New Bug description: Bluetooth no se activa no encuentra adapatdores por lo que no se conecta ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dafne 1765 F pulseaudio CurrentDesktop: Unity Date: Mon May 28 10:55:41 2018 HibernationDevice: RESUME=UUID=79ddee5d-4d53-46b9-8258-e69c02b97184 InstallationDate: Installed on 2018-05-08 (20 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV/2470EV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=869404d4-cd20-440d-a400-128fbf32948d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07RBF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP270E4E-K06VE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07RBF:bd10/24/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV/2470EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E4E-K06VE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773828/+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 1752536] Re: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic
kernel proposed activated :~$ uname -r 4.4.0-128-generic the problem has been solved by you, thank you! below the log output :~$ dmesg | grep i915 [1.039248] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [1.039662] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [1.040117] [drm:i915_ggtt_init_hw] GMADR size = 256M [1.040118] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [1.040119] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.049247] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.049793] [drm] Finished loading i915/kbl_dmc_ver1.bin (v1.1) [1.054392] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=30 [1.054395] [drm:i915_pages_create_for_stolen] offset=0x0, size=3145728 [1.054722] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 30 [1.054723] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [30, f000] [1.055941] [drm:i915_gem_context_init] LR context support initialized [1.059408] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.320757] [drm:i915_gem_object_create_stolen] creating stolen object: size=408000 [1.320760] [drm:i915_pages_create_for_stolen] offset=0x30, size=4227072 [1.640286] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.882062] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 24.554262] [drm:i915_gem_open] [ 24.554407] [drm:i915_gem_open] [ 24.554502] [drm:i915_gem_open] [ 24.554597] [drm:i915_gem_open] [ 32.719195] [drm:i915_gem_open] [ 33.460413] [drm:i915_gem_open] [ 33.474453] [drm:i915_gem_open] [ 40.532613] [drm:i915_gem_open] [ 46.456349] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 46.462564] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 46.547249] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 46.554472] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 46.556057] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 46.562544] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.340801] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.348924] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.351803] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.356905] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.359653] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 131.364903] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 141.643165] [drm:i915_gem_open] [ 142.158782] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 142.269302] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 214.103983] [drm:i915_gem_open] [ 214.129466] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 214.274136] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 224.526911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 225.390754] [drm:i915_gem_context_create_ioctl] HW context 2 created [ 226.006532] [drm:i915_gem_context_create_ioctl] HW context 3 created [ 226.020551] [drm:i915_gem_context_create_ioctl] HW context 4 created [ 226.246106] [drm:i915_gem_context_create_ioctl] HW context 5 created [ 227.173567] [drm:i915_gem_open] [ 227.198117] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 227.271472] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 227.508930] [drm:i915_gem_context_create_ioctl] HW context 6 created [ 227.512895] [drm:i915_gem_context_create_ioctl] HW context 7 created [ 228.564830] [drm:i915_gem_context_create_ioctl] HW context 8 created [ 262.716707] [drm:i915_gem_context_create_ioctl] HW context 9 created [ 262.720343] [drm:i915_gem_context_create_ioctl] HW context 10 created [ 262.732525] [drm:i915_gem_context_destroy_ioctl] HW context 8 destroyed [ 262.745533] [drm:i915_gem_context_destroy_ioctl] HW context 4 destroyed [ 262.746304] [drm:i915_gem_context_destroy_ioctl] HW context 3 destroyed [ 262.748930] [drm:i915_gem_context_destroy_ioctl] HW context 7 destroyed [ 262.749336] [drm:i915_gem_context_destroy_ioctl] HW context 6 destroyed [ 382.283507] [drm:i915_gem_context_create_ioctl] HW context 3 created [ 382.291001] [drm:i915_gem_context_create_ioctl] HW context 4 created [ 382.872217] [drm:i915_gem_context_destroy_ioctl] HW context 10 destroyed [ 382.873674] [drm:i915_gem_context_destroy_ioctl] HW context 9 destroyed [ 383.610506] [drm:i915_gem_context_create_ioctl] HW context 6 created [ 384.122684] [drm:i915_gem_context_destroy_ioctl] HW context 6 destroyed [ 449.236426] [drm:
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
IBM is seeing tm_sigreturn test failures on P8 and P9 hosts. The bad thing
exception is being raised when executing the following line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why they are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
This test failure is fixed by upstream commit 78a3e8889b4b.
Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.
== Fix ==
78a3e8889b4b ("powerpc: signals: Discard transaction state from signal
frames")
== Regression Potential ==
Low. Specific to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
This test fails in the same way on a P8 host, so it is nothing to do with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-
transactional state" and the MSR is set to be transactional
(suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08: 00
[Kernel-packages] [Bug 1772505] Re: [18.04] [regression testing] ubuntu_fan_smoke_tests failing on s390x
05/03 05:08:54 DEBUG| utils:0116| Running 'DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes build-essential gdb git docker.io ubuntu-fan gcc' 2. 05/03 05:08:54 DEBUG| utils:0153| [stdout] Reading package lists... 3. 05/03 05:08:54 DEBUG| utils:0153| [stdout] Building dependency tree... 4. 05/03 05:08:54 DEBUG| utils:0153| [stdout] Reading state information... 5. 05/03 05:08:54 DEBUG| utils:0153| [stdout] gcc is already the newest version (4:7.3.0-3ubuntu2). 6. 05/03 05:08:54 DEBUG| utils:0153| [stdout] gdb is already the newest version (8.1-0ubuntu3). 7. 05/03 05:08:54 DEBUG| utils:0153| [stdout] git is already the newest version (1:2.17.0-1ubuntu1). 8. 05/03 05:08:54 DEBUG| utils:0153| [stdout] ubuntu-fan is already the newest version (0.12.10). 9. 05/03 05:08:54 DEBUG| utils:0153| [stdout] docker.io is already the newest version (17.12.1-0ubuntu1). 10. 05/03 05:08:54 DEBUG| utils:0153| [stdout] build-essential is already the newest version (12.5ubuntu2). 11. 05/03 05:08:54 DEBUG| utils:0153| [stdout] The following packages were automatically installed and are no longer required: 12. 05/03 05:08:54 DEBUG| utils:0153| [stdout] linux-headers-4.15.0-19 linux-headers-4.15.0-19-generic 13. 05/03 05:08:54 DEBUG| utils:0153| [stdout] linux-image-4.15.0-19-generic linux-modules-4.15.0-19-generic 14. 05/03 05:08:54 DEBUG| utils:0153| [stdout] linux-modules-extra-4.15.0-19-generic 15. 05/03 05:08:54 DEBUG| utils:0153| [stdout] Use 'sudo apt autoremove' to remove them. 16. 05/03 05:08:54 DEBUG| utils:0153| [stdout] 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 17. 05/03 05:08:54 ERROR| utils:0153| [stderr] W: --force-yes is deprecated, use one of the options starting with --allow instead. 18. 05/03 05:08:54 DEBUG| utils:0116| Running 'ip address' 19. 05/03 05:08:54 DEBUG| utils:0116| Running './ubuntu_fan_smoke_test.sh 10.245.0.0/16' 20. 05/03 05:08:57 DEBUG| utils:0153| [stdout] Running in the Canonical CI environment 21. 05/03 05:09:04 DEBUG| utils:0153| [stdout] Testing Fan Networking (pre-0.13.0 API) 22. 05/03 05:09:18 DEBUG| utils:0153| [stdout] docker pull s390x/ubuntu: PASSED 23. 05/03 05:09:20 DEBUG| utils:0153| [stdout] enable disable fan test: PASSED 24. 05/03 05:09:20 DEBUG| utils:0153| [stdout] fanctl show test: PASSED 25. 05/03 05:09:21 DEBUG| utils:0153| [stdout] fanctl check bridge config test: PASSED 26. 05/03 05:09:30 ERROR| utils:0153| [stderr] debconf: delaying package configuration, since apt-utils is not installed 27. 05/03 05:09:42 ERROR| utils:0153| [stderr] Job for docker.service failed. 28. 05/03 05:09:42 ERROR| utils:0153| [stderr] See "systemctl status docker.service" and "journalctl -xe" for details. 29. 05/03 05:09:42 DEBUG| utils:0153| [stdout] fanatic docker test(--dns=10.245.80.1): FAILED (fanatic enable-docker returned 1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772505 Title: [18.04] [regression testing] ubuntu_fan_smoke_tests failing on s390x Status in linux package in Ubuntu: Triaged Bug description: see logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772505/+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 1759836] Re: systemd-udevd consumes 100% of CPU
I tried it with mainline 4.16.12 and 4.17-rc7 on the Dell Latitude and the problem still exists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1772964] Re: linux-kvm: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1772964 Title: linux-kvm: 4.4.0-1027.32 -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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: 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 Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772964/+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 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772963 Title: linux-aws: 4.4.0-1023.23 -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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: 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 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+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 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772966 Title: linux-aws: 4.4.0-1061.70 -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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+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 1772953] Re: linux-gcp: 4.13.0-1018.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1772953 Title: linux-gcp: 4.13.0-1018.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772953/+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 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
** Summary changed: - linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present + linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.ne
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
Observed sequence of sbins when software-updater called apt-get upgrade linux-firmware: Cross-checking initramfs-tools and depmod for any misbehaviors that might exacerbate what I've observed. DIOSCOVERED POINT TO INVESTIGATE: Potential for Dependency this Bug on Bug #701578 "purging a kernel sometimes fails to remove kernel in armel" in initramfs-tools (ubuntu). ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic - Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. - --- + Same configuration report for "Setting up linux-firmware..." with sudo + apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade + linux-firmware. Therefore: + + Reproducible: Always + Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. + Actual results, excepting actually installed Kernel Image packages: + + update-initramfs: Generating /boot/initrd.img-4.8.0-56 + WARNING: missing /lib/modules/4.8.0-56 + Ensure all necessary drivers are built into the linux image! + depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory + depmod: FATAL: could not search modules: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory + update-initramfs: Generating /boot/initrd.img-4.8.0 + WARNING: missing /lib/modules/4.8.0 + Ensure all necessary drivers are built into the linux image! + depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory + depmod: FATAL: could not search modules: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory + + Expected results, excepting actually installed Kernel Image packages: + + No attempt to generate /boot/initrd.img for missing kernels, thus no + warnings, errors or fatals. + + --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: - + DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz pr
[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
I have accepted both the xenial and bionic wireless-regdb uploads. One thing that stood out was the __eq__ implementation in the 0001-wireless- regdb-Fix-comparison-of-WmmRule-with-NoneTy.patch patch which seems to look a bit strange (no _as_tuple() before the comparison), but I have been informed that even if it's wrong it will have no impact on the actual package. Just something worth noting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: Fix Committed Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1769980] Please test proposed package
Hello Anthony, or anyone else affected, Accepted wireless-regdb into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2018.05.09-0ubuntu1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: Fix Committed Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
Hello Anthony, or anyone else affected, Accepted wireless-regdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2018.05.09-0ubuntu1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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! ** Changed in: wireless-regdb (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-bionic ** Changed in: wireless-regdb (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: Fix Committed Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/
[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
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-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761674
Title:
[Ubuntu 16.04] kernel: fix rwlock implementation
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reported this bug due to a regression introduced by mainline commit
94232a4332de. IBM has requested this SAUCE backport to resolve this
regression in Artful and Xenial.
With Bionic and v4.15, the rwlock code has been rewritten. See upstream
gitcommit:
eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").
Since the upstream code has been rewritten there also won't be an upstream
git commit id available which contains the attached fix.
== Fix ==
UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation
== Regression Potential ==
Low. The backport was written and tested by IBM. It is specific to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Description: kernel: fix rwlock implementation
Symptom: Kernel hangs, due to deadlock on an rwlock.
Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
write-lock the lock, then CPU 1 sets the writer bit and
afterwards busy waits for CPU 0 to release the lock. If now CPU 0
tries to read-lock the lock again (recursively) it will also
busy
wait until CPU 1 removes the writer bit, which will never
happen,
since it waits for the first reader on CPU 0 to release the
lock.
Solution: Revert the rwlock writer fairness semantics again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1761674/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752536] Re: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752536 Title: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial :~$ uname -r 4.4.0-116-generic The problem :~$ dmesg | grep i915 [0.991220] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [0.991711] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [0.992136] [drm:i915_ggtt_init_hw] GMADR size = 256M [0.992137] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [0.992138] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.001094] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.001114] i915_bpo :00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2 [1.001119] i915_bpo :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [1.005895] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=408000 [1.005897] [drm:i915_pages_create_for_stolen] offset=0x0, size=4227072 [1.006228] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 408000 [1.006230] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [408000, f000] [1.007450] [drm:i915_gem_context_init] LR context support initialized [1.010861] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.857985] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.248704] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 18.739304] [drm:i915_gem_open] [ 18.739408] [drm:i915_gem_open] [ 18.739484] [drm:i915_gem_open] [ 18.739524] [drm:i915_gem_open] [ 33.631792] [drm:i915_gem_open] [ 35.515257] [drm:i915_gem_open] [ 35.582793] [drm:i915_gem_open] [ 42.823681] [drm:i915_gem_open] [ 47.557725] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.565183] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.566992] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.573099] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.574721] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.581074] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.035670] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.044499] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.046373] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.052451] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.054246] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.060454] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 969.549771] [drm:i915_gem_open] [ 969.704665] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 969.794654] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1125.305318] [drm:i915_gem_open] [ 1125.328165] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1125.333583] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1227.799188] [drm:i915_gem_open] [ 1227.806911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1227.807865] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1436.623061] [drm:i915_gem_open] [ 1436.629327] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1436.630138] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1459.597494] [drm:i915_gem_open] [ 1459.603754] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1459.604550] [
[Kernel-packages] [Bug 1766054] Re: Acer Swift sf314-52 power button not managed
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766054 Title: Acer Swift sf314-52 power button not managed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level: [405.267887] acer_wmi: Unknown key number - 0x87] This patch adds the KEY_POWER event in acer-wmi. The patch will also be sent upstream, but it is being requested in Ubuntu to not wait for it to come back downstream. This patch is also needed in Xenial, but Xenial requres a minor backport. == Fix == UBUNTU: SAUCE: platform/x86: acer-wmi: add another KEY_POWER keycode == Regression Potential == Low. This is a oneliner that addes a new keymap. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level [405.267887] acer_wmi: Unknown key number - 0x87] I develop and test on Acer Swift sf314-52 a patch that fix the issue adding the KEY_POWER event in acer-wmi. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766054/+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 1770565] Re: [i915_bpo] Fix flickering issue after panel change
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770565 Title: [i915_bpo] Fix flickering issue after panel change Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] A certain OEM laptop changed the panel type/vendor, and the change regressed the driver causing a flickering image. The ODM has tools to measure various values of the driver/panel combination, and determined that some voltage levels were way too low to pass the spec. The process to bisect the commits took weeks, so while it's technically possible that this issue was fixed by a single commit (drm/i915: Ignore OpRegion panel type except on select machines), we've also kept another 10 commits which upstream thought should help (and did, they improved the measured values but not enough). So, this backport carries all 11 commits from 4.8/4.9 that the ODM verified to pass the tests. [Test case] Needs to be tested with the ODM tools to be sure. [Regression potential] There is some, but apart from the necessary refactoring the rest are bugfixes to match the HW specs, so this should in fact fix a lot more than just this certain machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1770565/+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 1750038] Re: user space process hung in 'D' state waiting for disk io to complete
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
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-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1750038
Title:
user space process hung in 'D' state waiting for disk io to complete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
[Fix]
Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is
upstream in:
ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback")
[Testcase]
See Test scenario in previous description.
A test kernel with this patch was tested heavily (>100hrs of test
suite) without issue.
[Regression Potential]
This changes memory allocation in NFS to use a different policy. This could
potentially affect NFS.
However, the patch is already in Artful and Bionic without issue.
The patch does not apply to Trusty.
== Previous Description ==
Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.
Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces
seems to be stuck in kmalloc allocation during cleanup of dirty NFS
pages.
All the subsequent operations on the NFS mounts are stuck and reboot
is required to rectify the situation.
[Test scenario]
1) Applications running in Docker environment
2) Application have cgroup limits --cpu-shares --memory -shm-limit
3) python and C++ based applications (torch and caffe)
4) Applications read big lmdb files and write results to NFS shares
5) use NFS v3 , hard and fscache is enabled
6) now swap space is configured
This prevents all other I/O activity on that mount to hang.
we are running into this issue more frequently and identified few
applications causing this problem.
As updated in the description, the problem seems to be happening when
exercising the stack
try_to_free_mem_cgroup_pages+0xba/0x1a0
we see this with docker containers with cgroup option --memory
.
whenever there is a deadlock, we see that the process that is hung has
reached the maximum cgroup limit, multiple times and typically cleans
up dirty data and caches to bring the usage under the limit.
This reclaim path happens many times and finally we hit probably a
race get into deadlock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+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 1769671] Re: [Xenial] Kernels OOPS when mwifiex is in AP mode
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769671 Title: [Xenial] Kernels OOPS when mwifiex is in AP mode Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: There's quite a chance to find kernel oops when mwifiex is in AP mode. Previously two workaround commits were added in the Xenial kernel, 8a034f97a28dba62026343eef7992766c91273a7 and f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The original report can be found at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 . Now that a fix has been merged in mainline, it's time to revert the workaround and apply the fix: commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3 Author: Limin Zhu Date: Thu Nov 30 14:22:34 2017 +0800 mwifiex: cfg80211: do not change virtual interface during scan processing (1) Change virtual interface operation in cfg80211 process reset and reinitilize private data structure. (2) Scan result event processed in main process will dereference private data structure concurrently, ocassionly crash the kernel. The cornel case could be trigger by below steps: (1) wpa_cli mlan0 scan (2) ./hostapd mlan0.conf Cfg80211 asynchronous scan procedure is not all the time operated under rtnl lock, here we add the protect to serialize the cfg80211 scan and change_virtual interface operation. Signed-off-by: Limin Zhu Signed-off-by: Xinming Hu Signed-off-by: Kalle Valo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769671/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- 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/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage noti
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Friday, 25. May 2018 14:32 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 28. May 2018 14:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 28. May 2018 14:03 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New 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: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
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-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
IBM is seeing tm_sigreturn test failures on P8 and P9 hosts. The bad thing
exception is being raised when executing the following line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why they are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
This test failure is fixed by upstream commit 78a3e8889b4b.
Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.
== Fix ==
78a3e8889b4b ("powerpc: signals: Discard transaction state from signal
frames")
== Regression Potential ==
Low. Specific to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
This test fails in the same way on a P8 host, so it is nothing to do with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-
transactional state" and the MSR is set to be transactional
(suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c00
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
** Description changed: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. + + --- + + wireless-regdb SRU Justification + + Impact: New regulatory requirements in the EU necessitate updating our + wireless regulatory database. + + Fix: New upstream release. + + Test Case: Minimal testing would be to reload the regdb (can be done + with iw built from git or by rebooting) and verifying that you are able + to change regulatory domains (e.g., sudo iw reg set US; iw reg get). + + Regression Potential: Minimal. Biggest risk would be the inability to + load the new database due to the changes in signing, however testing + will confirm that appropriate key is present. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: New Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requir
[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue
This bug was fixed in the package linux-firmware - 1.173.1 --- linux-firmware (1.173.1) bionic; urgency=medium * Redpine: BLE radio lost issue (LP: #1757443) - linux-firmware: rsi: update firmware images for Redpine 9113 chipset * Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement (LP: #1769980) - iwlwifi: add some new FW versions and update older ones - iwlwifi: update firmwares for 3160, 3168 and 7265 -- Seth Forshee Fri, 18 May 2018 13:09:45 -0500 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1757443 Title: Redpine: BLE radio lost issue Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in linux source package in Xenial: Triaged Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Bionic: Incomplete Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification Impact: Radio stops capturing advertisements after several hours. Fix: Updated firmware. Test Case: See below. Regression Potential: Limited to specific hardware. --- Below are the steps to replicate the issue We are doing continuous BLE scanning and monitoring the advertisements from reference device. After long periods of capture (several hours), the radio stops capturing advertisements and won't start again until we power cycle the box or manually unload/load the module via modprobe This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+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 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
This bug was fixed in the package linux-firmware - 1.173.1 --- linux-firmware (1.173.1) bionic; urgency=medium * Redpine: BLE radio lost issue (LP: #1757443) - linux-firmware: rsi: update firmware images for Redpine 9113 chipset * Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement (LP: #1769980) - iwlwifi: add some new FW versions and update older ones - iwlwifi: update firmwares for 3160, 3168 and 7265 -- Seth Forshee Fri, 18 May 2018 13:09:45 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: New Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
This bug was fixed in the package linux-firmware - 1.157.19 --- linux-firmware (1.157.19) xenial; urgency=medium * Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement (LP: #1769980) - iwlwifi: add some new FW versions and update older ones - iwlwifi: update firmwares for 3160, 3168 and 7265 -- Seth Forshee Fri, 18 May 2018 14:03:25 -0500 ** Changed in: linux-firmware (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: New Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1769980] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: New Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1773392] Re: zfs hangs on mount/unmount
Little update here: I tried ubuntu server 16.04 with HWE (4.13.0-36-generic) and lxd 3.0 + zfs 0.7.5 (latest from bionic repo) - and it seems there is no such bug with 4.13 kernel. After that I updated kernel (from bionic repo again - 4.15.0-22-generic) - and but appear again: zfs hangs if my lxd ct restarts (on mount again). So now I am kind of sure that it is kernel bug. Also I tried 4.16.12 from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.12/ Same behaviour - zfs hangs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773392 Title: zfs hangs on mount/unmount Status in linux package in Ubuntu: Confirmed Bug description: I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and 4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16; also tried 0.7.9). Sometimes lxd hangs when I try to stop / restart or "stop && move" some containers. Furhter investigation showed that problem is in zfs mount or unmount: it just hangs and lxd just wait it. Also commands like "zfs list" hangs to. It seems that it is not lxd or zfs issue, but kernel bug? https://github.com/lxc/lxd/issues/4104#issuecomment-392072939 I have one test ct that always hangs on restart, so here is info: dmesg: [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds. [ 1330.390994] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391101] txg_syncD0 9944 2 0x8000 [ 1330.391105] Call Trace: [ 1330.391117] __schedule+0x297/0x8b0 [ 1330.391122] schedule+0x2c/0x80 [ 1330.391136] cv_wait_common+0x11e/0x140 [spl] [ 1330.391141] ? wait_woken+0x80/0x80 [ 1330.391152] __cv_wait+0x15/0x20 [spl] [ 1330.391234] rrw_enter_write+0x3c/0xa0 [zfs] [ 1330.391306] rrw_enter+0x13/0x20 [zfs] [ 1330.391380] spa_sync+0x7c9/0xd80 [zfs] [ 1330.391457] txg_sync_thread+0x2cd/0x4a0 [zfs] [ 1330.391534] ? txg_quiesce_thread+0x3d0/0x3d0 [zfs] [ 1330.391543] thread_generic_wrapper+0x74/0x90 [spl] [ 1330.391549] kthread+0x121/0x140 [ 1330.391558] ? __thread_exit+0x20/0x20 [spl] [ 1330.391562] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391566] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391569] ret_from_fork+0x35/0x40 [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds. [ 1330.391630] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391735] lxd D0 12419 1 0x [ 1330.391739] Call Trace: [ 1330.391745] __schedule+0x297/0x8b0 [ 1330.391749] schedule+0x2c/0x80 [ 1330.391752] rwsem_down_write_failed+0x162/0x360 [ 1330.391808] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 1330.391814] call_rwsem_down_write_failed+0x17/0x30 [ 1330.391817] ? call_rwsem_down_write_failed+0x17/0x30 [ 1330.391821] down_write+0x2d/0x40 [ 1330.391825] grab_super+0x30/0x90 [ 1330.391901] ? zpl_create+0x160/0x160 [zfs] [ 1330.391905] sget_userns+0x91/0x490 [ 1330.391908] ? get_anon_bdev+0x100/0x100 [ 1330.391983] ? zpl_create+0x160/0x160 [zfs] [ 1330.391987] sget+0x7d/0xa0 [ 1330.391990] ? get_anon_bdev+0x100/0x100 [ 1330.392066] zpl_mount+0xa8/0x160 [zfs] [ 1330.392071] mount_fs+0x37/0x150 [ 1330.392077] vfs_kern_mount.part.23+0x5d/0x110 [ 1330.392080] do_mount+0x5ed/0xce0 [ 1330.392083] ? copy_mount_options+0x2c/0x220 [ 1330.392086] SyS_mount+0x98/0xe0 [ 1330.392092] do_syscall_64+0x73/0x130 [ 1330.392096] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 1330.392099] RIP: 0033:0x4db36a [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 00a5 [ 1330.392104] RAX: ffda RBX: RCX: 004db36a [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 00c420a23b60 [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: [ 1330.392110] R10: R11: 0216 R12: [ 1330.392112] R13: 0039 R14: 0038 R15: 0080 [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds. [ 1330.392171] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.392276] lxd D0 16725 1 0x0002 [ 1330.392279] Call Trace: [ 1330.392284] __schedule+0x297/0x8b0 [ 1330.392289] ? irq_work_queue+0x8d/0xa0 [ 1330.392293] schedule+0x2c/0x80 [ 1330.392297] io_schedule+0x16/0x40 [ 1330.392302] wait_on_page_bit_common+0xd8/0x160 [ 1330.392305] ? page_cache_tree_insert+0xe0/0xe0 [ 1330.39230
[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
can confirm after updating ubuntu Xenial and removing nomodeset from
boot options, everything seems to work again :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764194
Title:
Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
black screen at boot. Specifying 'nomodeset' on the kernel command line works
around the problem.
Intel resolved the problem in upstream commit a3520b8992e5. This commit
is now in mainline as of 4.17.rc2. It has also been cc'd to upstream
stable.
== Fix ==
a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child
devices")
== Regression Potential ==
Low. This commit was also cc'd to upstream stable, so it recieved
additional upstream review.
Description:Ubuntu 16.04.4 LTS
Release:16.04
Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
laptops, originally running BIOS version 1.0.8. The install media and
the installed OS was running linux-generic-hwe kernel 4.13.0.
After upgrading BIOS to latest version 1.1.9, the kernel no longer
boots: right after loading the i915 drm driver, the screen goes black,
and the machine can only be reset or power cycled. This is true for
both the installation media, and the OS instance previously installed
to the disk and updated to the latest hwe kernel 4.13.0-38.
Specifying 'nomodeset' on the kernel command line works around the
problem by disabling the i915 drm driver functionality. In that case,
several display driver function are obviously missing (eg GLX &
xrandr).
The problem manifested itself even when using the drm upstream latest
git-head version. A custom built kernel was used to provide logs for this
upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=105549
The upstream Intel developers provided a patch, which was successfully tested
by both the original reporter and me.
https://patchwork.freedesktop.org/patch/216371/
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde
I backported this fix to ubuntu-xenial hwe git-head, and tested the
result successfully. I'd like this fix to be added to the ubuntu-
xenial linux-generic-hwe kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764194/+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 1773400] Re: Redpine: wifi-ap stopped working after restart
** Description changed: SRU Justification: -- Impact: - Wi-Fi access point isn’t visible to outside devices after reboot + Wi-Fi access point isn’t visible to outside devices after reboot Test Case: - Configure Wi-Fi AP using setup wizard: -$ sudo wifi-ap.setup-wizard + Configure Wi-Fi AP using setup wizard: + $ sudo wifi-ap.setup-wizard - Check configured AP settings: -$ sudo wifi-ap.config get + Check configured AP settings: + $ sudo wifi-ap.config get -debug: false -dhcp.lease-time: 12h -dhcp.range-start: 10.0.60.2 -dhcp.range-stop: 10.0.60.200 -disabled: false -share.disabled: false -share.network-interface: wlan0 -wifi.address: 10.0.60.1 -wifi.channel: 6 -wifi.country-code: -wifi.hostapd-driver: nl80211 -wifi.interface: wlan0 -wifi.interface-mode: direct -wifi.netmask: ff00 -wifi.operation-mode: g -wifi.security: wpa2 -wifi.security-passphrase: some-password -wifi.ssid: dell-gateway + debug: false + dhcp.lease-time: 12h + dhcp.range-start: 10.0.60.2 + dhcp.range-stop: 10.0.60.200 + disabled: false + share.disabled: false + share.network-interface: wlan0 + wifi.address: 10.0.60.1 + wifi.channel: 6 + wifi.country-code: + wifi.hostapd-driver: nl80211 + wifi.interface: wlan0 + wifi.interface-mode: direct + wifi.netmask: ff00 + wifi.operation-mode: g + wifi.security: wpa2 + wifi.security-passphrase: some-password + wifi.ssid: dell-gateway - Restart AP and check its status: -$ sudo wifi-ap.status restart-ap + Restart AP and check its status: + $ sudo wifi-ap.status restart-ap - Check status of AP. It is showing true. -$ sudo wifi-ap.status -ap.active: true + Check status of AP. It is showing true. + $ sudo wifi-ap.status + ap.active: true - At this point, Wi-Fi access point is not visible. - + At this point, Wi-Fi access point is not visible. + Fix: - Power save is not enabled in AP mode and modified the same in source code. + Power save is not enabled in AP mode and modified the same in source code. Regression potential: - Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected. + Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected. + + This patch is for tracking only, please don't triage. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773400 Title: Redpine: wifi-ap stopped working after restart Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: -- Impact: Wi-Fi access point isn’t visible to outside devices after reboot Test Case: Configure Wi-Fi AP using setup wizard: $ sudo wifi-ap.setup-wizard Check configured AP settings: $ sudo wifi-ap.config get debug: false dhcp.lease-time: 12h dhcp.range-start: 10.0.60.2 dhcp.range-stop: 10.0.60.200 disabled: false share.disabled: false share.network-interface: wlan0 wifi.address: 10.0.60.1 wifi.channel: 6 wifi.country-code: wifi.hostapd-driver: nl80211 wifi.interface: wlan0 wifi.interface-mode: direct wifi.netmask: ff00 wifi.operation-mode: g wifi.security: wpa2 wifi.security-passphrase: some-password wifi.ssid: dell-gateway Restart AP and check its status: $ sudo wifi-ap.status restart-ap Check status of AP. It is showing true. $ sudo wifi-ap.status ap.active: true At this point, Wi-Fi access point is not visible. Fix: Power save is not enabled in AP mode and modified the same in source code. Regression potential: Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected. This patch is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1773410] Re: Redpine: Observed kernel panic while when running wireless tests in regression mode
** Description changed: SRU Justification - Impact: - Kernel freezes/panic when running wireless tests in regression + Kernel freezes/panic when running wireless tests in regression Test case: - 1. Keep a wrong access-point name in sta.conf file and run the nmcli. - 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. - 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed -a kernel panic. like below -[ 1171.913244] BUG: unable to handle page request at 001067e38 -[ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] -[ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] -[ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] -[ 1171.914098] process_one_work+0x142/0x3d0 -[ 1171.914111] worker_thread+0x229/0x440 -[ 1171.914122] kthread+0xf5/0x130 -[ 1171.914132] ? process_one_work+0x3d0/0x3d0 -[ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 -[ 1171.914152] ret_from_fork+0x35/0x40 - + 1. Keep a wrong access-point name in sta.conf file and run the nmcli. + 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. + 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed + a kernel panic. like below + [ 1171.913244] BUG: unable to handle page request at 001067e38 + [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] + [ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] + [ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] + [ 1171.914098] process_one_work+0x142/0x3d0 + [ 1171.914111] worker_thread+0x229/0x440 + [ 1171.914122] kthread+0xf5/0x130 + [ 1171.914132] ? process_one_work+0x3d0/0x3d0 + [ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 + [ 1171.914152] ret_from_fork+0x35/0x40 + Fix: - scan work function keeps running even after cancel_hw_scan() call. - Issue is resolved by calling cancel_work_sync(). + scan work function keeps running even after cancel_hw_scan() call. + Issue is resolved by calling cancel_work_sync(). Regression potential: - Ran driver_crash.sh for 100 times and didn't see the issue. + Ran driver_crash.sh for 100 times and didn't see the issue. + + This bug is for tracking purposes only, please don't triage. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773410 Title: Redpine: Observed kernel panic while when running wireless tests in regression mode Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification - Impact: Kernel freezes/panic when running wireless tests in regression Test case: 1. Keep a wrong access-point name in sta.conf file and run the nmcli. 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed a kernel panic. like below [ 1171.913244] BUG: unable to handle page request at 001067e38 [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 1171.914098] process_one_work+0x142/0x3d0 [ 1171.914111] worker_thread+0x229/0x440 [ 1171.914122] kthread+0xf5/0x130 [ 1171.914132] ? process_one_work+0x3d0/0x3d0 [ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 [ 1171.914152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync(). Regression potential: Ran driver_crash.sh for 100 times and didn't see the issue. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773410/+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 1770442] Re: Suspend does not connect network
Same as LP: #1752772? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770442 Title: Suspend does not connect network Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded ubuntu budgie 17.10 to 18.04, when suspending the OS when returning does not reconnect with the network. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu May 10 13:21:08 2018 InstallationDate: Installed on 2018-01-03 (127 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) 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/1770442/+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 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended
I can confirm that the PCI device no longer gets put to D3cold. ** Tags removed: verification-needed-artful verification-needed-bionic ** Tags added: verification-done-artful 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/1764684 Title: Fix an issue that some PCI devices get incorrectly suspended Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: ===SRU Justification=== [Impact] Some PCI device are not power managed by system firmware get runtime suspended incorrectly. In this case it's an xHC device, which can't be woken up by plugging USB device. [Test] With the patch, the xHC no longer get put to suspend incorrectly. USB devices can work on the xHC now. [Fix] We need to check if the device is power managed by system firmware, also if it supports PME from D3hot. [Regression Potential] Low. It fixes a regression caused by the PM core refactor. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1764684/+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 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended
fixed by oem kernel 4.13.0-1028.31 verified on BRMP-DVT2-C1H https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764684/comments/3 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1764684 Title: Fix an issue that some PCI devices get incorrectly suspended Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: ===SRU Justification=== [Impact] Some PCI device are not power managed by system firmware get runtime suspended incorrectly. In this case it's an xHC device, which can't be woken up by plugging USB device. [Test] With the patch, the xHC no longer get put to suspend incorrectly. USB devices can work on the xHC now. [Fix] We need to check if the device is power managed by system firmware, also if it supports PME from D3hot. [Regression Potential] Low. It fixes a regression caused by the PM core refactor. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1764684/+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 1772971] Re: linux-lts-trusty: 3.13.0-150.200~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772970 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 28. May 2018 10:05 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772970 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 28. May 2018 10:05 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1772971 Title: linux-lts-trusty: 3.13.0-150.200~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772970 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772971/+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 1655100] Re: NVME devices and Network devices disappears upon suspend
Please try the kernel: https://people.canonical.com/~khfeng/lp1655100-2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Won't Fix Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 25. May 2018 14:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773676] 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 1773676 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: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: Incomplete Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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 1773676] Re: Apport crashing on resume...
** Project changed: canonical-identity-provider => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773676 Title: Apport crashing on resume... Status in linux package in Ubuntu: New Bug description: When I attempt to "wake" / "resume" my laptop, I get a black screen instead of the login screen. I'm forced to do a hard reboot to get back into the system. When I reboot the system, it tells me there was an issue and give the following: /usr/share/apport/apportcheckresume Package linux-image-3.13.0-149-generic 3.13.0-149.199 Problem type kernelOoops ApportVersion 2.14.1-0ubuntu3.28 The issue only occurs when I allow the unit to sleep. I see in history where the system downloaded this package Wednesday 5.23.18 My system details: 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773676/+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
