[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
Please also try latest mainline build: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819028 Title: Intel 9260 WiFi adapter doesn't work on B450 motherboard Status in linux package in Ubuntu: Confirmed Bug description: Hi, I know this has been a well discussed issue on Linux forums, but I am having extreme issues maintaining the built-in Intel WiFi in my motherboard, it resets everytime I update my distros (Ubuntu 18.04 and Linux Mint Cinnamon 18.3). My best fix for it is following the guide at [https://askubuntu.com/questions/1038242/no-wifi-option-on- ubuntu-18-04-and-16-04]. I am wanting to know if there is a way to make this process more streamlined for users as this affects many and is a hassle to maintain properly. I know this has been addressed before with Ryzen CPUs but this shouldn't have to be necessary if the driver is baked into the kernel as this is quite frustrating for any user to go through, as it requires what is causing the problem to fix - a network connection. I don't mind if it's simpler to have a on/off feature like the Nvidia drivers have, as that is still a lot simpler than writing out a paragraphs of code. TL;DR I'm asking if changes could be added so that instead of needing a network connection (something that you can't have if the driver isn't built into/available through the distro) and writing a dissertation of code, they have a driver automatically work or a switch option like Broadcom and Nvidia have in this photo [https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] I was referred here by the Linux Mint forum, please refer to the page in case any questions have already been answered there [https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread] My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, Linux Mint 18.3/Ubuntu 18.04 dual boot. Thanks, Bionicle159 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2179 F pulseaudio /dev/snd/controlC1: amir 2179 F pulseaudio /dev/snd/controlC2: amir 2179 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b InstallationDate: Installed on 2018-08-22 (210 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Micro-Star International Co., Ltd. MS-7B85 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B85 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2179 F pulseaudio /dev/snd/controlC1: amir 2179 F pulseaudio /dev/snd/controlC2: amir 2179 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b InstallationDate: Installed on 2018-08-22 (210 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Micro-Star International Co., Ltd. MS-7B85 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOO
[Kernel-packages] [Bug 1820409] Re: Audio stutter after update
Please attach dmesg when this issue happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820409
Title:
Audio stutter after update
Status in linux package in Ubuntu:
Confirmed
Bug description:
After some update:
Audio stutters in VLC
Video and audio stutters in Youtube
I think cpu usage might be bigger in VLC too, over 20% vs. below 20%
earlier (one thread gets full 100%?)
Stuttering kernel at the moment is 4.15.0-46-generic.
Kernel version 4.15.0-43-generic definitely worked good.
Cant remember if i could get slight stutter from previous version version -45.
Tried also lowlatency and 4.18 kernel, bad stuttering in those.
(Distro is Lubuntu)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-46-generic 4.15.0-46.49
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-46-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: meie855 F pulseaudio
/dev/snd/controlC1: meie855 F pulseaudio
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50'
Mixer name : 'Intel Broadwell HDMI'
Components : 'HDA:80862808,80860101,0010'
Controls : 35
Simple ctrls : 5
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47'
Mixer name : 'Conexant CX20751/2'
Components : 'HDA:14f1510f,1043181d,00100100'
Controls : 20
Simple ctrls : 9
CurrentDesktop: LXDE
Date: Sat Mar 16 18:02:18 2019
InstallationDate: Installed on 2018-07-04 (255 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-46-generic N/A
linux-backports-modules-4.15.0-46-generic N/A
linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
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.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX305FA
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/1820409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814892] Re: [19.04 FEAT] qeth: Enhanced link speed - kernel part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814892 Title: [19.04 FEAT] qeth: Enhanced link speed - kernel part Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: Function: Provide enhanced link speed for OSA networks Business Case: Improved performance with OSA networks Available with kernel 4.20 Git-Commit: s390/qeth: report 25Gbit link speed [54e049c227] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821290] [NEW] Pop noise when headset is plugged in or removed from GHS/Line-out jack
Public bug reported: == SRU Justification == * Impact: There's unpleasant pop noise when headset is plugged in or removed from GHS/Line-out jack. * Fix: Issue can be fixed by these four patches. All of them are accepted by upstream. - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode for ALC225 - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225 - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB * Testcase: Connect/remove a headset to/from the jack and see if there's noise. * Risk of Regression: Low since these patches only affect specific platforms. ** Affects: hwe-next Importance: Undecided Assignee: Jesse Sung (wenchien) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: carson originate-from-1812330 ** Tags added: carson originate-from-1812330 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821290 Title: Pop noise when headset is plugged in or removed from GHS/Line-out jack Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: == SRU Justification == * Impact: There's unpleasant pop noise when headset is plugged in or removed from GHS/Line-out jack. * Fix: Issue can be fixed by these four patches. All of them are accepted by upstream. - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode for ALC225 - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225 - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB * Testcase: Connect/remove a headset to/from the jack and see if there's noise. * Risk of Regression: Low since these patches only affect specific platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1821290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack
The first two patches, 4d4b0c52 and d1dd4211, are in 5.0-rc2. The other two are in 5.1-rc1. ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821290 Title: Pop noise when headset is plugged in or removed from GHS/Line-out jack Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: == SRU Justification == * Impact: There's unpleasant pop noise when headset is plugged in or removed from GHS/Line-out jack. * Fix: Issue can be fixed by these four patches. All of them are accepted by upstream. - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode for ALC225 - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225 - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB * Testcase: Connect/remove a headset to/from the jack and see if there's noise. * Risk of Regression: Low since these patches only affect specific platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1821290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
[33031.949163] ath10k_pci :3a:00.0: Refused to change power state, currently in D3 [33032.529373] usb 1-3: reset full-speed USB device number 2 using xhci_hcd [33040.549168] usb 1-3: device descriptor read/64, error -71 [33045.220988] usb 1-3: device descriptor read/all, error -71 WiFi dies, Bluetooth follows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819727] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819727 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Tuesday, 12. March 2019 18:08 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
** Attachment added: "frozendmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248375/+files/frozendmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
It starts to happen more often. The symptom is a black screen with only "Started Bpfilter", a blinking cursor and a long waiting time, before showing the login screen. And I have a HiDPI Monitor, but i lowered the resolution to a normal one for 14". But if this problem happen, the monitor has the 2k resolution at login, while the login window itself has my lowered resolution. Meaning a little login screen attached to the left upper corner of the screen and the unused rest of the screen is just black. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 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:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
Thanks. It looks like the last kernel message is one from the Nvidia driver, but I can't tell if it's an error or just informational: [ 871.681257] NVRM: GPU at PCI::01:00: GPU-7eba71ac-fd71-c5c9-f569-09f6406e66c7 [ 871.681262] NVRM: GPU Board Serial Number: [ 871.681264] NVRM: Xid (PCI::01:00): 16, Head Count 8a93 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
Can you please check for crashes of gnome-shell or Xorg? https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pac
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
I have the test disabled on i386, so we can still run other tests without being interrupted. https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=47c843d9a608f212b9b1138b410151ae1e8f5b24 Will need to add this back after we got the fix applied. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Mach
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
Again, if you can still ssh in while the screen is frozen then please do so and run: journalctl -b0 > frozenjournal.txt and send us the file 'frozenjournal.txt' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
Passed with the proposed Bionic kernel - 4.15.0-47.50 selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 0.553(est) 0.89(act) [OK] Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 ok 1..7 selftests: raw_skew [PASS] ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [impact] autopkgtest failure during test for linux pkg. ADJ_OFFSET during test causes skew, and test to fail. [test case] this only happens intermittently, but frequently on the autopkgtests. when it happens it looks like: 20:46:54 DEBUG| [stdout] WARNING: ADJ_OFFSET in progress, this will cause inaccurate results 20:48:54 DEBUG| [stdout] Estimating clock drift: 16.881(est) 27.184(act) [FAILED] when it happens with a patched kernel it looks like: 01:04:35 DEBUG| [stdout] WARNING: ADJ_OFFSET in progress, this will cause inaccurate results 01:06:35 DEBUG| [stdout] Estimating clock drift: 14.52(est) 13.641(act) [OK] [regression potential] since this skips the test in question, it might miss an actual regression that the test should have caught; however, since ADJ_OFFSET is not always in progress during the test, if a real regression happens for this test, then it should correctly fail for test runs which have no concurrent ADJ_OFFSET and thus don't skip the test. [other info] original description: --- This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corpo
[Kernel-packages] [Bug 1819921] Re: [SRU] [B/OEM] Fix ACPI bug that causes boot failure
** Description changed: [Impact] - Some systems boot failed at a very early stage, only blackscreen shown. + Some lenovo laptops failed to boot at a very early stage, only blackscreen shown. [Fix] - Some system BIOS set definition in if statement, it would be deferred to be loaded. + Some system BIOS set definition in if statement, it would be deferred to + be loaded. Some devices would not work properly and cause a system lockup. - execute all acpi tables to make system work properly. + add a quirk for these laptops to execute all acpi tables and + make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] - Upstream fix. Low risk. - Backported changes is one line of debug ouput sentence in nsparse.c: - s/Start table execution pass/Start load pass/ + SAUCE patch. + Upstream fix: + + commit 5a8361f7ecceaed64b4064000d16cb703462be49 + Author: Schmauss, Erik + Date: Thu Feb 15 13:09:30 2018 -0800 + + ACPICA: Integrate package handling with module-level code + + Due to the lots of changes in this commit and other regressions concern + So made a sauce patch in Bionic kernel with the specific BIOS series. Verified on several laptops. Fix boot failure and no regression found. - This patch is from 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. + The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need + it. ** Description changed: [Impact] Some lenovo laptops failed to boot at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. add a quirk for these laptops to execute all acpi tables and make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] - SAUCE patch. + SAUCE patch.Low, specific changes depends on hardware. Upstream fix: commit 5a8361f7ecceaed64b4064000d16cb703462be49 Author: Schmauss, Erik Date: Thu Feb 15 13:09:30 2018 -0800 - ACPICA: Integrate package handling with module-level code + ACPICA: Integrate package handling with module-level code Due to the lots of changes in this commit and other regressions concern So made a sauce patch in Bionic kernel with the specific BIOS series. Verified on several laptops. Fix boot failure and no regression found. The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some lenovo laptops failed to boot at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. add a quirk for these laptops to execute all acpi tables and make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] SAUCE patch.Low, specific changes depends on hardware. Upstream fix: commit 5a8361f7ecceaed64b4064000d16cb703462be49 Author: Schmauss, Erik Date: Thu Feb 15 13:09:30 2018 -0800 ACPICA: Integrate package handling with module-level code Due to the lots of changes in this commit and other regressions concern So made a sauce patch in Bionic kernel with the specific BIOS series. Verified on several laptops. Fix boot failure and no regression found. The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
The directory /var/crash is empty. ** Attachment added: "frozenjournal.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248393/+files/frozenjournal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 1820988] Re: Please enable the config for ftrace on T-ARM64
It looks like ARM64 in Trusty does not have the Function Tracer support: phlin@tangerine:~/ubuntu-trusty$ git grep "ifdef CONFIG_FUNCTION_TRACER" Makefile:ifdef CONFIG_FUNCTION_TRACER arch/arm/include/asm/ftrace.h:#ifdef CONFIG_FUNCTION_TRACER arch/arm/kernel/Makefile:ifdef CONFIG_FUNCTION_TRACER arch/arm/kernel/armksyms.c:#ifdef CONFIG_FUNCTION_TRACER arch/arm/kernel/entry-common.S:#ifdef CONFIG_FUNCTION_TRACER arch/blackfin/kernel/bfin_ksyms.c:#ifdef CONFIG_FUNCTION_TRACER arch/ia64/include/asm/ftrace.h:#ifdef CONFIG_FUNCTION_TRACER arch/ia64/kernel/entry.S:#ifdef CONFIG_FUNCTION_TRACER arch/ia64/kernel/ia64_ksyms.c:#ifdef CONFIG_FUNCTION_TRACER arch/metag/include/asm/ftrace.h:#ifdef CONFIG_FUNCTION_TRACER ... phlin@tangerine:~/ubuntu-trusty/arch/arm64$ grep -r HAVE_FUNCTION_TRACER * phlin@tangerine:~/ubuntu-trusty/arch/arm64$ I will just disable the test for Trusty ARM64. ** Summary changed: - Please enable the config for ftrace on T-ARM64 + Please enable the config for ftrace on T-ARM64 (ubuntu_ftrace_smoke_test failed) ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Confirmed => Won't Fix ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820988 Title: Please enable the config for ftrace on T-ARM64 (ubuntu_ftrace_smoke_test failed) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Bug description: The ubuntu_ftrace_smoke_test is failing on Trusty ARM64. It looks like it will need the following configs for get it work: CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y CONFIG_STACK_TRACER=y CONFIG_DYNAMIC_FTRACE=y ftrace is useful for debugging. We should enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-167-generic 3.13.0-167.217 ProcVersionSignature: User Name 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Mar 20 10:14:53 2019 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp1s0d1 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-167-generic N/A linux-backports-modules-3.13.0-167-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1820988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard
I'm not sure how Linux Mint will react to that, I'll try it on the Ubuntu partition. On Fri, 22 Mar 2019, 7:20 am Kai-Heng Feng, wrote: > Please also try latest mainline build: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc1/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819028 > > Title: > Intel 9260 WiFi adapter doesn't work on B450 motherboard > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, I know this has been a well discussed issue on Linux forums, but I > am having extreme issues maintaining the built-in Intel WiFi in my > motherboard, it resets everytime I update my distros (Ubuntu 18.04 and > Linux Mint Cinnamon 18.3). My best fix for it is following the guide > at [https://askubuntu.com/questions/1038242/no-wifi-option-on- > ubuntu-18-04-and-16-04]. > > I am wanting to know if there is a way to make this process more > streamlined for users as this affects many and is a hassle to maintain > properly. I know this has been addressed before with Ryzen CPUs but this > shouldn't have to be necessary if the driver is baked into the kernel as > this is quite frustrating for any user to go through, as it requires what > is causing the problem to fix - a network connection. I don't mind if it's > simpler to have a on/off feature like the Nvidia drivers have, as that is > still a lot simpler than writing out a paragraphs of code. > > TL;DR I'm asking if changes could be added so that instead of needing a > network connection (something that you can't have if the driver isn't built > into/available through the distro) and writing a dissertation of code, they > have a driver automatically work or a switch option like Broadcom and > Nvidia have in this photo [ > https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png] > > I was referred here by the Linux Mint forum, please refer to the page > in case any questions have already been answered there > [ > https://forums.linuxmint.com/viewtopic.php?f=49&t=289358&e=1&view=unread#unread > ] > > My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi, > Linux Mint 18.3/Ubuntu 18.04 dual boot. > > Thanks, Bionicle159 > --- > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: amir 2179 F pulseaudio >/dev/snd/controlC1: amir 2179 F pulseaudio >/dev/snd/controlC2: amir 2179 F pulseaudio > CurrentDesktop: X-Cinnamon > DistroRelease: Linux 18.3 > HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b > InstallationDate: Installed on 2018-08-22 (210 days ago) > InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 > MachineType: Micro-Star International Co., Ltd. MS-7B85 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > Package: linux (not installed) > ProcFB: 0 VESA VGA > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic > root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 > RelatedPackageVersions: >linux-restricted-modules-4.15.0-45-generic N/A >linux-backports-modules-4.15.0-45-generic N/A >linux-firmware 1.157.21 > Tags: sylvia > Uname: Linux 4.15.0-45-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 08/06/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1.10 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85) > dmi.board.vendor: Micro-Star International Co., Ltd. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Micro-Star International Co., Ltd. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7B85 > dmi.product.version: 1.0 > dmi.sys.vendor: Micro-Star International Co., Ltd. > --- > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: amir 2179 F pulseaudio >/dev/snd/controlC1: amir 2179 F pulseaudio >/dev/snd/controlC2: amir 2179 F pulseaudio > CurrentDesktop: X-Cinnamon > DistroRelease: Linux 18.3 > HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b > InstallationDate: Installed on 2018-08-22 (210
[Kernel-packages] [Bug 1820988] Re: Please enable the config for ftrace on T-ARM64 (ubuntu_ftrace_smoke_test failed)
The ARM64 ftrace support was added in upstream commit 819e50e2 (arm64: Add ftrace support) A quick cherry-pick attempt shows that this will need some backport work in arch/arm64/Kconfig file. (Not sure if there will be more commits to pull) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820988 Title: Please enable the config for ftrace on T-ARM64 (ubuntu_ftrace_smoke_test failed) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Bug description: The ubuntu_ftrace_smoke_test is failing on Trusty ARM64. It looks like it will need the following configs for get it work: CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y CONFIG_STACK_TRACER=y CONFIG_DYNAMIC_FTRACE=y ftrace is useful for debugging. We should enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-167-generic 3.13.0-167.217 ProcVersionSignature: User Name 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Mar 20 10:14:53 2019 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp1s0d1 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-167-generic N/A linux-backports-modules-3.13.0-167-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1820988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Spot on, please test this kernel: https://people.canonical.com/~khfeng/lp1811755/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are identical, then only one drive can be seen. NQN is supposed to be unique but some Intel drives do not follow that. [Fix] The device-supplied subnqn is ignored and one will be generated as if the field is empty. The upstream patch conflicts with a value in 'enum nvme_quirks' that we added in a SAUCE patch, changed that from (1<<8) to (1<<15). [Test] With this fix, both drives can be seen. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. - I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248416/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchp
[Kernel-packages] [Bug 1821194] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248418/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1821194] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248421/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1821194] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248417/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1821194] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248419/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launc
[Kernel-packages] [Bug 1821194] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248422/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1821194] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248420/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launc
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 3364 F pulseaudio /dev/snd/controlC0: u 3364 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-gambit-eagle-kylin+X45 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Inspiron 3670 NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-graphics-drivers-410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1029-oem.efi.signed root=UUID=baab0cd6-ff41-4a5b-93a0-c52386e24070 ro mem_sleep_default=deep quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1029.34-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1029-oem N/A linux-backports-modules-4.15.0-1029-oem N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-1029-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.2:bd03/04/2019:svnDellInc.:pnInspiron3670:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3670 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18
[Kernel-packages] [Bug 1821194] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248415/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1821305] [NEW] csiostor and cxgb4 fight for the NIC
Public bug reported: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821305 Title: csiostor and cxgb4 fight for the NIC Status in linux package in Ubuntu: New Bug description: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supe
[Kernel-packages] [Bug 1821194] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248427/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1821194] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248424/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-p
[Kernel-packages] [Bug 1821194] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248432/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Just found that this issue for autotest-client-tests has already been addressed in https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=e8225af0687c7cb804458fa6cd03956739f24d39 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 m
[Kernel-packages] [Bug 1821194] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248431/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.lau
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
Have you ever seen this issue under Arftul? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248430/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.lau
[Kernel-packages] [Bug 1821194] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248429/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@li
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Just found that this issue for autotest-client-tests has already been addressed in 3c2347e74, so we're good, previous commit reverted. https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=e8225af0687c7cb804458fa6cd03956739f24d39 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell In
[Kernel-packages] [Bug 1821305] 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/1821305 Title: csiostor and cxgb4 fight for the NIC Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
I'm really not sure what's going on there. There's no evidence of a crash and if there is a hang then this looks like the last things gnome- shell said: Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: g_array_unref: assertion 'array' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: g_array_unref: assertion 'array' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: g_array_unref: assertion 'array' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:03 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:11 u-Inspiron-3670 kernel: NVRM: GPU at PCI::01:00: GPU-7eba71ac-fd71-c5c9-f569-09f6406e66c7 Mar 22 04:07:11 u-Inspiron-3670 kernel: NVRM: GPU Board Serial Number: Mar 22 04:07:11 u-Inspiron-3670 kernel: NVRM: Xid (PCI::01:00): 16, Head Count 8a93 Mar 22 04:07:11 u-Inspiron-3670 gnome-shell[1577]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Mar 22 04:07:11 u-Inspiron-3670 gnome-shell[1577]: JS ERROR: TypeError: device is null _init/<@resource:///org/gnome/shell/ui/keyboard.js:518:1 It's slightly interesting the kernel message from Nvidia is in the middle. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => New ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue i
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
It does not work for me with Kernel 5.0.2 generic under ubuntu 18.04. I don't see why this should be closed when the bios clearly does not fix it for all users -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820988] Re: ubuntu_ftrace_smoke_test failed on T-ARM64 due to no FUNCTION_TRACER support
Test disabled for T-ARM64 https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=d7e11e51c0bb04ca2fb124a051fc5031a70959d5 We can re-enable it if we decided to pull the function tracer support to the Trusty ARM64 kernel. ** Summary changed: - Please enable the config for ftrace on T-ARM64 (ubuntu_ftrace_smoke_test failed) + ubuntu_ftrace_smoke_test failed on T-ARM64 due to no FUNCTION_TRACER support ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820988 Title: ubuntu_ftrace_smoke_test failed on T-ARM64 due to no FUNCTION_TRACER support Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Bug description: The ubuntu_ftrace_smoke_test is failing on Trusty ARM64. It looks like it will need the following configs for get it work: CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y CONFIG_STACK_TRACER=y CONFIG_DYNAMIC_FTRACE=y ftrace is useful for debugging. We should enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-167-generic 3.13.0-167.217 ProcVersionSignature: User Name 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Mar 20 10:14:53 2019 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp1s0d1 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-167-generic N/A linux-backports-modules-3.13.0-167-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1820988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : http
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
Please test: https://people.canonical.com/~khfeng/lp1813537/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] 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 1821194 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 nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
Hi, Gustavo. Yes, we are keeping the filename as upstream, with a dash. Can you try the kernel at ppa:cascardo/linux, and see if that works for you? Best regards. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260 on kernel 4.15
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809483 Title: iwlwifi not working with Intel AC 9260 on kernel 4.15 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [ 22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324 [ 22.208574] [ cut here ] [ 22.208575] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425! [ 22.208578] invalid opcode: [#1] SMP NOPTI [ 22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass uvcvideo mxm_wmi intel_wmi_thunderb olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) aesni_intel aes_x86_64 crypto_simd [ 22.208598] cryptd glue_helper drm_kms_helper syscopyarea sysfillrect input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci ipmi_msghandler video mac_hid [ 22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P OE 4.15.0-43-generic #46-Ubuntu [ 22.208605] Hardware name: Notebook P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018 [ 22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] [ 22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286 [ 22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: e4b2e1c6ab60 [ 22.208612] RDX: 99b9b38b61a8 RSI: RDI: 99b9b8280078 [ 22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 007690c8 [ 22.208614] R10: R11: 99b9b8280050 R12: 99b9b828 [ 22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 99b9b38b61d0 [ 22.208615] FS: 7fb8c9ec9540() GS:99b9be30() knlGS: [ 22.208616] CS: 0010 DS: ES: CR0: 80050033 [ 22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 003606e0 [ 22.208618] DR0: DR1: DR2: [ 22.208619] DR3: DR6: fffe0ff0 DR7: 0400 [ 22.208619] Call Trace: [ 22.208623] _iwl_pcie_rx_init+0x252/0x710 [iwlwifi] [ 22.208626] iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi] [ 22.208631] ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm] [ 22.208635] iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi] [ 22.208639] iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm] [ 22.208640] ? 0xc198e000 [ 22.208644] iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208647] ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208650] ? iwl_wait_init_complete+0x20/0x20 [iwlmvm] [ 22.208654] iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208657] ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208660] _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi] [ 22.208663] iwl_opmode_register+0x75/0xe0 [iwlwifi] [ 22.208664] ? 0xc19e8000 [ 22.208668] iwl_mvm_init+0x38/0x1000 [iwlmvm] [ 22.208671] do_one_initcall+0x52/0x19f [ 22.208672] ? _cond_resched+0x19/0x40 [ 22.208674] ? kmem_cache_alloc_trace+0xa6/0x1b0 [ 22.208676] ? do_init_module+0x27/0x209 [ 22.208678] do_init_module+0x5f/0x209 [ 22.208679] load_module+0x191e/0x1f10 [ 22.208681] ? ima_post_read_file+0x96/0xa0 [ 22.208682] SYSC_finit_module+0xfc/0x120 [ 22.208683] ? SYSC_finit_module+0xfc/0x120 [ 22.208685] SyS_finit_module+0xe/0x10 [ 22.208686] do_syscall_64+0x73/0x130 [ 22.208688] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 22.208689] RIP: 0033:0x7fb8c99ef839 [ 22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 0139 [ 22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 7fb8c99ef839 [ 22.208691] RDX: RSI: 55c40c09cd2e RDI: 0001 [ 22.208692] RBP:
[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake
Can you provide instructions how to install? (I don't want to mess anything up) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813537 Title: Wifi + bluetooth adapters are gone after sleep/wake Status in linux package in Ubuntu: Confirmed Bug description: the only fix I found was to power down and power back on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uri2238 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 11:15:43 2019 HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5 InstallationDate: Installed on 2018-01-13 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802283] Re: system freezes
After a long time of no system freeze it happened again a few minutes ago: I'm not sure whether this is the same symptom as with the crashes before. I could reboot using the MagicSysRq keys. ar 22 11:33:25 x1cbn systemd-timesyncd[1035]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Mar 22 11:36:11 x1cbn org.gnome.Shell.desktop[2055]: libinput error: event6 - Synaptics TM3288-011: kernel bug: Touch jump detected and discarded. Mar 22 11:36:11 x1cbn org.gnome.Shell.desktop[2055]: See https://wayland.freedesktop.org/libinput/doc/1.12.1/touchpad-jumping-cursors.html for details Mar 22 11:36:13 x1cbn org.gnome.Shell.desktop[2055]: libinput error: event6 - Synaptics TM3288-011: kernel bug: Touch jump detected and discarded. Mar 22 11:36:13 x1cbn org.gnome.Shell.desktop[2055]: See https://wayland.freedesktop.org/libinput/doc/1.12.1/touchpad-jumping-cursors.html for details Mar 22 11:37:25 x1cbn pulseaudio[2100]: W: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP and XRUN: Datenübergabe unterbrochen (broken pipe) Mar 22 11:37:25 x1cbn kernel: [58375.090461] usb 5-1.4: cannot submit urb (err = -27) Mar 22 11:37:25 x1cbn kernel: [58375.090609] usb 5-1.4: cannot submit urb 0, error -27: internal error Mar 22 11:38:08 x1cbn firefox.desktop[2055]: IPDL protocol Error: Received an invalid file descriptor Mar 22 11:38:27 x1cbn org.gnome.Shell.desktop[2055]: Window manager warning: last_user_time (58437907) is greater than comparison timestamp (58437769). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 22 11:38:27 x1cbn org.gnome.Shell.desktop[2055]: Window manager warning: 0x183 (Benutzer ä) appears to be one of the offending windows with a timestamp of 58437907. Working around... Mar 22 11:39:20 x1cbn org.gnome.Shell.desktop[2055]: libinput error: client bug: timer event6 keyboard: offset negative (-2799ms) Mar 22 11:39:31 x1cbn kernel: [58501.502853] sysrq: SysRq : Keyboard mode set to system default Mar 22 11:39:31 x1cbn kernel: [58501.690698] sysrq: SysRq : Terminate All Tasks Mar 22 11:39:31 x1cbn kernel: [58501.690960] systemd-journald[498]: Received SIGTERM. ** Changed in: linux (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802283 Title: system freezes Status in linux package in Ubuntu: New Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 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:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810377] Re: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B
*** This bug is a duplicate of bug 1810376 *** https://bugs.launchpad.net/bugs/1810376 ** This bug has been marked a duplicate of bug 1810376 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810377 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1810376] Re: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B
** No longer affects: 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/1810376 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: Fix Released Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1821194/+subscriptions -- Mailing
[Kernel-packages] [Bug 1802283] 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/1802283 Title: system freezes Status in linux package in Ubuntu: Confirmed Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 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:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821317] [NEW] 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Public bug reported: I think this is identical to bug 1812845 Run 5fbc7c59fd22c5a6531b40b0759624b680a95e52 test in ubuntu_btrfs_kernel_fixes on an i386 system will make the SUT hang. This test will: 1. Create a 5-disk RAID5 2. Corrupt one of the device 3. Mount the FS as degraded 4. run btrfs scrub In bug 1812845 it just skipped step 2 and 3, and Andrea's patch states that this is caused by finish_parity_scrub(), so I think they're the same. If that's the case we should disable this test for now. This is the last thing we can see from the syslog: Mar 22 10:45:14 onza kernel: [12628.790147] Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Mar 22 10:45:15 onza kernel: [12629.635268] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 1 transid 5 /dev/loop0 Mar 22 10:45:15 onza kernel: [12629.759316] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 2 transid 5 /dev/loop1 Mar 22 10:45:15 onza kernel: [12629.902400] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 3 transid 5 /dev/loop2 Mar 22 10:45:15 onza kernel: [12630.031103] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 4 transid 5 /dev/loop3 Mar 22 10:45:15 onza kernel: [12630.202480] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 5 transid 5 /dev/loop4 Mar 22 10:45:16 onza kernel: [12631.419614] BTRFS info (device loop4): allowing degraded mounts Mar 22 10:45:16 onza kernel: [12631.419619] BTRFS info (device loop4): disk space caching is enabled Mar 22 10:45:16 onza kernel: [12631.419622] BTRFS info (device loop4): has skinny extents Mar 22 10:45:16 onza kernel: [12631.419624] BTRFS info (device loop4): flagging fs with big metadata feature Mar 22 10:45:16 onza kernel: [12631.420993] BTRFS warning (device loop4): devid 2 uuid f81e256a-ab46-4948-aa3d-3e8d0234fa9b is missing Mar 22 10:45:16 onza kernel: [12631.421888] BTRFS info (device loop4): creating UUID tree Mar 22 10:45:17 onza kernel: [12631.574478] [ cut here ] Mar 22 10:45:17 onza kernel: [12631.574482] kernel BUG at /build/linux-qJwW2z/linux-4.15.0/mm/highmem.c:350! Mar 22 10:45:17 onza kernel: [12631.630790] invalid opcode: [#1] SMP Mar 22 10:45:18 onza kernel: [12631.662771] Modules linked in: btrfs zstd_compress gpio_ich intel_powerclamp coretemp kvm_intel dcdbas kvm ipmi_ssif irqbypass input_leds joydev intel_cstate i7core_edac ipmi_si ipmi_devintf lpc_ich acpi_power_meter ipmi_msghandler shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect sysimgblt fb_sys_fops usbhid hid mpt3sas drm pata_acpi bnx2 raid_class scsi_transport_sas wmi [last unloaded: zstd_compress] Mar 22 10:45:18 onza kernel: [12632.153647] CPU: 1 PID: 3852 Comm: kworker/u16:4 Not tainted 4.15.0-46-generic #49-Ubuntu Mar 22 10:45:18 onza kernel: [12632.219025] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Mar 22 10:45:18 onza kernel: [12632.279533] Workqueue: btrfs-rmw btrfs_rmw_helper [btrfs] Mar 22 10:45:18 onza kernel: [12632.322819] EIP: kunmap_high+0xaa/0xb0 Mar 22 10:45:18 onza kernel: [12632.352697] EFLAGS: 00010246 CPU: 1 Mar 22 10:45:18 onza kernel: [12632.380572] EAX: 0028 EBX: f000 ECX: 0001 EDX: Mar 22 10:45:18 onza kernel: [12632.430629] ESI: 0005 EDI: EBP: d3669e50 ESP: d3669e4c Mar 22 10:45:18 onza kernel: [12632.480686] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Mar 22 10:45:18 onza kernel: [12632.523881] CR0: 80050033 CR2: b542effc CR3: 17e16000 CR4: 06f0 Mar 22 10:45:18 onza kernel: [12632.573938] Call Trace: Mar 22 10:45:18 onza kernel: [12632.593428] kunmap+0x3e/0x50 Mar 22 10:45:18 onza kernel: [12632.617106] finish_parity_scrub+0x24d/0x570 [btrfs] Mar 22 10:45:18 onza kernel: [12632.656764] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] Mar 22 10:45:18 onza kernel: [12632.702800] scrub_parity_work+0x24a/0x260 [btrfs] Mar 22 10:45:18 onza kernel: [12632.741072] normal_work_helper+0x7d/0x2f0 [btrfs] Mar 22 10:45:18 onza kernel: [12632.779343] btrfs_rmw_helper+0x10/0x20 [btrfs] Mar 22 10:45:18 onza kernel: [12632.815498] process_one_work+0x1b9/0x3d0 Mar 22 10:45:18 onza kernel: [12632.847459] worker_thread+0x37/0x420 Mar 22 10:45:18 onza kernel: [12632.876717] kthread+0xf0/0x110 Mar 22 10:45:18 onza kernel: [12632.901744] ? process_one_work+0x3d0/0x3d0 Mar 22 10:45:18 onza kernel: [12632.935164] ? kthread_create_worker_on_cpu+0x20/0x20 Mar 22 10:45:18 onza kernel: [12632.975448] ret_from_fork+0x2e/0x38 Mar 22 10:45:18 onza kernel: [12633.004009] Code: 2c ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 a0 d1 c4 d7 31 c9 3d a0 d1 c4 d7 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66
[Kernel-packages] [Bug 1821317] Re: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on X/B i386
Test passed on: T-AMD64 / T-i386 / T-ARM64 / T-P8 X-AMD64 / X-ARM64 / X-P8 / X-s390x B-ARM64 / B-ARM64 / B-P8 (B-amd64 was not tested yet) C-i386 / C-ARM64 / C-P8 (C-amd64 was not tested yet) D-i386 / D-ARM64 / D-P8 (D-amd64 was not tested yet) Failed on X-i386 B-i386 ** Summary changed: - 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on i386 + 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on X/B i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821317 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on X/B i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: I think this is identical to bug 1812845 Run 5fbc7c59fd22c5a6531b40b0759624b680a95e52 test in ubuntu_btrfs_kernel_fixes on an i386 system will make the SUT hang. This test will: 1. Create a 5-disk RAID5 2. Corrupt one of the device 3. Mount the FS as degraded 4. run btrfs scrub In bug 1812845 it just skipped step 2 and 3, and Andrea's patch states that this is caused by finish_parity_scrub(), so I think they're the same. If that's the case we should disable this test for now. This is the last thing we can see from the syslog: Mar 22 10:45:14 onza kernel: [12628.790147] Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Mar 22 10:45:15 onza kernel: [12629.635268] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 1 transid 5 /dev/loop0 Mar 22 10:45:15 onza kernel: [12629.759316] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 2 transid 5 /dev/loop1 Mar 22 10:45:15 onza kernel: [12629.902400] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 3 transid 5 /dev/loop2 Mar 22 10:45:15 onza kernel: [12630.031103] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 4 transid 5 /dev/loop3 Mar 22 10:45:15 onza kernel: [12630.202480] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 5 transid 5 /dev/loop4 Mar 22 10:45:16 onza kernel: [12631.419614] BTRFS info (device loop4): allowing degraded mounts Mar 22 10:45:16 onza kernel: [12631.419619] BTRFS info (device loop4): disk space caching is enabled Mar 22 10:45:16 onza kernel: [12631.419622] BTRFS info (device loop4): has skinny extents Mar 22 10:45:16 onza kernel: [12631.419624] BTRFS info (device loop4): flagging fs with big metadata feature Mar 22 10:45:16 onza kernel: [12631.420993] BTRFS warning (device loop4): devid 2 uuid f81e256a-ab46-4948-aa3d-3e8d0234fa9b is missing Mar 22 10:45:16 onza kernel: [12631.421888] BTRFS info (device loop4): creating UUID tree Mar 22 10:45:17 onza kernel: [12631.574478] [ cut here ] Mar 22 10:45:17 onza kernel: [12631.574482] kernel BUG at /build/linux-qJwW2z/linux-4.15.0/mm/highmem.c:350! Mar 22 10:45:17 onza kernel: [12631.630790] invalid opcode: [#1] SMP Mar 22 10:45:18 onza kernel: [12631.662771] Modules linked in: btrfs zstd_compress gpio_ich intel_powerclamp coretemp kvm_intel dcdbas kvm ipmi_ssif irqbypass input_leds joydev intel_cstate i7core_edac ipmi_si ipmi_devintf lpc_ich acpi_power_meter ipmi_msghandler shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect sysimgblt fb_sys_fops usbhid hid mpt3sas drm pata_acpi bnx2 raid_class scsi_transport_sas wmi [last unloaded: zstd_compress] Mar 22 10:45:18 onza kernel: [12632.153647] CPU: 1 PID: 3852 Comm: kworker/u16:4 Not tainted 4.15.0-46-generic #49-Ubuntu Mar 22 10:45:18 onza kernel: [12632.219025] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Mar 22 10:45:18 onza kernel: [12632.279533] Workqueue: btrfs-rmw btrfs_rmw_helper [btrfs] Mar 22 10:45:18 onza kernel: [12632.322819] EIP: kunmap_high+0xaa/0xb0 Mar 22 10:45:18 onza kernel: [12632.352697] EFLAGS: 00010246 CPU: 1 Mar 22 10:45:18 onza kernel: [12632.380572] EAX: 0028 EBX: f000 ECX: 0001 EDX: Mar 22 10:45:18 onza kernel: [12632.430629] ESI: 0005 EDI: EBP: d3669e50 ESP: d3669e4c Mar 22 10:45:18 onza kernel: [12632.480686] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Mar 22 10:45:18 onza kernel: [12632.523881] CR0: 80050033 CR2: b542effc CR3: 17e16000 CR4: 06f0 Mar 22 10:45:18 onza kernel: [12632.573938] Call Trace: Mar 22 10:45:18 onza kernel: [12632.593428] kunmap+0x3e/0x50 Mar 22 10:45:18 onza kernel: [12632.617106] finish_parity_scrub+0x24d/0x570 [btrfs] Mar 22 10:45:18 onza kernel: [12632.656764] v
[Kernel-packages] [Bug 1821317] 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/1821317 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in ubuntu_btrfs_kernel_fixes triggers system hang on X/B i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: I think this is identical to bug 1812845 Run 5fbc7c59fd22c5a6531b40b0759624b680a95e52 test in ubuntu_btrfs_kernel_fixes on an i386 system will make the SUT hang. This test will: 1. Create a 5-disk RAID5 2. Corrupt one of the device 3. Mount the FS as degraded 4. run btrfs scrub In bug 1812845 it just skipped step 2 and 3, and Andrea's patch states that this is caused by finish_parity_scrub(), so I think they're the same. If that's the case we should disable this test for now. This is the last thing we can see from the syslog: Mar 22 10:45:14 onza kernel: [12628.790147] Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Mar 22 10:45:15 onza kernel: [12629.635268] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 1 transid 5 /dev/loop0 Mar 22 10:45:15 onza kernel: [12629.759316] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 2 transid 5 /dev/loop1 Mar 22 10:45:15 onza kernel: [12629.902400] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 3 transid 5 /dev/loop2 Mar 22 10:45:15 onza kernel: [12630.031103] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 4 transid 5 /dev/loop3 Mar 22 10:45:15 onza kernel: [12630.202480] BTRFS: device fsid 7031ed1d-0a3e-41dd-8cca-348d4e8ab82a devid 5 transid 5 /dev/loop4 Mar 22 10:45:16 onza kernel: [12631.419614] BTRFS info (device loop4): allowing degraded mounts Mar 22 10:45:16 onza kernel: [12631.419619] BTRFS info (device loop4): disk space caching is enabled Mar 22 10:45:16 onza kernel: [12631.419622] BTRFS info (device loop4): has skinny extents Mar 22 10:45:16 onza kernel: [12631.419624] BTRFS info (device loop4): flagging fs with big metadata feature Mar 22 10:45:16 onza kernel: [12631.420993] BTRFS warning (device loop4): devid 2 uuid f81e256a-ab46-4948-aa3d-3e8d0234fa9b is missing Mar 22 10:45:16 onza kernel: [12631.421888] BTRFS info (device loop4): creating UUID tree Mar 22 10:45:17 onza kernel: [12631.574478] [ cut here ] Mar 22 10:45:17 onza kernel: [12631.574482] kernel BUG at /build/linux-qJwW2z/linux-4.15.0/mm/highmem.c:350! Mar 22 10:45:17 onza kernel: [12631.630790] invalid opcode: [#1] SMP Mar 22 10:45:18 onza kernel: [12631.662771] Modules linked in: btrfs zstd_compress gpio_ich intel_powerclamp coretemp kvm_intel dcdbas kvm ipmi_ssif irqbypass input_leds joydev intel_cstate i7core_edac ipmi_si ipmi_devintf lpc_ich acpi_power_meter ipmi_msghandler shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect sysimgblt fb_sys_fops usbhid hid mpt3sas drm pata_acpi bnx2 raid_class scsi_transport_sas wmi [last unloaded: zstd_compress] Mar 22 10:45:18 onza kernel: [12632.153647] CPU: 1 PID: 3852 Comm: kworker/u16:4 Not tainted 4.15.0-46-generic #49-Ubuntu Mar 22 10:45:18 onza kernel: [12632.219025] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Mar 22 10:45:18 onza kernel: [12632.279533] Workqueue: btrfs-rmw btrfs_rmw_helper [btrfs] Mar 22 10:45:18 onza kernel: [12632.322819] EIP: kunmap_high+0xaa/0xb0 Mar 22 10:45:18 onza kernel: [12632.352697] EFLAGS: 00010246 CPU: 1 Mar 22 10:45:18 onza kernel: [12632.380572] EAX: 0028 EBX: f000 ECX: 0001 EDX: Mar 22 10:45:18 onza kernel: [12632.430629] ESI: 0005 EDI: EBP: d3669e50 ESP: d3669e4c Mar 22 10:45:18 onza kernel: [12632.480686] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Mar 22 10:45:18 onza kernel: [12632.523881] CR0: 80050033 CR2: b542effc CR3: 17e16000 CR4: 06f0 Mar 22 10:45:18 onza kernel: [12632.573938] Call Trace: Mar 22 10:45:18 onza kernel: [12632.593428] kunmap+0x3e/0x50 Mar 22 10:45:18 onza kernel: [12632.617106] finish_parity_scrub+0x24d/0x570 [btrfs] Mar 22 10:45:18 onza kernel: [12632.656764] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] Mar 22 10:45:18 onza kernel: [12632.702800] scrub_parity_work+0x24a/0x260 [btrfs] Mar 22 10:45:18 onza kernel: [12632.741072] normal_work_helper+0x7d/0x2f0 [btrfs] Mar 22 10:45:18 onza kernel: [12632.779343] btrfs_rmw_helper+0x10/0x20 [btrfs] Mar 22 10:45:18 onza kernel: [12632.815498] process_one_work+0x1b9/0x3d0 Mar 22 10:45:18 onza
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
This was previously discovered as an alternative way to trigger bug 1804607, but re-filed as a new one for the different behaviour. By the way, bug 1817738 was once considered a potential root cause to it. However the proposed change prevents gnome-shell from starting up normally on systems with nvidia cards and installed nvidia-drivers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there sh
[Kernel-packages] [Bug 1389077] Re: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU
Happened to my Lenovo ThinkPad X220. Yesterday I was playing Factorio, with the laptop fan spinning full-throttle, and intel_powerclamp started idle injection, which, ok, fair enough. Factorio is very CPU hungry and this laptop model is like 6 years old. What is a problem is that today I'm not playing Factorio, the CPU temperature is at 45 degrees, the fan is idle, and yet powerclamp is still doing the idle injection schtick. Loadavg over 5, kinject_idle at 50-60% on all four threads (this is a dualcore system with hyperthreading), everything is painfully laggy. Rebooting fixed everything (until next time, I suppose). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389077 Title: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing minecraft with my daughter, I noticed the game was running very slowly. Even after closing the game, my web browsing slowed to a crawl. Looking at the processes in top, I noticed there were 4 tasks called kidle_inject running at 50% CPU each. After spending a long time figuring out what caused this, I found out this is caused by the Intel Powerclamp driver. I never did anything to enable this, and haven't observed this slowdown before the upgrade. I found the powerclamp driver in the /sys/class/thermal/cooling_device5 directory: root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type intel_powerclamp root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state -1 root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 50 I tried to echo 0 to cur_state, but it still reported -1 when I catted the value. There seems to be no obvious way to disable this, and this should not have been enabled in the first place. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bkat 2780 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 23:16:04 2014 HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993 InstallationDate: Installed on 2012-04-22 (925 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago) dmi.bios.date: 05/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.09 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU1284V1X dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389077] Re: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU
(Of course I forgot to mention the relevant bit: I'm on Ubuntu 18.10 with kernel 4.18.0-16-generic (version 4.18.0-16.17). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389077 Title: [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing minecraft with my daughter, I noticed the game was running very slowly. Even after closing the game, my web browsing slowed to a crawl. Looking at the processes in top, I noticed there were 4 tasks called kidle_inject running at 50% CPU each. After spending a long time figuring out what caused this, I found out this is caused by the Intel Powerclamp driver. I never did anything to enable this, and haven't observed this slowdown before the upgrade. I found the powerclamp driver in the /sys/class/thermal/cooling_device5 directory: root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type intel_powerclamp root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state -1 root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 50 I tried to echo 0 to cur_state, but it still reported -1 when I catted the value. There seems to be no obvious way to disable this, and this should not have been enabled in the first place. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bkat 2780 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 23:16:04 2014 HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993 InstallationDate: Installed on 2012-04-22 (925 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago) dmi.bios.date: 05/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.09 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU1284V1X dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820878] Re: linux-aws: 5.0.0-1001.1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1820878 Title: linux-aws: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Testing phase-changed: Thursday, 21. March 2019 16:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820878] Re: linux-aws: 5.0.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1820878 Title: linux-aws: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Testing phase-changed: Thursday, 21. March 2019 16:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819698 phase: Ready for Packaging phase-changed: Thursday, 21. March 2019 10:32 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820878] Re: linux-aws: 5.0.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-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 -- kernel-master-bug: 1819759 - phase: Ready for Testing - phase-changed: Thursday, 21. March 2019 16:08 UTC + phase: Ready for Release + phase-changed: Friday, 22. March 2019 12:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy -- 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/1820878 Title: linux-aws: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Release phase-changed: Friday, 22. March 2019 12:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819698 - phase: Ready for Packaging - phase-changed: Thursday, 21. March 2019 10:32 UTC + phase: Packaging + phase-changed: Friday, 22. March 2019 12:38 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819698 phase: Packaging phase-changed: Friday, 22. March 2019 12:38 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820311] Re: linux-kvm: 5.0.0-1001.1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1820311 Title: linux-kvm: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Testing phase-changed: Friday, 15. March 2019 20:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => (unassigned) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819660 - phase: Packaging - phase-changed: Friday, 15. March 2019 06:30 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 22. March 2019 12:43 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1819658 Title: linux-aws: 4.4.0-1040.43 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819660 phase: Holding before Promote to Proposed phase-changed: Friday, 22. March 2019 12:43 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux-base package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821345] [NEW] Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed
Public bug reported: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Confirmed Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [10
[Kernel-packages] [Bug 1821345] Re: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed
Note : if NUM_OF_VFS is set to 32, VF creation works fine. If it's set to 64 or above, VF creation fails. I haven't tested in between. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Confirmed Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821345] 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/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Confirmed Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Hi, We are also affected by this bug. Adding linux-meta in the loop because a simple solution could be to now add a tighter dependency on the linux-image-4.4.0-*-generic package, that means linux-base (>= 4.5ubuntu1~16.04.1). ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820311] Re: linux-kvm: 5.0.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-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 -- kernel-master-bug: 1819759 - phase: Ready for Testing - phase-changed: Friday, 15. March 2019 20:31 UTC + phase: Ready for Release + phase-changed: Friday, 22. March 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy -- 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/1820311 Title: linux-kvm: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Release phase-changed: Friday, 22. March 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] [NEW] Lenovo X1: failing to resume from suspend after closing the lid
Public bug reported: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] 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 1821350 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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid
apport information ** Tags added: apport-collected disco ** Description changed: - On a Lenovo X1, running current disco, the machine fails to resume from - suspend after closing the lid. After closing the LID, you see the LED - slowly flashing, and when again opening the lid, it changes to constant - bright light. Nothing else happens. + On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: doko 2011 F pulseaudio + /dev/snd/controlC0: doko 2011 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-01-12 (68 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: LENOVO 20MFCTO1WW + Package: linux (not installed) + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-7-generic N/A + linux-backports-modules-5.0.0-7-generic N/A + linux-firmware 1.178 + Tags: disco + Uname: Linux 5.0.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo + _MarkForUpload: True + dmi.bios.date: 01/08/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2EET36W (1.18 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20MFCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Extreme + dmi.product.name: 20MFCTO1WW + dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme + dmi.product.version: ThinkPad X1 Extreme + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248503/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Kernel-packages] [Bug 1821350] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248515/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248509/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+attachment/5248518/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248510/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248506/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248517/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248504/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248508/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248511/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248505/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248512/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248513/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248507/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248516/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1821350/+attachment/5248514/+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/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Incomplete Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1819660 - phase: Holding before Promote to Proposed - phase-changed: Friday, 22. March 2019 12:43 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 22. March 2019 13:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1819658 Title: linux-aws: 4.4.0-1040.43 -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: Confirmed 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1819660 phase: Ready for Promote to Proposed phase-changed: Friday, 22. March 2019 13:33 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819698 phase: Packaging phase-changed: Friday, 22. March 2019 12:38 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete -- 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/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -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: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819698 phase: Packaging phase-changed: Friday, 22. March 2019 12:38 UTC reason: prepare-package-meta: Pending -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid
Worked with doko on IRC and the nvidia 418 driver (currently in -proposed) fixes this. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Triaged Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820409] Re: Audio stutter after update
I would'nt say it happens, i'd say its always there constantly.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+attachment/5248540/+files/dmesg.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/1820409
Title:
Audio stutter after update
Status in linux package in Ubuntu:
Confirmed
Bug description:
After some update:
Audio stutters in VLC
Video and audio stutters in Youtube
I think cpu usage might be bigger in VLC too, over 20% vs. below 20%
earlier (one thread gets full 100%?)
Stuttering kernel at the moment is 4.15.0-46-generic.
Kernel version 4.15.0-43-generic definitely worked good.
Cant remember if i could get slight stutter from previous version version -45.
Tried also lowlatency and 4.18 kernel, bad stuttering in those.
(Distro is Lubuntu)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-46-generic 4.15.0-46.49
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-46-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: meie855 F pulseaudio
/dev/snd/controlC1: meie855 F pulseaudio
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50'
Mixer name : 'Intel Broadwell HDMI'
Components : 'HDA:80862808,80860101,0010'
Controls : 35
Simple ctrls : 5
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47'
Mixer name : 'Conexant CX20751/2'
Components : 'HDA:14f1510f,1043181d,00100100'
Controls : 20
Simple ctrls : 9
CurrentDesktop: LXDE
Date: Sat Mar 16 18:02:18 2019
InstallationDate: Installed on 2018-07-04 (255 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-46-generic N/A
linux-backports-modules-4.15.0-46-generic N/A
linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
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.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX305FA
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/1820409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid
but apparently still an issue with the nouveau driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821350 Title: Lenovo X1: failing to resume from suspend after closing the lid Status in linux package in Ubuntu: Triaged Bug description: On a Lenovo X1, running current disco, the machine fails to resume from suspend after closing the lid. After closing the LID, you see the LED slowly flashing, and when again opening the lid, it changes to constant bright light. Nothing else happens. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doko 2011 F pulseaudio /dev/snd/controlC0: doko 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-01-12 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 01/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET36W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + backports: bug 1820315 (linux-hwe-edge) + derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) + -- swm properties -- - backports: null - derivatives: bug 1820878 (linux-aws) phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-release: Pending -- ready to copy + promote-to-release: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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 1820315 (linux-hwe-edge) derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) -- swm properties -- phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1820315 (linux-hwe-edge) derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) -- swm properties -- phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-release: Pending -- ready to copy + promote-to-release: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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 1820315 (linux-hwe-edge) derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) -- swm properties -- phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume
By the way, this issue appeared on my machine, which is a Lenovo W520. I have turned off automatic suspend while plugged in. I need it to run financial calculations overnight. And, I have increased the battery power delay to 30m. Though that is neither here nor there. With "Night Light" and "Dim screen when inactive" turned off, blanking the screen works every time. Suspending and restoring works every time. I really want to get back to the "Night Light" feature, so I would like to see the bug resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Dell XPS 13 9350 on AC power left running overnight, suspends after a given timeout. When coming back the next morning sometimes the laptop resumes to an aubergine desktop (just the screen, no GDM) and cursor and sits there forever. Sometimes it resumes to a black screen and cursor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 14:15:04 2018 InstallationDate: Installed on 2018-02-13 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
