[Kernel-packages] [Bug 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes
Hello! Just checking in on this bug to see if there is any new info. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043733 Title: HP Zbook 17 G6 internal microphone causes hard crashes Status in linux package in Ubuntu: New Bug description: Anything that changes the state of the internal microphone on the HP Zbook 17 G6 can result in a hard crash of the entire system. This includes things like noise reduction being applied by Google Meets, but it can be reliably replicated by just changing the volume of the microphone until the system crashes. When the crashes occur, the logs cut off just as they would if the system's power were completely cut. This behavior only occurs with the internal microphone. External microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this same behavior. This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. This is the system device that should be responsible for handling the internal microphone. description: Multimedia audio controller product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=sof-audio-pci-intel-cnl latency=64 resources: iomemory:400-3ff iomemory:400-3ff irq:191 memory:404a108000-404a10bfff memory:404a00-404a0f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950195] Re: [amdgpu] Wayland session unresponsive on resume from suspend
I have the same issue. In Gnome on Wayland or GDM on Wayland, my system is unresponsive after resuming from suspend. The screen is black and switching to other VTs is impossible. This does not happen if I'm logged in to a Gnome on Xorg session at the time of the suspend. I have an Intel CPU and GPU. ** Attachment added: "Previous boot log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+attachment/5606317/+files/prevboot.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/1950195 Title: [amdgpu] Wayland session unresponsive on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: My laptop, HP model 17-y028cy, does not resume after the display has been shut off for inactivity. The computer starts back up and the display does turn on, but nothing is displayed on my screen. It doesn't appear to respond to any key presses so I have to force it to power down and back up by holding the power button until it shuts off. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 11:10:58 2021 DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221] InstallationDate: Installed on 2021-08-18 (82 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago) dmi.bios.date: 01/16/2017 dmi.bios.release: 15.37 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8221 dmi.board.vendor: HP dmi.board.version: 85.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 85.39 dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1MF63UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
AceLan, I have tested your kernel and touchscreen and touchpad work, without the pci=nocrs GRUB option. Thank you very much! I have two pieces of feedback on it that I think are specific to my system, but I want to log them in case they aren't. After selecting the patched 5.15 kernel in GRUB, I get the following message for a few seconds before the kernel starts to boot: "error: null src bitmap in grub_video_bitmap_create_scaled. Loading Linux 5.15.0-1043-generic ... Loading initial ramdisk ... Press any key to continue" I believe this is due to my custom GRUB theme, but it wasn't occurring on the 5.19 kernel. On both the 5.19 kernel and the 5.15.0-1043 kernel, booting is very slow - the kernel boot messages seem to take much longer than the stock 5.15 kernel. I assume this is for debugging purposes, but wanted to call it out just in case it's unexpected behavior. I'm more than happy to trade a slower boot for a working device of course! Again, feel free to ignore these quirks if they are specific to my system/expected behavior, I'm just being overly-thorough at this point. Thank you for backporting this! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Won't Fix Status in linux source package in Jammy: In Progress Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945927] [NEW] Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310
Public bug reported: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1945927 Title: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310 Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
[Kernel-packages] [Bug 1915082] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461462/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461463/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461464/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461454/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461455/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461461/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461460/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461457/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461452/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461458/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461456/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461459/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461453/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
apport information ** Tags added: apport-collected hera ** Description changed: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jordan 1659 F pulseaudio + CurrentDesktop: Pantheon + DistroRelease: elementary OS 5.1.7 + InstallationDate: Installed on 2021-01-30 (9 days ago) + InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) + MachineType: Apple Inc. MacBook7,1 + NonfreeKernelModules: nvidia wl + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-65-generic N/A + linux-backports-modules-5.4.0-65-generic N/A + linux-firmware1.173.19 + Tags: hera + Uname: Linux 5.4.0-65-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 02/02/18 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MB71.88Z.003F.B00.1802022149 + dmi.board.name: Mac-F22C89C8 + dmi.board.vendor: Apple Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-F22C89C8 + dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: + dmi.product.family: MacBook + dmi.product.name: MacBook7,1 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461451/+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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Confirmed Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 1659 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.1.7 InstallationDate: Installed on 2021-01-30 (9 days ago) InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814) MachineType: Apple Inc. MacBook7,1 NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.173.19 Tags: hera Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB71.88Z.003F.B00.1802022149 dmi.board.name: Mac-F22C89C8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8: dmi.product.family: MacBook dmi.product.name: MacBook7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.laun
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt8.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461438/+files/ssdt8.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt7.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461437/+files/ssdt7.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt6.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461436/+files/ssdt6.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461431/+files/version.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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt5.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461435/+files/ssdt5.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt1.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461430/+files/ssdt1.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt4.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461434/+files/ssdt4.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "grep -r . proc-acpi" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461426/+files/grep%20-r%20.%20proc-acpi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "fwts method" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461425/+files/fwts%20method -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "fwts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461424/+files/fwts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt2.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461432/+files/ssdt2.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ls sys-class-backlight" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461428/+files/ls%20sys-class-backlight -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "dsdt.dsl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461423/+files/dsdt.dsl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "ssdt3.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461433/+files/ssdt3.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461420/+files/acpidump.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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "results.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461429/+files/results.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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "dsdt.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461422/+files/dsdt.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "dmidecode" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461421/+files/dmidecode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461427/+files/lspci-vnvn.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/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915082] [NEW] [Macbook7, 1] backlight not working
Public bug reported: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "acpi_backlight=vendor ls sys-class-backlight" https://bugs.launchpad.net/bugs/1915082/+attachment/5461419/+files/acpi_backlight%3Dvendor%20ls%20sys-class-backlight -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915082 Title: [Macbook7,1] backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04. Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers. The apple_backlight directory appears in /sys/class/backlight and while different brightness values can be set, they have no effect on the backlight's emitted brightness. The backlight remains at full brightness. I have tested the following kernel parameters but they have no effect. acpi_backlight=vendor video.use_bios_initial_backlight=0 acpi_osi= video.use_native_backlight=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
I face a similar issue that I posted on ubuntu forum: https://ubuntuforums.org/showthread.php?t=2452881 PPA solves my issue and interestingly changes the Bluetooth controller address -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
I still find it weird that no issues occur in Windows. Will try to reproduce with kernel 5.7 and attach dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Switching the ports so that the WD15 dock is connected to the USB-C port closer to the power socket and the display is connected to the other USB-C port fixed the issue. Apple USB-C to HDMI dongle exhibited the same issue when plugged into the same port. When the WD15 was connected to the port closer to the power socket with a display attached, USB devices intermittently disconnected and reconnected. Likely a hardware defect, but @mapengyu could you try to reproduce with the ports switched around? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
@kaihengfeng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
@kaifengheng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Issue still occurs on latest mainline kernel without nvidia proprietary drivers. Attached another picture as logging is shutdown when issue occurs. The attached display is only connected to the dedicated GPU and is not outputted to at all in this configuration. ** Attachment added: "Picture of error message." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+attachment/5378562/+files/DSC_0436.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Additional information: Philips PHL276E8V attached via USB-C to DP1.2 cable Dell WD15 Dock attached via USB-C cable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Confirmed Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Confirmed Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858137] [NEW] TouchPad does not work
Public bug reported: The TouchPad will not work whatsoever. Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 2868 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 12:13:51 2020 InstallationDate: Installed on 2019-05-07 (240 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Razer Blade Stealth ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a595e455-6996-442c-bcc0-4659b0acadc5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: ABCDEF dmi.board.name: SKYBAY dmi.board.vendor: INTEL Corporation dmi.board.version: Default string dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd04/07/2016:svnRazer:pnBladeStealth:pvr1.04:rvnINTELCorporation:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Blade Stealth dmi.product.version: 1.04 dmi.sys.vendor: Razer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "/proc/bus/input/devices output" https://bugs.launchpad.net/bugs/1858137/+attachment/5317196/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858137 Title: TouchPad does not work Status in linux package in Ubuntu: Confirmed Bug description: The TouchPad will not work whatsoever. Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordan 2868 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 12:13:51 2020 InstallationDate: Installed on 2019-05-07 (240 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Razer Blade Stealth ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a595e455-6996-442c-bcc0-4659b0acadc5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: ABCDEF dmi.board.name: SKYBAY dmi.board.vendor: INTEL Corporation dmi.board.version: Default string dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd04/07/2016:svnRazer:pnBladeStealth:pvr1.04:rvnINTELCorporation:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Blade Stealth dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280550/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280548/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
apport information ** Tags added: apport-collected bionic ** Description changed: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. - There are upstream patches to fix this in the mainline kernel tree: - https://lkml.org/lkml/2019/5/17/725 + There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-06-20 (43 days ago) + InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro + ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-22-generic N/A + linux-backports-modules-4.18.0-22-generic N/A + linux-firmware 1.173.3 + RfKill: + + Tags: bionic + Uname: Linux 4.18.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/30/2019 + dmi.bios.vendor: Microsoft Corporation + dmi.bios.version: Hyper-V UEFI Release v4.0 + dmi.board.asset.tag: None + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: Hyper-V UEFI Release v4.0 + dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: Hyper-V UEFI Release v4.0 + dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: + dmi.product.family: Virtual Machine + dmi.product.name: Virtual Machine + dmi.product.sku: None + dmi.product.version: Hyper-V UEFI Release v4.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280543/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic
[Kernel-packages] [Bug 1838796] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280551/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280547/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280546/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280544/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280549/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280545/+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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] [NEW] TPM event log does not contain events measured after ExitBootServices
Public bug reported: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: New Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
There isn't yet a new kernel in *bionic* -proposed to solve this issue, so I can't test it. I have verified that building the 4.15.0-42.45 kernel with the patch (https://patchwork.kernel.org/patch/10382693/) applied fixes wifi for 16+ threaded systems on bionic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or more logical CPUs kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] And it leads to wifi can't scan any APs, and leads to system hangs while suspending. [Fix] Below commit contained in v4.17 fix the issue. ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
I encountered this iwlwifi failure while testing the Intel 9260 with the AMD Ryzen 7 2700x (8 core, 16 thread). By bisecting the kernel, I was able to narrow it down to the same commit. I can also verify that setting maxcpus=15, fixes wifi (at the cost of performance). This is a really important fix for certain System76 products. We'd really like to see it backported so Ubuntu works without compromises on our machines. I'm happy to test any testing or proposed kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or more logical CPUs kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] And it leads to wifi can't scan any APs, and leads to system hangs while suspending. [Fix] Below commit contained in v4.17 fix the issue. ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772467] Re: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic
Tested with the 4.15.0-34-generic kernel from -proposed and this also solves the issue for me. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772467 Title: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: This is a hardware specific issue with Ubuntu 18.04 and kernel 4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip causes the problem. Driver location: https://www.intel.com/content/www/us/en/support/articles/05511 /network-and-i-o/wireless-networking.html The wifi connection is very slow (1MB instead of 100MB possible download speed, upload speed is normal) and is also very unreliable. When installing the 4.16 kernel from mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described problem is solved. Sytem data: Description: Ubuntu 18.04 LTS Release: 18.04 Package: 4.15.0-20-generic driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1729 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-19 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Swift SF114-32 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=39ea17c1-4c91-45ac-81a7-401583763b21 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-19 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.15.18-041518-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
I can reproduce the issue with ethernet failing on the r8169 on resume from suspend with the current kernel. This is a regression since a previous kernel on 18.04 since the symptoms occur after installing updates. I can also confirm that Kai's kernel seems to fix ethernet after suspend on at least one of our products. Will do more testing, but this would be very good to get into the next bionic kernel update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled
The same issue here. Kernel: 4.15.0-24-generic. Ubuntu: 16.04.3 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1572659 Title: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled Status in bcmwl package in Ubuntu: Confirmed Bug description: After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver (package bcmwl-kernel-source) does not load and wifi not work. sudo modprobe wl modprobe: ERROR: could not insert 'wl': Required key not available If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works. If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21 and wifi works. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-12-02 (140 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: wl Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Also I identified this issue by using this command: dmesg |grep -i blue I got output which stated "hci0: don't support firmware rome" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7.1
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Battant et all, I believe the issue is from a commit that happened after the 4.13.xx kernel's ie 4.15 is affected. The bug affects Lenovo's for sure as that is what I have but others too. More details here: https://bugzilla.kernel.org/show_bug.cgi?id=199271 Also to fix try a 4.13.xx kernel. ** Bug watch added: Linux Kernel Bug Tracker #199271 https://bugzilla.kernel.org/show_bug.cgi?id=199271 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1750156] Re: Touchpad not recognised on ASUS FX553V since install
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750156/+attachment/5057318/+files/Xorg.0.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/1750156 Title: Touchpad not recognised on ASUS FX553V since install Status in linux package in Ubuntu: New Bug description: I installed Ubuntu 16.04 several months ago and have been using external mouse since then because the touchpad never worked. (Works under Windows.) Now upgraded to 17.10 but the problem persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750156] Re: Touchpad not recognised on ASUS FX553V since install
** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750156/+attachment/5057317/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750156 Title: Touchpad not recognised on ASUS FX553V since install Status in linux package in Ubuntu: New Bug description: I installed Ubuntu 16.04 several months ago and have been using external mouse since then because the touchpad never worked. (Works under Windows.) Now upgraded to 17.10 but the problem persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750156] [NEW] Touchpad not recognised on ASUS FX553V since install
Public bug reported: I installed Ubuntu 16.04 several months ago and have been using external mouse since then because the touchpad never worked. (Works under Windows.) Now upgraded to 17.10 but the problem persists. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1750156/+attachment/5057316/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750156 Title: Touchpad not recognised on ASUS FX553V since install Status in linux package in Ubuntu: New Bug description: I installed Ubuntu 16.04 several months ago and have been using external mouse since then because the touchpad never worked. (Works under Windows.) Now upgraded to 17.10 but the problem persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728724] [NEW] package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Hi. i was updating my OS and at the same time i was testing checkbox services. i aborted the testing service in the middle of updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-97-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stealth1645 F pulseaudio Date: Mon Oct 30 22:20:21 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9c734fcf-bf0e-46c8-bf53-6a129e895b3f InstallationDate: Installed on 2017-02-18 (254 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0bda:5801 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ProBook 6450b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=90392a73-6811-430d-a82d-9ccbf769b538 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDE Ver. F.06 dmi.board.name: 146D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.13 dmi.chassis.asset.tag: S08603 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDEVer.F.06:bd01/11/2011:svnHewlett-Packard:pnHPProBook6450b:pvr:rvnHewlett-Packard:rn146D:rvrKBCVersion73.13:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6450b dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728724 Title: package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Hi. i was updating my OS and at the same time i was testing checkbox services. i aborted the testing service in the middle of updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-97-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stealth1645 F pulseaudio Date: Mon Oct 30 22:20:21 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9c734fcf-bf0e-46c8-bf53-6a129e895b3f InstallationDate: Installed on 2017-02-18 (254 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0bda:5801 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ProBook 6450b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=90392a73-6811-430d-a82d-9ccbf769b538 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDE Ver. F.06 dmi.board.name: 146D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.13 dmi.chassis.asset.tag: S08603 dmi.chassis.type: 10
[Kernel-packages] [Bug 1686815] Re: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04
I tested the package on a new system that hadn't gotten the new firmware installed yet. Bluetooth works after installing the test package. -- 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/1686815 Title: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Incomplete Bug description: Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265 wireless modules that haven't yet had firmware loaded onto them. dmesg reports the following: Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2 This could be difficult for many people to reproduce, since installing a later version of Ubuntu once will load the necessary firmware, which will persist through reinstalling the operating system. So installing Ubuntu 17.04 just once, will leave Bluetooth in a working state forever. I was able to consistently produce the issue on a *brand new* Kabylake Meerkat 3. With Ubuntu 16.04.2, bluetooth didn't work. I copied the ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted. After this point, Bluetooth worked (and continued to work after reinstalling Ubuntu 16.04.2 and *not* copying the firmware files again). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1686815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687901] Re: i915 driver makes linux crash
@Joseph Salisbury, Nope, haven't found the commit yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded from ubuntu 16.10 to 17.04. Today I got several crash which seems to imply the i915 driver. I had the crash while using gnome-shell, and also while using unity. As I work, the system completely crash. The problem is always in: /build/linux- 2NWldV/linux-4.10.0/drivers/gpu/drm/i915/intel_display.c:4813 skylake_pfit_enable+0x140/0x160 [i915] each time I get the message: [drm:skylake_pfit_enable [i915]] *ERROR* Requesting pfit without getting a scaler first I attach the relevant kern.log parts. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 5651 F pulseaudio /dev/snd/controlC0: alex 5651 F pulseaudio CurrentDesktop: GNOME Date: Wed May 3 11:36:16 2017 HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583 InstallationDate: Installed on 2015-11-10 (539 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-02-25 (66 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687901] Re: i915 driver makes linux crash
The underlying problem appears to be the same (identical errors reported), but the symptoms can be different. The hardware I'm testing doesn't crash completely. Instead X creates a non-existent DisplayPort monitor with 1024x768 resolution and 0x0 physical size (on hardware without any DisplayPort ports). While less catastrophic than alex-garel's symptoms, it's still really confusing for the user to lose their mouse and windows to the ether of an impossible screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded from ubuntu 16.10 to 17.04. Today I got several crash which seems to imply the i915 driver. I had the crash while using gnome-shell, and also while using unity. As I work, the system completely crash. The problem is always in: /build/linux- 2NWldV/linux-4.10.0/drivers/gpu/drm/i915/intel_display.c:4813 skylake_pfit_enable+0x140/0x160 [i915] each time I get the message: [drm:skylake_pfit_enable [i915]] *ERROR* Requesting pfit without getting a scaler first I attach the relevant kern.log parts. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 5651 F pulseaudio /dev/snd/controlC0: alex 5651 F pulseaudio CurrentDesktop: GNOME Date: Wed May 3 11:36:16 2017 HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583 InstallationDate: Installed on 2015-11-10 (539 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-02-25 (66 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687901] Re: i915 driver makes linux crash
I can confirm this bug on both Ubuntu 16.04 and 17.04 on Intel Kabylake i7-7500U with Sunrise Point chipset. The 4.11 kernel you suggested fixes the problem, so it is fixed upstream. We should try and backport the fix into at least 16.04 and 17.04. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded from ubuntu 16.10 to 17.04. Today I got several crash which seems to imply the i915 driver. I had the crash while using gnome-shell, and also while using unity. As I work, the system completely crash. The problem is always in: /build/linux- 2NWldV/linux-4.10.0/drivers/gpu/drm/i915/intel_display.c:4813 skylake_pfit_enable+0x140/0x160 [i915] each time I get the message: [drm:skylake_pfit_enable [i915]] *ERROR* Requesting pfit without getting a scaler first I attach the relevant kern.log parts. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 5651 F pulseaudio /dev/snd/controlC0: alex 5651 F pulseaudio CurrentDesktop: GNOME Date: Wed May 3 11:36:16 2017 HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583 InstallationDate: Installed on 2015-11-10 (539 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-02-25 (66 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686815] [NEW] Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04
Public bug reported: Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265 wireless modules that haven't yet had firmware loaded onto them. dmesg reports the following: Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2 This could be difficult for many people to reproduce, since installing a later version of Ubuntu once will load the necessary firmware, which will persist through reinstalling the operating system. So installing Ubuntu 17.04 just once, will leave Bluetooth in a working state forever. I was able to consistently produce the issue on a *brand new* Kabylake Meerkat 3. With Ubuntu 16.04.2, bluetooth didn't work. I copied the ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted. After this point, Bluetooth worked (and continued to work after reinstalling Ubuntu 16.04.2 and *not* copying the firmware files again). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- 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/1686815 Title: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04 Status in linux-firmware package in Ubuntu: New Bug description: Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265 wireless modules that haven't yet had firmware loaded onto them. dmesg reports the following: Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2 This could be difficult for many people to reproduce, since installing a later version of Ubuntu once will load the necessary firmware, which will persist through reinstalling the operating system. So installing Ubuntu 17.04 just once, will leave Bluetooth in a working state forever. I was able to consistently produce the issue on a *brand new* Kabylake Meerkat 3. With Ubuntu 16.04.2, bluetooth didn't work. I copied the ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted. After this point, Bluetooth worked (and continued to work after reinstalling Ubuntu 16.04.2 and *not* copying the firmware files again). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1686815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
Verified the 1.164.1 package in proposed. It fixes this bug. ** Tags removed: wifi ** Tags added: verification-donewifi ** Tags removed: verification-donewifi ** Tags added: verification-done wifi -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Status in linux-firmware source package in Artful: Confirmed Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I have a new laptop Avell B155 V4 with i7 and GTX 950M and I get the same error. I'm not able to install or run the live Ubuntu, it gets stuck on loading screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [
[Kernel-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move
Initial testing shows that the test kernel resolves the issue as well. I will continue to test to check for regressions, but I think we have a solution here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646574 Title: Mouse cursor invisible or does not move Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed in left upper corner or sometimes disappear. I actually can click or hover everywhere on the screen, I just don't know where the mouse is pointer at the moment. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: yakkety DistroRelease: Ubuntu 16.10 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04] InstallationDate: Installed on 2016-11-26 (5 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 002: ID ffc0:0040 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_67RSRP Package: xserver-xorg-video-nouveau 1:1.0.12-2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Tags: yakkety ubuntu Uname: Linux 4.8.0-27-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/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
Just tested 1.161.1 in yakkety-proposed and can confirm it fixes the issue. ** Tags added: verification-done -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Committed Status in linux-firmware source package in Zesty: Fix Committed Bug description: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
The test package works here! -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: In Progress Status in linux-firmware source package in Yakkety: In Progress Status in linux-firmware source package in Zesty: In Progress Bug description: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] [NEW] intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
Public bug reported: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug linux-firmware wifi yakkety ** Attachment added: "oryp2_64gb_iwlwifi_dmesg" https://bugs.launchpad.net/bugs/1647826/+attachment/4788267/+files/oryp2_64gb_iwlwifi_dmesg -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 Status in linux-firmware package in Ubuntu: New Bug description: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update
Verified linux-firmware 1.157.6 from xenial-proposed. ** Tags added: verification-done -- 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/1645911 Title: linux-firmware 1.157.5 causes sound issues after initramfs update Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Status in linux-firmware source package in Xenial: Fix Committed Bug description: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update
Just tested on the affected hardware, and can confirm the new package fixes this bug. After enabling -proposed, running updates, and doing a full shutdown, sound begins working correctly again. -- 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/1645911 Title: linux-firmware 1.157.5 causes sound issues after initramfs update Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Status in linux-firmware source package in Xenial: Fix Committed Bug description: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645911] Re: linux-firmware package causes sound issues with after initramfs update
The test package fixes the issue (after running 'sudo update-initramfs -u' and doing a shutdown and cold boot. Perhaps we could have the linux-firmware package update the initramfs as part of the post install process. In my testing simply installing a new linux-firmware package didn't immediately manifest different behavior, which made tracking this issue down more difficult. This would make it so the updated package automatically heals the affected systems on the next cold boot. -- 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/1645911 Title: linux-firmware package causes sound issues with after initramfs update Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Status in linux-firmware source package in Xenial: Confirmed Bug description: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645911] [NEW] linux-firmware package causes sound issues with after initramfs update
Public bug reported: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: kabylake linux-firmware sound update-initramfs -- 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/1645911 Title: linux-firmware package causes sound issues with after initramfs update Status in linux-firmware package in Ubuntu: New Bug description: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1645911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1608622] Re: 14.04.5 drops to initramfs prompt during boot with nvme drive
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => 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/1608622 Title: 14.04.5 drops to initramfs prompt during boot with nvme drive Status in initramfs-tools package in Ubuntu: New Bug description: So, installing 14.04.4 works fine, but systems with nvme drives don't boot after installing 14.04.5. Steps to reproduce: 1) Install Ubuntu 14.04.5 on a system with an nvme drive 2) reboot 3) instead of booting to a graphical environment, there is an initramfs prompt. Notes: This also prevents reaching any of the recovery mode tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1608622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1608622] [NEW] 14.04.5 drops to initramfs prompt during boot with nvme drive
Public bug reported: So, installing 14.04.4 works fine, but systems with nvme drives don't boot after installing 14.04.5. Steps to reproduce: 1) Install Ubuntu 14.04.5 on a system with an nvme drive 2) reboot 3) instead of booting to a graphical environment, there is an initramfs prompt. Notes: This also prevents reaching any of the recovery mode tools. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608622 Title: 14.04.5 drops to initramfs prompt during boot with nvme drive Status in linux package in Ubuntu: New Bug description: So, installing 14.04.4 works fine, but systems with nvme drives don't boot after installing 14.04.5. Steps to reproduce: 1) Install Ubuntu 14.04.5 on a system with an nvme drive 2) reboot 3) instead of booting to a graphical environment, there is an initramfs prompt. Notes: This also prevents reaching any of the recovery mode tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
Tested the proposed kernel with: * GTX 970M * GTX 970 * GTX 1080 All three systems boot into unity as expected with the proposed kernel. Only the GTX 1080 is in low graphics mode (expected because nouveau doesn't yet support it) This should be good to go. It's already a confirmed improvement for first boot, and I'll test again to confirm that the new kernel enables the graphical installer once it hits the daily iso. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
Success with the patched test build! The nouveau patch allows our systems to boot into Unity with Pascal series cards without requiring nvidia-367. Tested and successfully booted with: *GTX 1070 *GTX 1080 *GTX 970 *GTX 950 *GTX 730 No regressions found so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Bug description: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
** Description changed: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. + + + Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 ** Description changed: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. - Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 + Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards Status in linux package in Ubuntu: Incomplete Bug description: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602340] [NEW] nouveau: boot hangs at blank screen with unsupported graphics cards
Public bug reported: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug nouveau -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards Status in linux package in Ubuntu: Incomplete Bug description: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
Confirming this issue also with the Phillips Bluetooth speaker model BT2500B/37. Cannot set to higher quality sound in pulseaudio. Using gnome-ubuntu 16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Note that while this particular bug, about missing ohci-pci in the initramfs, is fixed in Ubuntu 15.04 another similar bug, missing xhci- pci, is still present. The debian bug report about, and fix for, missing xhci-pci is here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=773250 If you are experiencing these symptoms on Ubuntu 15.04 (USB keyboard working in installed and Live systems, but not debian-installer / early boot initramfs), you are probably hitting the xhci-pci bug. ** Bug watch added: Debian Bug tracker #773250 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773250 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in initramfs-tools source package in Saucy: Invalid Status in linux source package in Saucy: Fix Released Status in initramfs-tools source package in Trusty: Confirmed Status in linux source package in Trusty: Fix Released Status in initramfs-tools source package in Utopic: Invalid Status in linux source package in Utopic: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1074792] Re: Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not Windows
I found that my issue was actually caused by interference. The dongle was too close to my cell phone, moving the dongle closer to the mouse and farther from the cell phone, actually solved all jitter issues for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1074792 Title: Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not Windows Status in bluez package in Ubuntu: Confirmed Bug description: My Prolink PMO624B Bluetooth Mouse movement is laggy/sluggish/erratic in Ubuntu 12.04 and 12.10 on a Asus EeePC 1215B. However, it works completely normal in Windows 7 on the same machine, so I believe that the issue is with Linux/BlueZ. Please advise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1074792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Just an update, I rebooted without the dongle plugged in and get the previous error messages. I've attached the error log. ** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+attachment/4389617/+files/dmesg.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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: In Progress Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
I'm still having an issue with my Alienware 13 with xubuntu 14.04. I tried Laaag's method with both the MSI and Alienware drivers to no avail. The logs were showing Firmware Crashed earlier but now shows the attached. I've also tried on both the latest stable kernel (4.0.1) and the latest Release Candidate (4.1-rc1). I've got wifi going with the following dongle http://www.dx.com/p/ultra- mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network- adapter-48166 in the meantime. Hopefully there is a solid fix for this soon. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+attachment/4389616/+files/dmesg.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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: In Progress Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
An addition to my #18 comment above. I forgot that I had to remove logging on calls from skb_release_head_state to dst_release due to performance impact of the number of calls. In both failure and success scenarios, calls to dst_release by skb_release_head_state are also present. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
To add to my comment just above, we have found a workload that is not under own our control (which limits what we can do with it, including sharing it) but which exacerbates the issue on our systems. This workload causes the issue less than 5% of the time and that gives us the chance to look at what callers are using dst_release on the dst in question (the one that meets conditions A, B, and C; ABC dst). To clarify, failure at this point for us is when the dst-ref_cnt=1 during free_fib_info_rcu, success is when dst-ref_cnt=0 and free_fib_info_rcu calls dst_destroy on it's nh_rth_input member. In both failure and non-failure scenarios the only two callers we see on are a single call to ipv4_pktinfo_prepare, and many calls to inet_sock_destruct, and tcp_data_queue. That likely eliminates a unique function call to dst_release that can be identified as missing in failure scenarios. My interpretation is that a single call to inet_sock_destruct or tcp_data_queue is failing to occur when in the failure scenario. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
I'm working with Rodrigo Vaz and we've found some details about our occurrence of this issue using systemtap. rt_cache_route places a dst_entry struct into a fib_nh struct as the nh_rth_input. Occasionally the reference counter on that dst is not decremented by the time free_fib_info_rcu is called on the fib during container teardown. In that case free_fib_info_rcu doesn't call dst_destroy and dev_put is not called on the lo interface of the container. The only situation where we've seen this is when A) the fib_nh-nh_dev points to the eth0 interface of the container, B) the dst is part of an rtable struct where rt- rt_is_input==1, and C) the dst points to the lo interface of the container. The dst is cached in the fib only once and never replaced and then thousands of dst_hold/dst_release calls are made on the dst for connections and socket buffers. We have only seen this so far on containers making lots of outbound connections. It doesn't appear to depend on the lifetime of the container, some are only alive for 30min and others are alive for 24hrs. The issue occurs when you try to destroy the container because that is when the fib is freed. We don't know when or where the dst ref_cnt becomes incorrect. We don't know how to reproduce the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337281] Re: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot
I experienced this myself but it seems to be all outbound NAT traffic. I set grub to boot and older kernel and everything went back to normal. From a workstation behind the firewall, do a speed test at speakeasy.net and notice that the download speeds are really not affected but when it goes to test your upload it can't even complete the test. My kernel version was 3.2.0-65. I hope they fix this soon - it has caused a lot of problems for me and my customers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337281 Title: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot Status in “linux” package in Ubuntu: Confirmed Bug description: Since we installed the latest kernel update on our firewall this weekend (3.2.0-65.98) we got massive problems connecting from thunderbird (windows client) to an external imap-server (dovecot with tls). With our Linux client we got no problems. Opening or sending mails with attachments which was done in a second before the update, took some minutes after the update to kernel 3.2.0-65! Installing the kernel version 3.2.0-64 on our firewall system fixed the problem, also the newer kernel linux-generic-lts-trusty did fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1275846] [NEW] [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure
Public bug reported: Failed to resume on suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-generic 3.13.0-6.23 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1505 F pulseaudio jordan 2287 F pulseaudio /dev/snd/controlC0: lightdm1505 F pulseaudio jordan 2287 F pulseaudio CurrentDmesg: [ 40.723244] init: plymouth-stop pre-start process (1104) terminated with status 1 Date: Mon Feb 3 17:12:19 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=046d6951-8fb9-4e7d-b5fa-cd45fd627c0d InstallationDate: Installed on 2014-01-31 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=5b32ed91-dc40-4660-8245-d7af9291b3f5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.name: 3636 dmi.board.vendor: Hewlett-Packard dmi.board.version: 33.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd05/17/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3636:rvr33.23:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049D212412102 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1275846 Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: Failed to resume on suspend. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-generic 3.13.0-6.23 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1505 F pulseaudio jordan 2287 F pulseaudio /dev/snd/controlC0: lightdm1505 F pulseaudio jordan 2287 F pulseaudio CurrentDmesg: [ 40.723244] init: plymouth-stop pre-start process (1104) terminated with status 1 Date: Mon Feb 3 17:12:19 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=046d6951-8fb9-4e7d-b5fa-cd45fd627c0d InstallationDate: Installed on 2014-01-31 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=5b32ed91-dc40-4660-8245-d7af9291b3f5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.name: 3636
