[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same here for a while now, really annoying $ inxi -SCGxxxz System:Host: Slenvy Kernel: 5.3.0-46-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) info: gnome-shell dm: gdm3 Distro: Ubuntu 18.04.4 LTS CPU: Quad core Intel Core i7-8550U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15999 clock speeds: min/max: 400/4000 MHz 1: 796 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz 5: 796 MHz 6: 799 MHz 7: 798 MHz 8: 795 MHz Graphics: Card-1: Intel UHD Graphics 620 bus-ID: 00:02.0 chip-ID: 8086:5917 Card-2: NVIDIA GP108M [GeForce MX150] bus-ID: 01:00.0 chip-ID: 10de:1d10 Display Server: x11 (X.Org 1.20.5 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 1873441] Re: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
added to git ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-oem-5.6 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873441 Title: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Committed Bug description: Error messages printed whenever trying to update initramfs for 5.6 kernels: $ sudo update-initramfs -u -k 5.6.0-1008-oem -> mkinitramfs -v -o a.new 5.6.0-1008-oem -> modinfo -k 5.6.0-1008-oem -F firmware da903x https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=b66512b91a5918b01d4cc46ec85d829fb957e989 "UBUNTU: [Packaging] Include modules.builtin.modinfo in linux-modules" is not included in 5.6 tree. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vicamo 1465 F pulseaudio /dev/snd/controlC1: vicamo 1465 F pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 17 19:25:38 2020 InstallationDate: Installed on 2019-09-28 (201 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-24-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash crashkernel=512M-:192M 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-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1873441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863973] Re: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
[Expired for linux (Ubuntu Eoan) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863973 Title: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings Status in linux package in Ubuntu: Expired Status in linux source package in Eoan: Expired Status in linux source package in Focal: Expired Bug description: [Impact] I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for meetings. I access Google Meet with Firefox. During a meeting, or immediately after one, and especially so if I join a second meeting after one finishes, my input devices start acting up and my system becomes unstable. Things start with my Headset getting reset: [ 3153.811599] usb 3-3: reset high-speed USB device number 2 using xhci_hcd This happens multiple times. Then I get a long list of suppressed callbacks: [13468.808356] retire_capture_urb: 133 callbacks suppressed From there, things timeout and I get this stack trace: hid-generic 0003:046D:0A38.0005: input,hiddev2,hidraw4: USB HID v1.11 Device [Logitech Inc. Logitech USB Headset H340] on usb-:06:00.0-2/input3 INFO: task kworker/0:1:366 blocked for more than 120 seconds. Not tainted 5.3.0-40-generic #32-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/0:1 D0 366 2 0x80004000 Workqueue: usb_hub_wq hub_event Call Trace: __schedule+0x2b9/0x6c0 ? unlink1+0x31/0x130 schedule+0x42/0xb0 usb_kill_urb+0x81/0xc0 ? wait_woken+0x80/0x80 usb_hcd_flush_endpoint+0x16c/0x180 usb_disable_endpoint+0x9b/0xb0 usb_disable_interface+0x43/0x60 usb_unbind_interface+0x183/0x260 device_release_driver_internal+0xe4/0x1c0 device_release_driver+0x12/0x20 bus_remove_device+0xe1/0x150 device_del+0x168/0x370 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x250 usb_disconnect+0xc0/0x270 hub_port_connect+0x7d/0x850 port_event+0x502/0x780 ? __switch_to_asm+0x40/0x70 hub_event+0x152/0x390 ? __schedule+0x2c1/0x6c0 process_one_work+0x1db/0x380 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x380/0x380 ? kthread_park+0x80/0x80 ret_from_fork+0x35/0x40 This is then followed by: [14262.566484] xhci_hcd :06:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [14262.566487] xhci_hcd :06:00.0: Looking for event-dma 0007ed5edff0 trb-start 0007b4a5b000 trb-end 0007b4a5b000 seg-start 0007b4a5b000 seg-end 0007b4a5bff0 During this time, video stutters and audio coming to the headphone stutters and repeats. It sometimes makes having meetings difficult. This has happened since 4.18 on cosmic, and was just as bad on 5.0 disco. When I moved to 5.3 eoan things got better, but I still experience these problems. Usually these problems make Firefox unusable too, but for this particular snapshot of logs, Firefox continued to work fine. If I unplug the headset and move it from a USB 2 port to a USB 3 port I can usually get through the meeting okay. [Test Case] Use a Logitech H340 USB Headset with Google Meet on Firefox. This is not always reproducible, and I am still determining how to reliably reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863973] Re: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
[Expired for linux (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863973 Title: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings Status in linux package in Ubuntu: Expired Status in linux source package in Eoan: Expired Status in linux source package in Focal: Expired Bug description: [Impact] I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for meetings. I access Google Meet with Firefox. During a meeting, or immediately after one, and especially so if I join a second meeting after one finishes, my input devices start acting up and my system becomes unstable. Things start with my Headset getting reset: [ 3153.811599] usb 3-3: reset high-speed USB device number 2 using xhci_hcd This happens multiple times. Then I get a long list of suppressed callbacks: [13468.808356] retire_capture_urb: 133 callbacks suppressed From there, things timeout and I get this stack trace: hid-generic 0003:046D:0A38.0005: input,hiddev2,hidraw4: USB HID v1.11 Device [Logitech Inc. Logitech USB Headset H340] on usb-:06:00.0-2/input3 INFO: task kworker/0:1:366 blocked for more than 120 seconds. Not tainted 5.3.0-40-generic #32-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/0:1 D0 366 2 0x80004000 Workqueue: usb_hub_wq hub_event Call Trace: __schedule+0x2b9/0x6c0 ? unlink1+0x31/0x130 schedule+0x42/0xb0 usb_kill_urb+0x81/0xc0 ? wait_woken+0x80/0x80 usb_hcd_flush_endpoint+0x16c/0x180 usb_disable_endpoint+0x9b/0xb0 usb_disable_interface+0x43/0x60 usb_unbind_interface+0x183/0x260 device_release_driver_internal+0xe4/0x1c0 device_release_driver+0x12/0x20 bus_remove_device+0xe1/0x150 device_del+0x168/0x370 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x250 usb_disconnect+0xc0/0x270 hub_port_connect+0x7d/0x850 port_event+0x502/0x780 ? __switch_to_asm+0x40/0x70 hub_event+0x152/0x390 ? __schedule+0x2c1/0x6c0 process_one_work+0x1db/0x380 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x380/0x380 ? kthread_park+0x80/0x80 ret_from_fork+0x35/0x40 This is then followed by: [14262.566484] xhci_hcd :06:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [14262.566487] xhci_hcd :06:00.0: Looking for event-dma 0007ed5edff0 trb-start 0007b4a5b000 trb-end 0007b4a5b000 seg-start 0007b4a5b000 seg-end 0007b4a5bff0 During this time, video stutters and audio coming to the headphone stutters and repeats. It sometimes makes having meetings difficult. This has happened since 4.18 on cosmic, and was just as bad on 5.0 disco. When I moved to 5.3 eoan things got better, but I still experience these problems. Usually these problems make Firefox unusable too, but for this particular snapshot of logs, Firefox continued to work fine. If I unplug the headset and move it from a USB 2 port to a USB 3 port I can usually get through the meeting okay. [Test Case] Use a Logitech H340 USB Headset with Google Meet on Firefox. This is not always reproducible, and I am still determining how to reliably reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863761] Re: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863761 Title: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel Status in linux package in Ubuntu: Expired Bug description: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel. More details is here: https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000163.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000164.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000165.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000166.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860367] Re: New kernel 5.3 doesn't recognize older NVIDIA graphics card
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860367 Title: New kernel 5.3 doesn't recognize older NVIDIA graphics card Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Expired Bug description: Updated U-Mate 18.04.3 which installed kernel 5.3.0. 1920x1080 monitor went into 800x600 resolution and unable to fix. Rebooted to 5.0.0 through grub and everything was back to normal. I've seen other forums (Ask Ubuntu, Linux Mint) that are reporting the same thing. I posted on the community forum and was asked to submit a bug report: https://ubuntu-mate.community/t/18-04-3-update-caused-problems-with- display-nvidia/20929/2 It seems to be an Ubuntu problem with the 390 driver. Graphics Card: Nvidia Quadro 600. I don't have problems with the new kernel on my other machines with AMD or Intel integrated graphics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1860367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863939] Re: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863939 Title: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot Status in linux package in Ubuntu: Expired Bug description: Hello! I found that both of generic and snapdragon kernels from focal repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device tree blob..." (which means I can not provide apport report, because I can not boot kernel from focal repository, and apport refuse to collect information with other kernels). At the same time snapdragon kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with https://bugzilla.kernel.org/show_bug.cgi?id=204685 and https://bugs.launchpad.net/bugs/1863761 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863752] Re: Removal of linux-image-5.3.0-29-generic fails
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863752 Title: Removal of linux-image-5.3.0-29-generic fails Status in linux package in Ubuntu: Expired Bug description: Attempting to update the kernel from linux-image-5.3.0-29-generic to 5.3.0-40-generic on a 19.10 system with default ZFS root and boot keeps failing. The latter has installed (for some value of install) but the former can't be removed and the system is left running that older kernel. Possibly due to some issue with setting up the next boot image under ZFS? root@foo:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED linux-image-5.3.0-29-generic 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 2 not fully installed or removed. After this operation, 11.4 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 228252 files and directories currently installed.) Removing linux-image-5.3.0-29-generic (5.3.0-29.31) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.3.0-29-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.elf Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sdb7 failed: Device or resource busy Command failed. Found Debian GNU/Linux 10 (buster) on /dev/sdc2 error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 178 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-5.3.0-29-generic (--remove): installed linux-image-5.3.0-29-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-5.3.0-29-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) root@foo:~# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 root@foo:~# apt-cache policy linux-image-5.3.0-29-generic linux-image-5.3.0-29-generic: Installed: 5.3.0-29.31 Candidate: 5.3.0-29.31 Version table: *** 5.3.0-29.31 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# apt-cache policy linux-image-5.3.0-40-generic linux-image-5.3.0-40-generic: Installed: 5.3.0-40.32 Candidate: 5.3.0-40.32 Version table: *** 5.3.0-40.32 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# uname -a Linux foo 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Feb 18 12:06:33 2020 InstallationDate: Installed on 2020-01-16 (32 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64
[Kernel-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
** Tags added: hwe-bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Sounds like this might be a kernel bug, or a hardware problem. I am skeptical of CSR Bluetooth dongles since they seem to be consistently unreliable, at least on Linux. Please try a newer (or older) kernel version and tell us if that makes any difference: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Or more simply just try live booting Ubuntu 20.04 from USB and tell us if that has the same bug: http://cdimage.ubuntu.com/daily-live/current/ Ubuntu 20.04 is due for release at the end of this week. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
Now we are getting somewhere. X windows system implicated. Though the 2d video shows how fast the shortcut boot is, I thought I should get a firm number so I did the shortcut boot and logged in to get output of 'systemd-analyze critical- chain' and I got the following very interesting responses, shell dialogue copied below. The same processes (I would assume) are hanging for 1m44s, but the shortcut somehow allows the user to log in while waiting for them to finish (as well as solving the other problems of clipboard and screen size, which seem to go with the more primitive login screen). Whether those processes should take 1m44s or not, I don't know, maybe it is normal, but the user should be able to log in before they are complete, as I can do with shortcut boot. If those processes are taking inordinately long, then shortcut boot gives opportunity to log in and catch them as they struggle, as seen below. The time I had to wait to get the critical-chain result was about as long as I had to wait to log in at all, under stock 19.10 without shortcut-boot procedure: wift@stock19:~$ sudo -i [sudo] password for swift: root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemctl list-jobs JOB UNIT TYPE STATE 48 setvtrgb.service start waiting 137 system-getty.slice start waiting 1 graphical.target start waiting 102 systemd-update-utmp-runlevel.service start waiting 83 plymouth-quit-wait.service start running 2 multi-user.targetstart waiting 6 jobs listed. root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# date Sun 19 Apr 2020 10:50:27 PM EDT root@stock19:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 44.881s └─multi-user.target @1min 44.881s └─xrdp.service @1.496s +1.036s └─xrdp-sesman.service @1.474s +20ms └─network.target @1.470s └─NetworkManager.service @1.381s +88ms └─dbus.service @1.379s └─basic.target @1.375s └─sockets.target @1.375s └─snapd.socket @1.373s +1ms └─sysinit.target @1.372s └─systemd-timesyncd.service @1.175s +196ms └─systemd-tmpfiles-setup.service @1.160s +10ms └─local-fs.target @1.158s └─home-swift-shared\x2ddrives.mount @11.731s └─local-fs-pre.target @177ms └─lvm2-monitor.service @116ms +61ms └─dm-event.socket @115ms └─system.slice @110ms └─-.slice @110ms root@stock19:~# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf,
[Kernel-packages] [Bug 1873720] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873720 Title: Failed to boot after upgrade due to video driver Status in linux package in Ubuntu: Confirmed Bug description: When I upgraded my system to 20.04, the boot sequence hung. When I changed my GRUB to include nomodeset, things booted up fine, but not much functionality for my display. I finally added modeprobe.blacklist=nouveau in order to get the machine to boot and get more display functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: compat ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1606 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 19:33:29 2020 IwConfig: wlp60s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=88bc2510-1184-416f-8e62-077047a331e7 ro quiet splash modeprobe.blacklist=nouveau vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-18 (2 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 02MV1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd11/08/2019:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn02MV1F:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.product.sku: 077A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu. Yes, I am able to select the “restart” button with
the keyboard. But then the shortcut doesn’t work; what triggers the
shortcut is powering off the VM.
https://chaetura.net/ms-vid2-bug-1848534.webm
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3.
Reasonable conclusion is that all three problems have the same cause,
which somehow the shortcut boot avoids:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas
stock 19.10 came in one size only and user has no opportunity to select;
goes hand in hand with the different login screen, as you can see in
video.
3) after login, cut-and-paste from guest to host is possible. Not
functional with stock 19.10.
I see that graphical artifact at some point during boot of any Ubuntu VM
in Hyper-V. You can see it in the video too. In 19.10 it comes while the
Spectre mitigation message is on the screen in console, at a point where
console changes its rendering/mode somehow and the message reappears in
a slightly different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10
it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the shortcut boot sequence. On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot now (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less than 2s to "graphical.target", compared with 104s for
19.10.
swift@Riflebird:~$ sudo -i
[sudo] password for swift:
root@Riflebird:~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1.836s
└─multi-user.target @1.836s
└─kerneloops.service @1.829s +6ms
└─network-online.target @1.827s
└─NetworkManager-wait-online.service @663ms +1.163s
└─NetworkManager.service @566ms +96ms
└─dbus.service @538ms
└─basic.target
[Kernel-packages] [Bug 1873718] [NEW] CSR8510 based BTA-402 Bluetooth device cannot be started
Public bug reported: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: New Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0:
[Kernel-packages] [Bug 1873720] [NEW] Failed to boot after upgrade due to video driver
Public bug reported: When I upgraded my system to 20.04, the boot sequence hung. When I changed my GRUB to include nomodeset, things booted up fine, but not much functionality for my display. I finally added modeprobe.blacklist=nouveau in order to get the machine to boot and get more display functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: compat ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1606 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 19:33:29 2020 IwConfig: wlp60s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=88bc2510-1184-416f-8e62-077047a331e7 ro quiet splash modeprobe.blacklist=nouveau vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-18 (2 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 02MV1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd11/08/2019:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn02MV1F:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.product.sku: 077A dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873720 Title: Failed to boot after upgrade due to video driver Status in linux package in Ubuntu: New Bug description: When I upgraded my system to 20.04, the boot sequence hung. When I changed my GRUB to include nomodeset, things booted up fine, but not much functionality for my display. I finally added modeprobe.blacklist=nouveau in order to get the machine to boot and get more display functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: compat ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1606 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 19:33:29 2020 IwConfig: wlp60s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=88bc2510-1184-416f-8e62-077047a331e7 ro quiet splash modeprobe.blacklist=nouveau vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-18 (2 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 02MV1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd11/08/2019:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn02MV1F:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.product.sku: 077A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
@vicamo, did this failure (comment#23) only happen this v5 patch? We did successfully aplly the earlier (v3?) patch, right? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: New Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873441] Re: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
** Tags added: oem-priority originate-from-1873553 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873441 Title: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Confirmed Bug description: Error messages printed whenever trying to update initramfs for 5.6 kernels: $ sudo update-initramfs -u -k 5.6.0-1008-oem -> mkinitramfs -v -o a.new 5.6.0-1008-oem -> modinfo -k 5.6.0-1008-oem -F firmware da903x https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=b66512b91a5918b01d4cc46ec85d829fb957e989 "UBUNTU: [Packaging] Include modules.builtin.modinfo in linux-modules" is not included in 5.6 tree. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vicamo 1465 F pulseaudio /dev/snd/controlC1: vicamo 1465 F pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 17 19:25:38 2020 InstallationDate: Installed on 2019-09-28 (201 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-24-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash crashkernel=512M-:192M 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-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1873441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873714] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873714 Title: Computer freeze on application change / memory allocation Status in linux package in Ubuntu: Confirmed Bug description: Experience behaviour: The system freezes for about 10 seconds often when - I change applications - I open applications - switch tabs in firefox - open new web pages - draw in GIMP with pen tablet Average occurance: - every 1 - 4 minutes // usual PC usage - every 30 seconds // when drawing in GIMP with pen tablet Reproducability: always My guess is: The system freezes, when memory management is done. Additional information: - 5.3.0-40-generic had none of these problems - 5.3.0-45-generic had similar problems, but instead of freezing for 10 seconds, the system would just freeze forever. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 1588 F pulseaudio /dev/snd/pcmC0D3p: nimono 1588 F...m pulseaudio /dev/snd/pcmC0D0c: nimono 1588 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Apr 20 11:19:29 2020 MachineType: FUJITSU FMVWB3U27 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-01 (141 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873714] [NEW] Computer freeze on application change / memory allocation
Public bug reported: Experience behaviour: The system freezes for about 10 seconds often when - I change applications - I open applications - switch tabs in firefox - open new web pages - draw in GIMP with pen tablet Average occurance: - every 1 - 4 minutes // usual PC usage - every 30 seconds // when drawing in GIMP with pen tablet Reproducability: always My guess is: The system freezes, when memory management is done. Additional information: - 5.3.0-40-generic had none of these problems - 5.3.0-45-generic had similar problems, but instead of freezing for 10 seconds, the system would just freeze forever. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 1588 F pulseaudio /dev/snd/pcmC0D3p: nimono 1588 F...m pulseaudio /dev/snd/pcmC0D0c: nimono 1588 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Apr 20 11:19:29 2020 MachineType: FUJITSU FMVWB3U27 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-01 (141 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873714 Title: Computer freeze on application change / memory allocation Status in linux package in Ubuntu: Confirmed Bug description: Experience behaviour: The system freezes for about 10 seconds often when - I change applications - I open applications - switch tabs in firefox - open new web pages - draw in GIMP with pen tablet Average occurance: - every 1 - 4 minutes // usual PC usage - every 30 seconds // when drawing in GIMP with pen tablet Reproducability: always My guess is: The system freezes, when memory management is done. Additional information: - 5.3.0-40-generic had none of these problems - 5.3.0-45-generic had similar problems, but instead of freezing for 10 seconds, the system would just freeze forever. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 1588 F pulseaudio /dev/snd/pcmC0D3p: nimono 1588 F...m pulseaudio /dev/snd/pcmC0D0c: nimono 1588 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Apr 20 11:19:29 2020 MachineType: FUJITSU FMVWB3U27 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-01 (141 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873714/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu.
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas stock
19.10 came in one size only
and user has no opportunity to select; goes hand in hand with the
different login screen, as you
I see that graphical artifact at some point during boot of any Ubuntu VM in
Hyper-V. You can see it in the video too. In 19.10 it comes while the Spectre
mitigation message is on the screen in console, at a point where console
changes its rendering/mode somehow and the message reappears in a slightly
different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10 it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the restart sequence described last time. (On that subject, I don't get
the "system setup" grub option in the stock 19.10, only after updates.
You probably figured out I mistakenly wrote "system startup" earlier
instead of "system setup" as well. And yes, keyboard can select
"restart" but in this case, the shortcut does *NOT* work. Only pulling
the plug on the VM from Hyper-V ) On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot noq (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Also in 19.10 I never get the choice of a screen size for the guest when
connecting; it is always the same size. I get the choice in 18.04 and
can choose any size including full-screen, and it just works.
I understand that these other problems with 19.10 guest may be off-
topic; I am mentioning them here in case they correlate to the current
topic. In summary, four significant problems with 19.10 that do not
exist in 18.04, both out of the box quick-create, using same host: 1)
the long delay at startup. 2) no cut-and-paste from guest to host. 3) no
capability to resize Hyper-V Connection screen. 4) requires research to
get past a grub update.
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
A stray click sent my previous message before I had finished editing it, and I see no way to edit my post. I will post fully complete/edited version momentarily. I hope an admin will delete this message and my prior message to avoid cruft in this thread. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-07-04 (105 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: xorg-server (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash video=hyperv_fb:1900x900 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 RfKill: Tags: eoan ubuntu Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) UserGroups: adm cdrom dip lpadmin 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: 2831-3616-6111-5725-4803-1162-28 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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/gdm3/+bug/1848534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
And yes nvidia-drm.modeset=1 will give you back the missing boot animation, but that discussion should stay in bug 1868240. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note that we don't recommend use of nvidia-drm.modeset=1 for most users because it still results in some bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset And I'm not sure that's even a complete list. So you should be aware of what you're getting into. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/gdm3/+bug/1845801/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1802652] Re: keyboard backlight not working on Asus GM501
I'm trying to break this down further: This block is the set of keys which I've included the byte output for in a reply further back, repeated for clarity. This block is currently not interpreted by the kernel as anything I guess due to the vendor specific page: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x76, // Usage (0x76) 0xA1, 0x01, // Collection (Application) 0x85, 0x5A, // Report ID (90) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x05, // Report Count (5) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0xB1, 0x00, // Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection while the ROG key gives: [90, 56, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Fan: [90, 174, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-off: [90, 53, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-down: [90, 16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-up: [90, 32, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Touchpad-toggle: [90, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Sleep: [90, 108, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Airplane-toggle: [90, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Keyboard backlight up: [90, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Keyboard backlight down: [90, 197, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Aura-prev: [90, 178, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Aura-next: [90, 179, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] This block is functioning fine as a consumer device: 0x05, 0x0C, // Usage Page (Consumer) 0x09, 0x01, // Usage (Consumer Control) 0xA1, 0x01, // Collection (Application) 0x85, 0x02, // Report ID (2) 0x19, 0x00, // Usage Minimum (Unassigned) 0x2A, 0x3C, 0x02, // Usage Maximum (AC Format) 0x15, 0x00, // Logical Minimum (0) 0x26, 0x3C, 0x02, // Logical Maximum (572) 0x75, 0x10, // Report Size (16) 0x95, 0x02, // Report Count (2) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0xC0, // End Collection This block has I/O. 0x5D, // Report ID (93) is the LED backlight for the keyboard. The Backlight controller I think writes back the input data. 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x79, // Usage (0x79) 0xA1, 0x01, // Collection (Application) 0x85, 0x5D, // Report ID (93) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x1F, // Report Count (31) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0x91, 0x00, // Output (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0xB1, 0x00, // Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection I don't know what this block is. HID descriptors are a little confusing to look at: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x80, // Usage (0x80) 0xA1, 0x01, // Collection (Application) 0x85, 0x5E, // Report ID (94) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x05, // Report Count (5) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF)
[Kernel-packages] [Bug 1802652] Re: keyboard backlight not working on Asus GM501
The USB descriptor for the affected device: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x76,// Usage (0x76) 0xA1, 0x01,// Collection (Application) 0x85, 0x5A,// Report ID (90) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x05,// Report Count (5) 0x81, 0x00,// Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x3F,// Report Count (63) 0xB1, 0x00,// Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection 0x05, 0x0C,// Usage Page (Consumer) 0x09, 0x01,// Usage (Consumer Control) 0xA1, 0x01,// Collection (Application) 0x85, 0x02,// Report ID (2) 0x19, 0x00,// Usage Minimum (Unassigned) 0x2A, 0x3C, 0x02, // Usage Maximum (AC Format) 0x15, 0x00,// Logical Minimum (0) 0x26, 0x3C, 0x02, // Logical Maximum (572) 0x75, 0x10,// Report Size (16) 0x95, 0x02,// Report Count (2) 0x81, 0x00,// Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0xC0, // End Collection 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x79,// Usage (0x79) 0xA1, 0x01,// Collection (Application) 0x85, 0x5D,// Report ID (93) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x1F,// Report Count (31) 0x81, 0x00,// Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x3F,// Report Count (63) 0x91, 0x00,// Output (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x3F,// Report Count (63) 0xB1, 0x00,// Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x80,// Usage (0x80) 0xA1, 0x01,// Collection (Application) 0x85, 0x5E,// Report ID (94) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x05,// Report Count (5) 0x81, 0x00,// Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00,// Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00,// Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08,// Report Size (8) 0x95, 0x3F,// Report Count (63) 0xB1, 0x00,// Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection // 167 bytes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 Status in linux package in Ubuntu: Confirmed Bug description: The keyboard lights and most of the F keys aren't working. Kernel = 4.15.0-20-generic System linux mint 19 ls -hal /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 10 15:47 . drwxr-xr-x 72 root root 0 Nov 10 15:43 .. lrwxrwxrwx 1 root root 0 Nov 10 15:43 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Nov 10 15:47 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::scrolllock ->
[Kernel-packages] [Bug 1872635] Re: remove oem-5.4 from the archive
Removing packages from focal: linux-oem-5.4 5.4.0-1002.4 in focal linux-buildinfo-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 linux-headers-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 linux-image-unsigned-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 linux-modules-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal amd64 linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal arm64 linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal armhf linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal i386 linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal ppc64el linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal riscv64 linux-oem-5.4-headers-5.4.0-1002 5.4.0-1002.4 in focal s390x linux-oem-5.4-tools-5.4.0-1002 5.4.0-1002.4 in focal amd64 linux-oem-5.4-tools-common 5.4.0-1002.4 in focal amd64 linux-oem-5.4-tools-common 5.4.0-1002.4 in focal arm64 linux-oem-5.4-tools-common 5.4.0-1002.4 in focal armhf linux-oem-5.4-tools-common 5.4.0-1002.4 in focal i386 linux-oem-5.4-tools-common 5.4.0-1002.4 in focal ppc64el linux-oem-5.4-tools-common 5.4.0-1002.4 in focal riscv64 linux-oem-5.4-tools-common 5.4.0-1002.4 in focal s390x linux-oem-5.4-tools-host 5.4.0-1002.4 in focal amd64 linux-oem-5.4-tools-host 5.4.0-1002.4 in focal arm64 linux-oem-5.4-tools-host 5.4.0-1002.4 in focal armhf linux-oem-5.4-tools-host 5.4.0-1002.4 in focal i386 linux-oem-5.4-tools-host 5.4.0-1002.4 in focal ppc64el linux-oem-5.4-tools-host 5.4.0-1002.4 in focal riscv64 linux-oem-5.4-tools-host 5.4.0-1002.4 in focal s390x linux-tools-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 Comment: superseded by linux-oem-5.6; LP: #1872635 1 package successfully removed. ** Changed in: linux-oem-5.4 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1872635 Title: remove oem-5.4 from the archive Status in linux-meta-oem-5.4 package in Ubuntu: Fix Released Status in linux-oem-5.4 package in Ubuntu: Fix Released Status in linux-restricted-modules-oem-5.4 package in Ubuntu: Fix Released Status in linux-signed-oem-5.4 package in Ubuntu: Fix Released Bug description: This is replaced by oem-5.6, so should be removed from the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.4/+bug/1872635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872635] Re: remove oem-5.4 from the archive
Removing packages from focal: linux-meta-oem-5.4 5.4.0.1002.4 in focal Comment: superseded by linux-meta-oem-5.6; LP: #1872635 1 package successfully removed. ** Changed in: linux-meta-oem-5.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1872635 Title: remove oem-5.4 from the archive Status in linux-meta-oem-5.4 package in Ubuntu: Fix Released Status in linux-oem-5.4 package in Ubuntu: Fix Released Status in linux-restricted-modules-oem-5.4 package in Ubuntu: Fix Released Status in linux-signed-oem-5.4 package in Ubuntu: Fix Released Bug description: This is replaced by oem-5.6, so should be removed from the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.4/+bug/1872635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872635] Re: remove oem-5.4 from the archive
Removing packages from focal: linux-restricted-modules-oem-5.4 5.4.0-1002.4 in focal linux-modules-nvidia-390-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 linux-modules-nvidia-390-oem-20.04 5.4.0-1002.4 in focal amd64 linux-modules-nvidia-440-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 Comment: superseded by linux-oem-5.6; LP: #1872635 1 package successfully removed. ** Changed in: linux-restricted-modules-oem-5.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1872635 Title: remove oem-5.4 from the archive Status in linux-meta-oem-5.4 package in Ubuntu: Fix Released Status in linux-oem-5.4 package in Ubuntu: Fix Released Status in linux-restricted-modules-oem-5.4 package in Ubuntu: Fix Released Status in linux-signed-oem-5.4 package in Ubuntu: Fix Released Bug description: This is replaced by oem-5.6, so should be removed from the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.4/+bug/1872635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872635] Re: remove oem-5.4 from the archive
Removing packages from focal: linux-signed-oem-5.4 5.4.0-1002.4 in focal linux-image-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64 Comment: superseded by linux-oem-5.6; LP: #1872635 1 package successfully removed. ** Changed in: linux-signed-oem-5.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1872635 Title: remove oem-5.4 from the archive Status in linux-meta-oem-5.4 package in Ubuntu: Fix Released Status in linux-oem-5.4 package in Ubuntu: Fix Released Status in linux-restricted-modules-oem-5.4 package in Ubuntu: Fix Released Status in linux-signed-oem-5.4 package in Ubuntu: Fix Released Bug description: This is replaced by oem-5.6, so should be removed from the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.4/+bug/1872635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
I noticed that after boot with badly initialized GPU idle power consumption is 2-2.5 higher than after normal boots. But this can be fixed by putting laptop to suspend and waking it. Therefore I've extended my workaround from #3 to this: [Service] Type=oneshot ExecCondition=/bin/sh -c "journalctl -fk | grep -Fm1 'amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser'" ExecStart=/usr/bin/echo 'Not good. Restarting display-manager' ExecStart=/usr/bin/systemctl restart display-manager.service ExecStart=/usr/bin/sleep 3 ExecStart=/usr/bin/echo 'Brief suspend to fix power consumption' # Note that mode has to be "mem". "freeze" does not fix power consumption. ExecStart=/usr/sbin/rtcwake --mode mem --seconds 3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Rajat Pandita: awesome, thanks for sharing! I came here to report that I too was experiencing this bug: GTX 1060, up-to-date Focal Fossa beta, NVidia 440 driver series, 5.4.0-24 kernel. Couldn't log in. Removing `splash` from grub's kernel parameters solved the issue, but adding `nvidia-drm.modeset=1` is a much better solution since it leaves the splash screen unaffected (so you get a nice-looking boot). Besides, I remember from using KDE on Archlinux that `nvidia-drm.modeset=1` is required to get decent performance from NVidia drivers on KDE (though on Ubuntu I'm using Gnome). The driver install script should really edit and update grub configuration accordingly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL
This bug was fixed in the package linux - 5.4.0-25.29 --- linux (5.4.0-25.29) focal; urgency=medium * focal/linux: 5.4.0-25.29 -proposed tracker (LP: #1873459) * [TGL] VMD support in TGL (LP: #1855954) - PCI: vmd: Add bus 224-255 restriction decode - PCI: vmd: Add device id for VMD device 8086:9A0B * Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake (LP: #1871812) - ahci: Add Intel Comet Lake PCH RAID PCI ID -- Seth Forshee Fri, 17 Apr 2020 08:41:16 -0500 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855954 Title: [TGL] VMD support in TGL Status in HWE Next: New Status in intel: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Bug description: [SRU Justification] [Impact] On platforms with VMD support, block devices won't be scanned if VMD controller is not previously probed. [Fix] Two commits from v5.5-rc1 to be backported. [Test Case] On platforms with VMD support, boot with prebuilt kernel and check if Intel Volume Management Device appears among PCI devices: $ lspci | grep 'Volume Management Device' :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller [Regression Potential] Low. This only enables VMD controller on platforms with such device. == original description == Description: VMD support in Tiger Lake Platform Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake
This bug was fixed in the package linux - 5.4.0-25.29 --- linux (5.4.0-25.29) focal; urgency=medium * focal/linux: 5.4.0-25.29 -proposed tracker (LP: #1873459) * [TGL] VMD support in TGL (LP: #1855954) - PCI: vmd: Add bus 224-255 restriction decode - PCI: vmd: Add device id for VMD device 8086:9A0B * Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake (LP: #1871812) - ahci: Add Intel Comet Lake PCH RAID PCI ID -- Seth Forshee Fri, 17 Apr 2020 08:41:16 -0500 ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871812 Title: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: === SRU Justification === [Impact] ID is missing so the devcie isn't bound to AHCI driver. Without the driver, we can't check the existence of remapped NVMe. [Fix] Add one missing ID. [Test] Use lspci to see if the device is bound to ahci driver. Test positive after applying the patch. [Regression Potential] Low. This is a trivial fix which limits to one specific device. === Original Bug Report === Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
I did a bisect for this bug, now it is weekend and I was able to do tests on this computer. The bisect result is: 51d69817519f5f00041a1a039277f0367d76c82c is the first new commit commit 51d69817519f5f00041a1a039277f0367d76c82c Merge: 0174cb6ce944 f3efc406d67e Author: Linus Torvalds Date: Wed Jan 15 11:30:50 2020 -0800 Merge tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86 Pull x86 platform driver fixes from Andy Shevchenko: - Fix keyboard brightness control for ASUS laptops - Better handling parameters of GPD pocket fan module to avoid thermal shock - Add IDs to PMC platform driver to support Intel Comet Lake - Fix potential dead lock in Mellanox TM FIFO driver and ABI documentation * tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86: Documentation/ABI: Add missed attribute for mlxreg-io sysfs interfaces Documentation/ABI: Fix documentation inconsistency for mlxreg-io sysfs interfaces platform/x86: asus-wmi: Fix keyboard brightness cannot be set to 0 platform/x86: intel_pmc_core: update Comet Lake platform driver platform/x86: GPD pocket fan: Allow somewhat lower/higher temperature limits platform/x86: GPD pocket fan: Use default values when wrong modparams are given platform/mellanox: fix potential deadlock in the tmfifo driver platform/x86: intel-ips: Use the correct style for SPDX License Identifier Documentation/ABI/stable/sysfs-driver-mlxreg-io | 13 ++-- drivers/platform/mellanox/mlxbf-tmfifo.c| 19 - drivers/platform/x86/asus-wmi.c | 8 +--- drivers/platform/x86/gpd-pocket-fan.c | 27 ++--- drivers/platform/x86/intel_ips.h| 2 +- drivers/platform/x86/intel_pmc_core.h | 2 +- drivers/platform/x86/intel_pmc_core_pltdrv.c| 2 ++ 7 files changed, 46 insertions(+), 27 deletions(-) Which is unexpected to me, as it seems there is nothing related to i915. However, the computer really doesn't crash after this commit. The bisect log is below. Some of the kernels crash my computer in seconds: $ git bisect log git bisect start # old: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4 git bisect old 219d54332a09e8d8741c1e1982f5eae56099de85 # new: [d5226fa6dbae0569ee43ecfc08bdcd6770fc4755] Linux 5.5 git bisect new d5226fa6dbae0569ee43ecfc08bdcd6770fc4755 # old: [8c39f71ee2019e77ee14f88b1321b2348db51820] Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net git bisect old 8c39f71ee2019e77ee14f88b1321b2348db51820 # old: [76bb8b05960c3d1668e6bee7624ed886cbd135ba] Merge tag 'kbuild-v5.5' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild git bisect old 76bb8b05960c3d1668e6bee7624ed886cbd135ba # old: [018e0e3594f7dcd029d258e368c485e742fa9cdb] habanalabs: rate limit error msg on waiting for CS git bisect old 018e0e3594f7dcd029d258e368c485e742fa9cdb # old: [ec34c0157580a68c10dccbdd18c7701f0b317172] Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf git bisect old ec34c0157580a68c10dccbdd18c7701f0b317172 # new: [51d69817519f5f00041a1a039277f0367d76c82c] Merge tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86 git bisect new 51d69817519f5f00041a1a039277f0367d76c82c # old: [b07f636fca1c8fbba124b0082487c0b3890a0e0c] Merge tag 'tpmdd-next-20200108' of git://git.infradead.org/users/jjs/linux-tpmdd git bisect old b07f636fca1c8fbba124b0082487c0b3890a0e0c # old: [658e1af5eec6d51f95fa81e61f67d2fe1c6376aa] Merge tag 'thermal-v5.5-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux git bisect old 658e1af5eec6d51f95fa81e61f67d2fe1c6376aa # old: [213356fe986faff3580f2c12c14773f53da32768] Merge tag 'usb-5.5-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb git bisect old 213356fe986faff3580f2c12c14773f53da32768 # old: [2fe20210fc5f5e62644678b8f927c49f2c6f42a7] mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid git bisect old 2fe20210fc5f5e62644678b8f927c49f2c6f42a7 # old: [452424cdcbcaf6a2ebaae4301da5a4e1850a941a] Merge branch 'parisc-5.5-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux git bisect old 452424cdcbcaf6a2ebaae4301da5a4e1850a941a # old: [0174cb6ce9449ce9b59cb9c6f4f64dc4df3de458] Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 git bisect old 0174cb6ce9449ce9b59cb9c6f4f64dc4df3de458 # old: [1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3] platform/x86: GPD pocket fan: Allow somewhat lower/higher temperature limits git bisect old 1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3 # old: [176a7fca81c5090a7240664e3002c106d296bf31] platform/x86: asus-wmi: Fix keyboard brightness cannot be set to 0 git bisect old 176a7fca81c5090a7240664e3002c106d296bf31 # old: [f3efc406d67e6236b513c4302133b0c9be74fd99]
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I’ve had the same problem during installation Ubuntu 20.04 Beta and last daily release. I’m not sure if it’s necessary but my PC spec is Intel i9 9900k/RTX2080Ti. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
After doing some research I'm quite sure that this bug was introduced by [1] in the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel. The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's the case on my machine [3] and Heiner Kallweit also pointed in this direction [4]. The only thing that doesn't fit in this picture is that adding realtek to /etc/modules fixed the problem for Ryan. But it didn't fix the problem for me. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.32=791c420f42289fe9afed9e325c6b21eb6a5a329e [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.32=3fcd53b1d859799686a08785afb8990566c31cfa [3] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873552 [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873512/comments/20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873684] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873684 Title: bug #1320282 Status in linux package in Ubuntu: Confirmed Bug description: Computer restarts when i tell it shutdown. Does not happen when shutdown from grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-96-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Apr 19 17:45:43 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 10AAS26000 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=93704773-d4bc-4268-acb0-35d5acc4a037 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT87AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD or WIN 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:bvnLENOVO:bvrFBKT87AUS:bd05/09/2014:svnLENOVO:pn10AAS26000:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50512STDorWIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 10AAS26000 dmi.product.version: ThinkCentre M93p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873684] [NEW] bug #1320282
Public bug reported: Computer restarts when i tell it shutdown. Does not happen when shutdown from grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-96-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Apr 19 17:45:43 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 10AAS26000 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=93704773-d4bc-4268-acb0-35d5acc4a037 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT87AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD or WIN 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:bvnLENOVO:bvrFBKT87AUS:bd05/09/2014:svnLENOVO:pn10AAS26000:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50512STDorWIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 10AAS26000 dmi.product.version: ThinkCentre M93p dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873684 Title: bug #1320282 Status in linux package in Ubuntu: New Bug description: Computer restarts when i tell it shutdown. Does not happen when shutdown from grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-96-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Apr 19 17:45:43 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 10AAS26000 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=93704773-d4bc-4268-acb0-35d5acc4a037 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware
[Kernel-packages] [Bug 1873677] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873677 Title: Lenovo Ideapad S145 - Touchpad not recognized at all Status in linux package in Ubuntu: Confirmed Bug description: Touchpad not working and does not show in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hockenberry 1405 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 18:55:43 2020 InstallationDate: Installed on 2020-04-14 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=13de703e-a708-4fe2-a00d-136215c4176a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873644] Re: Regression in 5.4.0-24 kernel, r8169 network driver is broken
*** This bug is a duplicate of bug 1871182 *** https://bugs.launchpad.net/bugs/1871182 Should be fixed by: net: phy: realtek: fix handling of RTL8105e-integrated PHY ** This bug has been marked a duplicate of bug 1871182 [RTL810xE] No ethernet connection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873644 Title: Regression in 5.4.0-24 kernel, r8169 network driver is broken Status in linux package in Ubuntu: Incomplete Bug description: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873677] [NEW] Lenovo Ideapad S145 - Touchpad not recognized at all
Public bug reported: Touchpad not working and does not show in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hockenberry 1405 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 18:55:43 2020 InstallationDate: Installed on 2020-04-14 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=13de703e-a708-4fe2-a00d-136215c4176a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO ** Affects: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1873677 Title: Lenovo Ideapad S145 - Touchpad not recognized at all Status in linux package in Ubuntu: New Bug description: Touchpad not working and does not show in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hockenberry 1405 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 18:55:43 2020 InstallationDate: Installed on 2020-04-14 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=13de703e-a708-4fe2-a00d-136215c4176a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Did a Fresh Install today, and Selected the option to automatically install proprietary drivers, Something changed and my Installation Failed, I got a message saying that there was already a bug for that, I followed along and updated my situation in that bug report, because why not, It is just a 2 Minute Job. So this time around I changed the kernel parameters before installing Nvidia Drivers using the ubuntu-drivers autoinstall command. I edited by /etc/default/grub and I added nvidia-drm.modeset=1, Did not remove splash or any other parameters. I then ran sudo ubuntu-drivers autoinstall and waited for that to finish, Once done, I ran sudo update-grub. Then rebooted. This way I now have the flicker free boot/Animation and I can get into the desktop without any issues, GDM autologin works absolutely fine. I rebooted again just to be sure, and things stayed good. I wanted to update here so others can benefit while the bug is addressed. This is a working solution for me. I have a GTX 1070 CPU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz
[Kernel-packages] [Bug 1873673] Re: Kernel Error IRQ
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356793/+files/syslog.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873673 Title: Kernel Error IRQ Status in linux package in Ubuntu: Confirmed Bug description: Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0 - one with an external HD connected, and one USB-C) I noted that the mouse and keyboard using one Logitech Unifying receiver (connected through USB on the Laptop, not dock) started to jump over the screen and responded bad. I noted on dmesg the following error: [ 464.663455] [ cut here ] [ 464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled interrupts [ 464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core wmi_bmof serio_raw snd_rawmidi [ 464.663564] elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel [ 464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P O 5.4.0-24-lowlatency #28-Ubuntu [ 464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 ) 01/15/2020 [ 464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 [ 464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286 [ 464.663647] RAX: RBX: 97bd37c54200 RCX: 0006 [ 464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0 [ 464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d [ 464.663653] R10: 0001eb4c R11: 0004 R12: 00a0 [ 464.663655] R13: R14: 97bd3825c700 R15: 0002 [ 464.663658] FS: () GS:97bd3c10() knlGS: [ 464.663661] CS: 0010 DS: ES: CR0: 80050033 [ 464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0 [ 464.663665] DR0: DR1: DR2: [ 464.663667] DR3: DR6: fffe0ff0 DR7: 0400 [ 464.663669] Call Trace: [ 464.663680] ? irq_finalize_oneshot.part.0+0xe0/0xe0 [ 464.663686] handle_irq_event_percpu+0x33/0x80 [ 464.663692] handle_irq_event+0x39/0x58 [ 464.663697] handle_simple_irq+0x6f/0xa0 [ 464.663703] generic_handle_irq+0x28/0x40 [ 464.663709] i2c_handle_smbus_host_notify+0x28/0x40 [ 464.663717] i801_isr+0x1ee/0x300 [i2c_i801] [ 464.663724] irq_forced_thread_fn+0x33/0x80 [ 464.663729] irq_thread+0xda/0x170 [ 464.663736] ? wake_threads_waitq+0x30/0x30 [ 464.663741] kthread+0x104/0x140 [ 464.663747] ? irq_thread_check_affinity+0xe0/0xe0 [ 464.663750] ? kthread_park+0x90/0x90 [ 464.663757] ret_from_fork+0x35/0x40 [
[Kernel-packages] [Bug 1873673] [NEW] Kernel Error IRQ
Public bug reported: Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0 - one with an external HD connected, and one USB-C) I noted that the mouse and keyboard using one Logitech Unifying receiver (connected through USB on the Laptop, not dock) started to jump over the screen and responded bad. I noted on dmesg the following error: [ 464.663455] [ cut here ] [ 464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled interrupts [ 464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core wmi_bmof serio_raw snd_rawmidi [ 464.663564] elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel [ 464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P O 5.4.0-24-lowlatency #28-Ubuntu [ 464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 ) 01/15/2020 [ 464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 [ 464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286 [ 464.663647] RAX: RBX: 97bd37c54200 RCX: 0006 [ 464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0 [ 464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d [ 464.663653] R10: 0001eb4c R11: 0004 R12: 00a0 [ 464.663655] R13: R14: 97bd3825c700 R15: 0002 [ 464.663658] FS: () GS:97bd3c10() knlGS: [ 464.663661] CS: 0010 DS: ES: CR0: 80050033 [ 464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0 [ 464.663665] DR0: DR1: DR2: [ 464.663667] DR3: DR6: fffe0ff0 DR7: 0400 [ 464.663669] Call Trace: [ 464.663680] ? irq_finalize_oneshot.part.0+0xe0/0xe0 [ 464.663686] handle_irq_event_percpu+0x33/0x80 [ 464.663692] handle_irq_event+0x39/0x58 [ 464.663697] handle_simple_irq+0x6f/0xa0 [ 464.663703] generic_handle_irq+0x28/0x40 [ 464.663709] i2c_handle_smbus_host_notify+0x28/0x40 [ 464.663717] i801_isr+0x1ee/0x300 [i2c_i801] [ 464.663724] irq_forced_thread_fn+0x33/0x80 [ 464.663729] irq_thread+0xda/0x170 [ 464.663736] ? wake_threads_waitq+0x30/0x30 [ 464.663741] kthread+0x104/0x140 [ 464.663747] ? irq_thread_check_affinity+0xe0/0xe0 [ 464.663750] ? kthread_park+0x90/0x90 [ 464.663757] ret_from_fork+0x35/0x40 [ 464.663763] ---[ end trace 73ff5361b8214bea ]--- NOTES: Ubuntu Focal just installed, enabled the thunderbolt and allow it (I had to poweroff the laptop, otherwise the External displays connected to the Thunderbolt did not work) NOTE: The mouse is still making jumps and does not respond when I perform a file transfer from the Dock USB external drive (big files that take long to copy). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Kernel-packages] [Bug 1873673] Re: Kernel Error IRQ
** Attachment added: "lsusb --tree -vv" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356792/+files/lsusb-tree-vv.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873673 Title: Kernel Error IRQ Status in linux package in Ubuntu: Confirmed Bug description: Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0 - one with an external HD connected, and one USB-C) I noted that the mouse and keyboard using one Logitech Unifying receiver (connected through USB on the Laptop, not dock) started to jump over the screen and responded bad. I noted on dmesg the following error: [ 464.663455] [ cut here ] [ 464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled interrupts [ 464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core wmi_bmof serio_raw snd_rawmidi [ 464.663564] elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel [ 464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P O 5.4.0-24-lowlatency #28-Ubuntu [ 464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 ) 01/15/2020 [ 464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 [ 464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286 [ 464.663647] RAX: RBX: 97bd37c54200 RCX: 0006 [ 464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0 [ 464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d [ 464.663653] R10: 0001eb4c R11: 0004 R12: 00a0 [ 464.663655] R13: R14: 97bd3825c700 R15: 0002 [ 464.663658] FS: () GS:97bd3c10() knlGS: [ 464.663661] CS: 0010 DS: ES: CR0: 80050033 [ 464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0 [ 464.663665] DR0: DR1: DR2: [ 464.663667] DR3: DR6: fffe0ff0 DR7: 0400 [ 464.663669] Call Trace: [ 464.663680] ? irq_finalize_oneshot.part.0+0xe0/0xe0 [ 464.663686] handle_irq_event_percpu+0x33/0x80 [ 464.663692] handle_irq_event+0x39/0x58 [ 464.663697] handle_simple_irq+0x6f/0xa0 [ 464.663703] generic_handle_irq+0x28/0x40 [ 464.663709] i2c_handle_smbus_host_notify+0x28/0x40 [ 464.663717] i801_isr+0x1ee/0x300 [i2c_i801] [ 464.663724] irq_forced_thread_fn+0x33/0x80 [ 464.663729] irq_thread+0xda/0x170 [ 464.663736] ? wake_threads_waitq+0x30/0x30 [ 464.663741] kthread+0x104/0x140 [ 464.663747] ? irq_thread_check_affinity+0xe0/0xe0 [ 464.663750] ? kthread_park+0x90/0x90 [ 464.663757]
[Kernel-packages] [Bug 1873673] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873673 Title: Kernel Error IRQ Status in linux package in Ubuntu: Confirmed Bug description: Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0 - one with an external HD connected, and one USB-C) I noted that the mouse and keyboard using one Logitech Unifying receiver (connected through USB on the Laptop, not dock) started to jump over the screen and responded bad. I noted on dmesg the following error: [ 464.663455] [ cut here ] [ 464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled interrupts [ 464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core wmi_bmof serio_raw snd_rawmidi [ 464.663564] elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel [ 464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P O 5.4.0-24-lowlatency #28-Ubuntu [ 464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 ) 01/15/2020 [ 464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 [ 464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286 [ 464.663647] RAX: RBX: 97bd37c54200 RCX: 0006 [ 464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0 [ 464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d [ 464.663653] R10: 0001eb4c R11: 0004 R12: 00a0 [ 464.663655] R13: R14: 97bd3825c700 R15: 0002 [ 464.663658] FS: () GS:97bd3c10() knlGS: [ 464.663661] CS: 0010 DS: ES: CR0: 80050033 [ 464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0 [ 464.663665] DR0: DR1: DR2: [ 464.663667] DR3: DR6: fffe0ff0 DR7: 0400 [ 464.663669] Call Trace: [ 464.663680] ? irq_finalize_oneshot.part.0+0xe0/0xe0 [ 464.663686] handle_irq_event_percpu+0x33/0x80 [ 464.663692] handle_irq_event+0x39/0x58 [ 464.663697] handle_simple_irq+0x6f/0xa0 [ 464.663703] generic_handle_irq+0x28/0x40 [ 464.663709] i2c_handle_smbus_host_notify+0x28/0x40 [ 464.663717] i801_isr+0x1ee/0x300 [i2c_i801] [ 464.663724] irq_forced_thread_fn+0x33/0x80 [ 464.663729] irq_thread+0xda/0x170 [ 464.663736] ? wake_threads_waitq+0x30/0x30 [ 464.663741] kthread+0x104/0x140 [ 464.663747] ? irq_thread_check_affinity+0xe0/0xe0 [ 464.663750] ? kthread_park+0x90/0x90 [ 464.663757] ret_from_fork+0x35/0x40 [ 464.663763] ---[ end trace 73ff5361b8214bea
[Kernel-packages] [Bug 1872856] Re: whole system freezes frequently
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872856
Title:
whole system freezes frequently
Status in linux-meta package in Ubuntu:
Confirmed
Bug description:
version_signature -> Ubuntu 5.3.0-48.41-generic 5.3.18
uname-a -> Linux work 5.3.0-48-generic #41-Ubuntu SMP Fri Apr 10 06:59:18 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
dmesg and lspci logs attached.
$> lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
The problem is with the kernel versions 5.3.0-48-generic, 5.3.0-46-generic,
and 5.3.0-45-generic.
Kernel version 5.3.0-42-generic is working fine.
Steps to reproduce:
Download some Java project (say, https://github.com/yegor256/cactoos/)
Open this Java project in IntellijIdea community version
(https://www.jetbrains.com/idea/)
Type Ctrl+Shift+f (to search for all the files in a project)
This freezes the system for 7-8 seconds.
Similar behavior was seen when browsing firefox and or switching
windows (Alt+Tab). But not that easy to reproduce.
The problem does not occur when running heavy memory task (i.e.
stress-ng --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2 * 0.9;}'
< /proc/meminfo)k --vm-keep -m 1)
The problem does not occur when running heavy cpu task (i.e. sudo
stress-ng --cpu 8 --timeout 60 --metrics-brief)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1872856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855954 Title: [TGL] VMD support in TGL Status in HWE Next: New Status in intel: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Bug description: [SRU Justification] [Impact] On platforms with VMD support, block devices won't be scanned if VMD controller is not previously probed. [Fix] Two commits from v5.5-rc1 to be backported. [Test Case] On platforms with VMD support, boot with prebuilt kernel and check if Intel Volume Management Device appears among PCI devices: $ lspci | grep 'Volume Management Device' :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller [Regression Potential] Low. This only enables VMD controller on platforms with such device. == original description == Description: VMD support in Tiger Lake Platform Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th
usbcore.quirks=056a:5146:m also failed for me (with 19.10 and focal); I read on the Arch wiki that disabling Thunderbolt in the bios (under Security -> IO ports) might work and tried it, and it worked! I imagine this breaks Thunderbolt, but have no way to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836176 Title: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: As described above. With the last BIOS-updates Lenovo enabled proper S3 deep sleep mode for Linux. Sadly the touchscreen doesn't work after resuming. There are a lot of others facing the same problem: https://forums.lenovo.com/t5/Other-Linux-Discussions/X1Y3-Touchscreen- not-working-after-resume-on-Linux/td-p/4021200/highlight/false A workaround described in the Arch-wiki doesn't seem to work on Ubuntu: https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Yoga_(Gen_3)#Fix_touchscreen_after_resume ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 4186 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 11:19:05 2019 HibernationDevice: RESUME=UUID=1c3b8070-c343-4dbf-8fe2-4112233d7954 InstallationDate: Installed on 2018-11-30 (222 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20LES01W00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=d887a86a-3729-4962-9692-d9db9d49ed4c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-14 (87 days ago) dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET49W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET49W(1.35):bd06/12/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873552] Re: No wired network since 5.4.0-24 (r8169)
*** This bug is a duplicate of bug 1871182 *** https://bugs.launchpad.net/bugs/1871182 So now I build a kernel based on 5.4.0-24-generic with [1] on top of it and it indeed fixed the problem for me. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.32=3fcd53b1d859799686a08785afb8990566c31cfa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873552 Title: No wired network since 5.4.0-24 (r8169) Status in linux package in Ubuntu: Confirmed Bug description: Since kernel version 5.4.0-24 there is no wired network interface (eth0) on my dell-laptop. With 5.4.0-21 it still worked. My network interface: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 05) dmesg | grep r8 [0.102496] percpu: Embedded 54 pages/cpu s184320 r8192 d28672 u262144 [0.102507] pcpu-alloc: s184320 r8192 d28672 u262144 alloc=1*2097152 [1.181324] r8169 :01:00.0: can't disable ASPM; OS doesn't have ASPM control [1.185944] libphy: r8169: probed [1.185948] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? [1.205058] r8169: probe of :01:00.0 failed with error -49 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 10:42:37 2020 InstallationDate: Installed on 2013-04-06 (2568 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328) MachineType: Dell Inc. Inspiron 3521 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=839ab8e7-b938-4031-b40a-8304aaf855b3 ro video.use_native_backlight=1 quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to focal on 2020-04-15 (2 days ago) dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0010T1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron3521:pvrA14:rvnDellInc.:rn0010T1:rvrA00:cvnDellInc.:ct8:cvrA14: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
No amelioration with Ubuntu 20.04 beta. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873644] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1873644 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873644 Title: Regression in 5.4.0-24 kernel, r8169 network driver is broken Status in linux package in Ubuntu: Incomplete Bug description: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873644] Re: Regression in 5.4.0-24 kernel, r8169 network driver is broken
Another important note: this module is included to initramfs so this "fix" fixes nothing, in fact breaks stuff ** Changed in: linux (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/1873644 Title: Regression in 5.4.0-24 kernel, r8169 network driver is broken Status in linux package in Ubuntu: Incomplete Bug description: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Still present in the nvidia-graphics-drivers-440 package, sigh. To reproduce, it's still as simple as "Start playing a video with VLC in user #1, switch to user #2 for a couple of seconds, switch back to user #2 to see a black screen in VLC and hundreds of megabytes of error messages in the logs". It still doesn't happen with VLC in a PC with an AMD card doing the graphics acceleration. Syslog: Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. (those two repeated at least 90,000 times a second) Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: video surface destruction failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: message repeated 3 times: [ video surface destruction failure: An invalid handle value was provided.] Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: [7f6ead8e1730] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Apr 19 12:21:14 punch org.mate.panel.applet.MateMenuAppletFactory[5505]: video surface destruction failure: An invalid handle value was provided. Apr 19 12:21:14 punch kernel: [ 842.264228] show_signal_msg: 40 callbacks suppressed Apr 19 12:21:14 punch kernel: [ 842.264230] vlc[5545]: segfault at 8c ip 7f6ea7908be0 sp 7f6ea991f338 error 4 in libnvidia-glcore.so.440.64[7f6ea6a2a000+12de000] Apr 19 12:21:14 punch kernel: [ 842.264236] Code: fa ff 48 8b 05 c1 50 e0 00 48 83 c0 10 48 89 45 00 48 8b 5c 24 08 48 8b 6c 24 10 48 83 c4 18 c3 90 90 90 90 90 90 90 90 90 90 <66> 83 bf 8c 00 00 00 00 b8 01 00 00 00 75 20 30 c0 f6 87 8a 00 00 Apr 19 12:21:14 punch systemd[1]: Starting Process error reports when automatic reporting is enabled... Apr 19 12:21:18 punch whoopsie[1727]: [12:21:18] Parsing /var/crash/_usr_bin_vlc.1000.crash. Apr 19 12:21:18 punch whoopsie[1727]: [12:21:18] Uploading /var/crash/_usr_bin_vlc.1000.crash. ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873644] [NEW] Regression in 5.4.0-24 kernel, r8169 network driver is broken
Public bug reported: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: network r8169 ** Attachment added: "network-chip-data.txt" https://bugs.launchpad.net/bugs/1873644/+attachment/5356712/+files/network-chip-data.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/1873644 Title: Regression in 5.4.0-24 kernel, r8169 network driver is broken Status in linux package in Ubuntu: Incomplete Bug description: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873644] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1873644 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873644 Title: Regression in 5.4.0-24 kernel, r8169 network driver is broken Status in linux package in Ubuntu: Incomplete Bug description: No network connection since 5.4.0-24 kernel update, `dmesg` output contains the following unusual line: [2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? Important note: this module is available and listed in the `lsmod` output Possible cause is the following change: - r8169: fix PHY driver check on platforms w/o module softdeps https://paste.ubuntu.com/p/YcVx6jPndD/ No logs included bc I'm using the previous kernel build rn, so no point I guess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873645] [NEW] bluetooth
Public bug reported: bluetooth cannot connect ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 16:58:04 2020 InstallationDate: Installed on 2016-07-09 (1379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1873645 Title: bluetooth Status in linux-signed package in Ubuntu: New Bug description: bluetooth cannot connect ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 16:58:04 2020 InstallationDate: Installed on 2016-07-09 (1379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1873645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873641] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. Status in linux package in Ubuntu: Confirmed Bug description: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873641] Re: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Um, that should say I got a "single" report like this in syslog 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/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. Status in linux package in Ubuntu: New Bug description: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873641] [NEW] pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Public bug reported: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. Status in linux package in Ubuntu: New Bug description: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
https://patchwork.freedesktop.org/series/75941/ was merged as https://cgit.freedesktop.org/drm/drm- tip/commit/?id=0f8925090ac7ad451ed9e803662ebe3214dc8072 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: New Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828712] Re: I/O errors when trying to loop mount an image
Update: My `print_req_error: I/O error` errors went away after writing some files to the image, unmounting it and running `e2fsck -f` again. No errors reported from e2fsck but after I didn't get the print_req errors anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image Status in linux package in Ubuntu: Confirmed Bug description: Command sudo mount -t vfat flop1 /mnt/flop1 fails. The image is readable but the log shows many I/O errors such as May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read boot sector May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev loop0, sector 1 May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, logical block 1, async page read May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev loop0, sector 2 May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, logical block 2, async page read May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev loop0, sector 3 May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, logical block 3, async page read May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev loop0, sector 4 May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, logical block 4, async page read May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev loop0, sector 5 May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, logical block 5, async page read May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev loop0, sector 6 May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, logical block 6, async page read May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev loop0, sector 7 May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, logical block 7, async page read May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, logical block 1, async page read The command, understandably, reports "can't read superblock on /dev/loop0". The problem happens even on newly created images. Here's a sample set of commands and responses: $ mkfs.msdos -C flop1 1440 $ ls -l -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1 $ hd flop1 <--- output looks reasonable including 55 aa and two FATs ---> $ sudo mkdir /mnt/flop1 $ sudo mount -o loop flop1 /mnt/flop1 mount: /mnt/flop1: can't read superblock on /dev/loop0. $ losetup -f /dev/loop0 $ I see plenty of reports of similar on different websites but without resolution, including one on Launchpad but where the OP stopped responding so it did not get resolved. I don't know when this problem started to occur on this machine. If it's relevant, this is running under VirtualBox which reports itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host extensions' enabled. However, mounting a floppy image previously worked on this virtual machine. I have rebooted with /forcefsck to check the root (and only) filesystem. I have upgraded to the latest LTS Ubuntu, as below, but the problem persists. System info: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The machine is command-line only, i.e. no windowing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873578] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873578 Title: [WinBook TW102] Autorotation works but is backwards Status in iio-sensor-proxy package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics 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.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/iio-sensor-proxy/+bug/1873578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873578] Re: [WinBook TW102] Autorotation works but is backwards
** Summary changed: - Autorotation works but is backwards + [WinBook TW102] Autorotation works but is backwards ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: iio-sensor-proxy (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/1873578 Title: [WinBook TW102] Autorotation works but is backwards Status in iio-sensor-proxy package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics 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.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/iio-sensor-proxy/+bug/1873578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810636] Re: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
** Tags added: a2dp a2dp-skip ** Tags removed: cosmic ** Tags added: 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/1810636 Title: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810636] Re: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810636 Title: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810636] Re: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
** Summary changed: - Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing] + [Qualcomm Atheros QCA6174] Bluetooth audio choppiness ** Also affects: pulseaudio (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/1810636 Title: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873578] [NEW] [WinBook TW102] Autorotation works but is backwards
You have been subscribed to a public bug: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics 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.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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- [WinBook TW102] Autorotation works but is backwards https://bugs.launchpad.net/bugs/1873578 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853374] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1853374 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
