[Kernel-packages] [Bug 1989521] Re: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly
Can confirm happening to my reasonably new installation on server 22.04.3. Server isn't doing much, some dockers and a tp-link omada installation. Have null'd out the suspend options. Is anyone else also runing plex, after the soft lockup goes on for long enough I start getting these in my kern log. kern.log.1:Oct 18 03:43:24 nas kernel: [79118.116772] watchdog: BUG: soft lockup - CPU#8 stuck for 50271s! [PMS HttpClientC:311710] kern.log.1:Oct 18 03:43:24 nas kernel: [79118.117632] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:28 nas kernel: [79122.128665] watchdog: BUG: soft lockup - CPU#13 stuck for 50272s! [PMS GTP:141334] kern.log.1:Oct 18 03:43:28 nas kernel: [79122.129516] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:44 nas kernel: [79138.136234] watchdog: BUG: soft lockup - CPU#15 stuck for 50343s! [kworker/15:0:41010] kern.log.1:Oct 18 03:43:44 nas kernel: [79138.137125] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:52 nas kernel: [79146.100025] watchdog: BUG: soft lockup - CPU#0 stuck for 50297s! [PMS HttpServer:9967] kern.log.1:Oct 18 03:43:52 nas kernel: [79146.100894] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:52 nas kernel: [79146.108020] watchdog: BUG: soft lockup - CPU#4 stuck for 50297s! [PMS HttpServer:9968] kern.log.1:Oct 18 03:43:52 nas kernel: [79146.108933] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:52 nas kernel: [79146.116019] watchdog: BUG: soft lockup - CPU#8 stuck for 50297s! [PMS HttpClientC:311710] kern.log.1:Oct 18 03:43:52 nas kernel: [79146.116969] ? watchdog_timer_fn+0x1be/0x220 kern.log.1:Oct 18 03:43:56 nas kernel: [79150.127912] watchdog: BUG: soft lockup - CPU#13 stuck for 50298s! [PMS GTP:141334] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989521 Title: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Ubuntu server 22.04.1 is having issues freezing repeatedly with CPU softlocking. The issue seems to have started in the last week, all packages are up to date. I've updated to hwe kernel, rebooted several times, and it still happens. Hw info: 32G RAM, AMD 3600x CPU, Quadro RTX 4000 GPU. I caught the following in syslog : Sep 13 04:17:55 marcus-server kernel: [33687.436241] watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/u64:17:154214] Sep 13 04:17:55 marcus-server kernel: [33687.436243] Modules linked in: tls xt_nat veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink overlay bridge stp llc nvidia_drm(PO) snd_hda_codec_realtek intel_rapl_msr intel_rapl_common nvidia_modeset(PO) snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event zfs(PO) edac_mce_amd nls_iso8859_1 snd_rawmidi kvm_amd zunicode(PO) nvidia(PO) snd_seq kvm zzstd(O) zlua(O) zavl(PO) snd_seq_device icp(PO) rapl wmi_bmof snd_timer zcommon(PO) k10temp ccp ucsi_ccg znvpair(PO) snd typec_ucsi typec spl(O) soundcore apex(OE) gasket(OE) mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nct6775 hwmon_vid ipmi_devi ntf ipmi_msghandler msr parport_pc ppdev lp Sep 13 04:17:55 marcus-server kernel: [33687.436279] parport ramoops reed_solomon pstore_blk pstore_zone mtd efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nouveau mxm_wmi drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm aesni_intel video crypto_simd igb cryptd xhci_pci ahci dca i2c_piix4 i2c_nvidia_gpu arcmsr libahci xhci_pci_renesas i2c_algo_bit wmi Sep 13 04:17:55 marcus-server kernel: [33687.436302] CPU: 2 PID: 154214 Comm: kworker/u64:17 Tainted: P OE 5.15.0-47-generic #51-Ubuntu Sep 13 04:17:55 marcus-server kernel: [33687.436303] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Phantom Gaming 4, BIOS P4.20 08/02/2021 Sep 13 04:17:55 marcus-server kernel: [33687.436305] Workqueue: events_unbound async_run_entry_fn Sep 13 04:17:55 marcus-server kernel: [33687.436308] RIP: 0010:arcmsr_wait_firmware_ready+0xc1/0x140 [arcmsr] Sep 13 04:17:55 marcus-server kernel: [33687.436312] Code: e3 49 8b 94 24 48 08 00 00 b8 10 00 00 00 89 02 5b 41 5c 5d e9 b0 7b db e8 48 8b 47 50 4c 8d a0 bc 00 00 00 eb 0c 41 8b 04 24 <85> c0 0f 88 64 ff ff ff f6 83 81 00 00 00 01 75 eb bf 14 00 00 00 Sep 13 04:17:55
[Kernel-packages] [Bug 2028268] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
Thanks Juerg! I had the same issue with "pfring/8.0.0.7334". Removing it solved the issue! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025572] [NEW] Broadcom Wireless Drivers do not install properly as of Ubuntu 22.04
Public bug reported: When installing Broadcom Wireless driver (bcmwl-kernel-source) the package does not properly force the updating of the kernel module blacklist, and as a result the system still loads a conflicting driver (bcma). Users need to manually call the command: sudo update-initramfs -u Which correctly updates the blacklist allowing the Wireless adapter driver to load. On ubuntu versions 20.04 and earlier, installing the driver allows the network card to work immediately (no reboot require, it even works on the USB live distro). For version 22 and 23, it's possible to get it working by manually removing the b43 and bcma drivers, and then adding the wl driver, or running the above command. I'm filing this bug at the suggestion of an Ubuntu member who suggested that the bcmwl-kernel-source package should probably already be performing the update-initramfs command as part of it's installation. See Ubuntu Forums thread: https://ubuntuforums.org/showthread.php?t=248=2=14148921#post14148921 for more detail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: veleek 816 F wireplumber /dev/snd/controlC0: veleek 816 F wireplumber /dev/snd/seq:veleek 814 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Jul 2 15:19:26 2023 InstallationDate: Installed on 2023-06-30 (2 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Hewlett-Packard HP t620 Quad Core TC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=4c92a210-5f47-45e3-9ef4-fda0ed5c04a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-24-generic N/A linux-backports-modules-6.2.0-24-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2015 dmi.bios.release: 2.10 dmi.bios.vendor: AMI dmi.bios.version: L40 v02.10 dmi.board.name: 21B4 dmi.board.vendor: Hewlett-Packard dmi.board.version: A01 dmi.chassis.asset.tag: MXL62112RC 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:bvnAMI:bvrL40v02.10:bd07/03/2015:br2.10:svnHewlett-Packard:pnHPt620QuadCoreTC:pvr:rvnHewlett-Packard:rn21B4:rvrA01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuX1Y83UP#ABA: dmi.product.family: 103C_53302C G=D dmi.product.name: HP t620 Quad Core TC dmi.product.sku: X1Y83UP#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Broadcom Wireless Drivers do not install properly as of Ubuntu 20.X + Broadcom Wireless Drivers do not install properly as of Ubuntu 22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025572 Title: Broadcom Wireless Drivers do not install properly as of Ubuntu 22.04 Status in linux package in Ubuntu: New Bug description: When installing Broadcom Wireless driver (bcmwl-kernel-source) the package does not properly force the updating of the kernel module blacklist, and as a result the system still loads a conflicting driver (bcma). Users need to manually call the command: sudo update-initramfs -u Which correctly updates the blacklist allowing the Wireless adapter driver to load. On ubuntu versions 20.04 and earlier, installing the driver allows the network card to work immediately (no reboot require, it even works on the USB live distro). For version 22 and 23, it's possible to get it working by manually removing the b43 and bcma drivers, and then adding the wl driver, or running the above command. I'm filing this bug at the suggestion of an Ubuntu member who suggested that the bcmwl-kernel-source package should probably already be performing the update-initramfs command as part of it's installation. See Ubuntu Forums thread: https://ubuntuforums.org/showthread.php?t=248=2=14148921#post14148921 for more detail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: veleek 816 F wireplumber /dev/snd/controlC0: veleek 816 F wireplumber /dev/snd/seq:
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
Using the following kernel boot args: `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 i915.enable_dc=0 intel_idle.max_cstate=1"` So far I haven't got any issues waking from sleep. @Attila can you confirm if it works for you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp.
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
Thanks for posting @Attila. So it turns out I'm still getting the occasional freezing still also. I have found another kernel boot arg to try. `i915.enable_dc=0` I'm going to add this now and see if it helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
Can you try adding `intel_idle.max_cstate=1` kernel boot arg. So far it seems to have fixed the suspend-wakeup issue on AC power for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001:
[Kernel-packages] [Bug 2020917] Re: ethtool -m produces unreadable output for devices managed by the Intel ice driver
As suggested, this is indeed a bug in the ice kernel driver and not ethtool. Fixed by: commit 84cba1840e68430325ac133a11be06bfb2f7acd8 Author: Petr Oros Date: Wed Mar 1 21:47:07 2023 +0100 ice: copy last block omitted in ice_get_module_eeprom() ** Package changed: ethtool (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020917 Title: ethtool -m produces unreadable output for devices managed by the Intel ice driver Status in linux package in Ubuntu: Incomplete Bug description: We have a Supermicro X12SDV-8C-SP6F motherboard with a pair of SFP28 ports managed by an Intel E823-L for SFP controller. On this machine the SFP28 ports are eno3 and eno4. When asking ethtool for information about the installed SFP modules, we get this unhelpful output on Ubuntu Server 22.04 LTS: sudo ethtool --module-info eno3 Offset Values -- -- 0x: 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0a 64 0x0010: 00 00 00 00 46 53 20 20 20 20 20 20 20 20 20 20 0x0020: 20 20 20 20 00 00 1b 21 53 46 50 2d 31 30 47 4c 0x0030: 52 2d 33 31 20 20 20 20 41 20 20 20 05 1e 00 d3 0x0040: 00 3a 00 00 46 32 30 33 30 33 32 32 36 38 39 20 0x0050: 20 20 20 20 32 32 30 34 30 32 20 20 68 fa 02 f1 0x0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I suspect this is the same bug that was reported by Red Hat here (access requires a Red Hat account): https://access.redhat.com/solutions/6999793 This patch in netdev seems relevant: https://lore.kernel.org/netdev/20230228204139.2264495-1-po...@redhat.com/T/ If I understand that patch correctly, this might a netdev issue that was exposed by a change in ethtool. If that's the case, then it's possible this shouldn't be classified as an ethtool bug, but I figured I'd start here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ethtool 1:5.16-1 ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 26 17:29:58 2023 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error
Short: I think downloading the new headers worked for me: https://packages.ubuntu.com/lunar/kernel/ Long: Before installing the new headers I tried to remove the new headers to run on the old kernel. Running on the old kernel is possible by just picking it from GRUB, so this was probably unnecessary in the first place anyway. When doing it I ran into the problem of beeing unable to create metapackages (which I removed to beeing able to remove the new kernel headers). I was unable to install metapackages with the old version (for kinetic). So, I decided to go back to the newest setup and downloaded and installed the new headers (again). When I finally had all dependencies in my list the install went through without a problem. So, I suspect this is just a problem of compiling the new kernel, right? I did no final reboot of the system yet... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017267 Title: Release upgrade to lunar lobster linux-headers-6.2.0-20 post- installation error Status in linux package in Ubuntu: Confirmed Bug description: Ended with a dialog box: Could not install 'linux-headers-6.2.0-20-generic' The upgrade will continue but the 'linux-headers-6.2.0-20-generic' package may not be in a working state. Please consider submitting a bug report about it. installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash 644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 08:09:44 2023 InstallationDate: Installed on 2021-01-04 (836 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-kitty XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error
Same problem with Ubuntu when doing suggested upgrade from 22.10 to 23.04. I am running it in Virtualbox 7.0.6 r155176 on a Windows 10 host. I am unable to remove the broken kernel now (getting same error message). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017267 Title: Release upgrade to lunar lobster linux-headers-6.2.0-20 post- installation error Status in linux package in Ubuntu: Confirmed Bug description: Ended with a dialog box: Could not install 'linux-headers-6.2.0-20-generic' The upgrade will continue but the 'linux-headers-6.2.0-20-generic' package may not be in a working state. Please consider submitting a bug report about it. installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash 644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 08:09:44 2023 InstallationDate: Installed on 2021-01-04 (836 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-kitty XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Du ChengEn, thank-you for your additional comments. We are seeing good behaviour after the patch. However, (and please feel free to call me stupid) when you talk about user's login time, how does this reflect with system processes, such as www-data (apache2), or similar? Is a "login" for such users a systemctl start, restart or reload? I am asking specifically regarding access cache; our particular issue being apache2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Why is this not recognised as critical? We identified this as a major incident, with severe loss of service (availability) and likewise opening a risk assessment in relation to our dependency on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
A couple of days ago I upgraded my 21.10 system to 22.04 and got this "out of memory" issue (Dell XPS 15 9550 with 3840x2160 display). The fix in comment #41 worked (changing the compression to 19), and the sequence of commands in #44 helped. However, just noting that there are several typos in #44 that had me stumped for a while (it's the first time I've used chroot to update grub). So here are (I think!) the corrected commands to update grub: $ sudo su - # mkdir root # mkdir boot # mkdir efi # cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt # mount /dev/mapper/vgubuntu-root ./root # mount /dev/nvme0n1p1 ./efi # was "nvme01p1" # mount /dev/nvme0n1p2 ./boot # was "nvme01p2" # mount -B ./boot ./root/boot # mount -B ./efi ./root/boot/efi # mount -B /dev ./root/dev # was: mount -B ./dev ./root/boot/dev # mount -B /dev/pts ./root/dev/pts # was: mount -B ./dev/pts ./root/boot/dev/pts # mount -B /proc ./root/proc # was: mount -B ./proc ./root/proc # mount -B /sys ./root/sys # was: mount -B ./sys ./root/sys # chroot ./root # ### Now edit line 196 of /usr/sbin/mkinitramfs to to use -19 instead of -1 # update-initramfs -u -k all # update-grub # exit # reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Joseph, out of interest, what model of XPS 13 do you have? I'm getting new XPS 13 soon and wondering if it'll have the same issue (I guess it's likely given the 4k screen). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my
[Kernel-packages] [Bug 1962129] [NEW] wifi adapter driver does not work
Public bug reported: BCM43228 driver doesnt working in Ubuntu 20.04 version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 08:13:13 2022 InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-02-23T21:32:33.135380 ** Affects: bcmwl (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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1962129 Title: wifi adapter driver does not work Status in bcmwl package in Ubuntu: New Bug description: BCM43228 driver doesnt working in Ubuntu 20.04 version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 08:13:13 2022 InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-02-23T21:32:33.135380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1962129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown
Same issue for me with an ASUS PN-51 computer (CPU: Ryzen 5 5500U) with Ubuntu 21.10, currently running with kernel 5.13.0-27-generic. The older kernel 5.13.0-22 was not affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic, the system cannot be powered down or rebooted, just hangs indefinitely. A screenshot with the final screen is shown here: https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff I can restore the previous behavior (i.e. a correct shutdown) with choosing the previous kernel in the grub menu on boot. Is there anything I can do to provide more information and debug this further? My system information: Description: Ubuntu 21.10 Release: 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petr 1146 F pulseaudio /dev/snd/controlC0: petr 1146 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-07 (62 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgxubuntu-root ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
** Attachment added: "yet another journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557317/+files/bug3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly Status in linux package in Ubuntu: New Bug description: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
** Attachment added: "another journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557316/+files/bug2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly Status in linux package in Ubuntu: New Bug description: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958975] [NEW] linux-image-5.13.0-28-generic hangs randomly
Public bug reported: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish package-from-proposed wayland-session ** Attachment added: "bug1" https://bugs.launchpad.net/bugs/1958975/+attachment/5557296/+files/bug1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly Status in linux package in Ubuntu: New Bug description: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1933728] Re: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
This happened apparently without reasons after a reboot. Now my screen resolution is not detected properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1933728 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-50-generic Date: Sat Jun 5 15:09:53 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-04-06 (80 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1933728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
For me it looks like it is fixed in ppa 5.13.0-26.27 see: https://www.ubuntuupdates.org/package/canonical_kernel_team/impish/main/base/linux But I don't know if this means it is going to be fixed in the next main update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
linux/5.13.0-24.24 proposed fixed it for me on a ThinkPad L13 (non-Yoga) I had to install the linux-modules-extra to get wifi to work as well. I just changed from fedora to ubuntu three weeks ago (after an unwanted ssd replacement) and can now finally use my ubuntu notebook as it is supposed to be used (without an external mouse) thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze
Confirmed - this bug impacts the 21.10 installer of Ubuntu Budgie and appears like it is an upstream issue as well given I found this. This bug does not impact 20.04 installers. (could not find 21.04 installer, so not tested) Also I know initially I did not have this issue before I repartitioned with Minitool - I felt it was safer to repartition and move things around how I wanted from that tool first before proceeding and then the installer broke after after that. I ran diskcheck repairs from Windows and never found an issue either, so no idea what happened - but I am guessing some code change causes it to get hung up on something NTFS related when it shouldn't be. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: Incomplete Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze
I also get this error with Ubuntu Budgie 21.10, may try going to 21.04 and see if it changes. I think this is occurring due to the "ntfsresize tainted" error in the log - I do have Windows on half the partition and had used "MiniTool Partition Wizard to clear half the drive first. Might be a path to replicating the error. Step 1) Install Windows on half the drive. Step 2) Install Windows on the other half Step 3) Use MiniTool Partition Wizard and clear half the drive. Step 4) Attempt to install Ubuntu - If you get past the "Updates and other software" screen then go the recommended route and then click the go back button instead of confirming that you want to go forward. Step 5) Watch as every subsequent install fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: Incomplete Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I installed 21.10 with ZFS+encryption before this was fixed. Do I need to reformat and reinstall? Or is there a way to check for corruption on each zpool? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
I have disabled PSR by adding the kernel parameter to /etc/default/grub and running sudo update-grub before rebooting. It has been a few hours, and the screen flickering has not recurred as of yet. I'll keep you updated if that changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Upgraded to 20.10 running 5.8.0-1030-kvm and everything is fine again too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 80 0d
[Kernel-packages] [Bug 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot
I've tested the beta ISO without Secure Boot -- it still fails. I've also tested the beta ISO with a Gen1 (non-UEFI) Hyper-V VM, and it works fine! ** Description changed: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) - inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft - UEFI Certificate Authority) enabled. + inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). ** Summary changed: - hirsute beta desktop AMD64 ISO kernel panic on boot + hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
I am using the desktop ISO (both images). I've added to the bug description that the original ISO that I used was the beta ISO downloaded from this URL: http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso I validated the ISO checksum against the given checksum and verified the checksum file against the signing key. I downloaded the daily image on 04-05-2021 when the file had a last modified date of 04-05-2021 from this URL: https://cdimage.ubuntu.com /daily-live/current/hirsute-desktop-amd64.iso and it had the same issue. ** Summary changed: - hirsute live cd kernel panic on boot + hirsute beta desktop ISO kernel panic on boot ** Summary changed: - hirsute beta desktop ISO kernel panic on boot + hirsute beta desktop AMD64 ISO kernel panic on boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
** Description changed: - I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a - Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI - Certificate Authority) enabled. + I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; + http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) + inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft + UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
The 04-04-2021 daily ISO also has the same bug (screenshot attached). ** Attachment added: "ubuntu-hirsute-hippo-daily-livecd-kernelpanic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+attachment/5484139/+files/ubuntu-hirsute-hippo-daily-livecd-kernelpanic.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
(Obviously, I can't run apport-collect since it panics on boot.) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
** Summary changed: - hirsute live cd kernel panic + hirsute live cd kernel panic on boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot Status in linux package in Ubuntu: Incomplete Bug description: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic
changed to 'linux' to reflect that this is a kernel bug ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot Status in linux package in Ubuntu: New Bug description: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916988] Re: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade
this also works for 5.8.0.48 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916988 Title: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: After updating some packages which included a new version of kernel (5.8.0-44-generic) the internal microphone of my Lenovo Yoga Slim 7 does not work anymore and it doesn't seem to be recognized in Settings->Sound (I attached a screenshot) 1. ~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 2. ~# apt-cache policy linux-image-5.8.0-44-generic linux-image-5.8.0-44-generic: Installed: 5.8.0-44.50~20.04.1 Candidate: 5.8.0-44.50~20.04.1 Version table: *** 5.8.0-44.50~20.04.1 500 500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3. Expected internal microphone to work 4. Internal microphone not working --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1690 F pulseaudio /dev/snd/controlC0: stefan 1690 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=06bbabdd-494d-48b9-b17e-31cb56c8ff0f ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 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.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/18/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN38WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDMCN38WW:bd01/18/2020:br1.38:efr1.29:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1690 F pulseaudio /dev/snd/controlC0: stefan 1690 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: alsa-base 1.0.25+dfsg-0ubuntu5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: third-party-packages focal Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/18/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN38WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDMCN38WW:bd01/18/2020:br1.38:efr1.29:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 1918586] Re: File system becomes read only during upgrade
I'm not able to access these machines physically as I'm getting remote hands to do it as they are in different countries. I'm unlikely going to be able to get you enough information to investigate this issue. I'm having the devices wiped and reinstalled. Sorry about that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1918586 Title: File system becomes read only during upgrade Status in linux-firmware package in Ubuntu: Incomplete Bug description: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918586] [NEW] File system becomes read only during upgrade
Public bug reported: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "terminal.txt" https://bugs.launchpad.net/bugs/1918586/+attachment/5475612/+files/terminal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1918586 Title: File system becomes read only during upgrade Status in linux-firmware package in Ubuntu: New Bug description: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
I'm back to say that kernel 5.4.0-66-generic works for me again after applying the grub default `amdgpu.dc=0` work-around mentioned above. This is for a Radeon RX 580 if that helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle Status in linux package in Ubuntu: Confirmed Bug description: i updated today to linux kernel 5.4.0-66-generic. since then the monitor (HDMI) remains black when switched off and on again. this can be corrected once, if a virtual text console hasn't been used so far by switching to a virtual text console and then back to the desktop. Ubuntu 5.4.0-66.74-generic 5.4.86 (Linux Mint 20, Cinnamon 4.6.7) lspci-vnvn.log attached Asrock DeskMini A300 AMD Ryzen 5 2400G with Radeon Vega Graphics × 4 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kio1177 F pulseaudio /dev/snd/controlC1: kio1177 F pulseaudio /dev/snd/controlC0: kio1177 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-07-24 (216 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=c96f03d4-1951-4c06-8d5d-61bd5b22b308 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: ulyana Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.50 dmi.board.name: A300M-STX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd05/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA300M-STX:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
I can confirm I have the same issue. I've reverted the kernel back to 5.4.0-65 to temporarily solve the issue. I have all of the logs and details posted here: https://forums.linuxmint.com/viewtopic.php?f=59=343546=1977800#p1977800 The most important being: Feb 25 15:46:06 meritwork-linux kernel: [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! Feb 25 15:46:06 meritwork-linux kernel: [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle Status in linux package in Ubuntu: Confirmed Bug description: i updated today to linux kernel 5.4.0-66-generic. since then the monitor (HDMI) remains black when switched off and on again. this can be corrected once, if a virtual text console hasn't been used so far by switching to a virtual text console and then back to the desktop. Ubuntu 5.4.0-66.74-generic 5.4.86 (Linux Mint 20, Cinnamon 4.6.7) lspci-vnvn.log attached Asrock DeskMini A300 AMD Ryzen 5 2400G with Radeon Vega Graphics × 4 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kio1177 F pulseaudio /dev/snd/controlC1: kio1177 F pulseaudio /dev/snd/controlC0: kio1177 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-07-24 (216 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=c96f03d4-1951-4c06-8d5d-61bd5b22b308 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: ulyana Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.50 dmi.board.name: A300M-STX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd05/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA300M-STX:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
As of 5.8.0-40-generic (and possibly the previous version as well) this issue seems to be 100% resolved for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Just a note: in attempting to fix this issue I borked my laptop - after disabling UEFI boot and then re-enabling it in the BIOS settings, I couldn't boot at all. So I reinstalled Ubuntu and then was getting the following issue after doing system updates (but still on the 5.4 kernel): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320, which showed "error: out of memory" when GRUB was trying to hand over to the kernel. The fix (workaround) for that is to set GFXMODE=800x600 in the GRUB config. And now the software updates *and* the 5.8 kernel works fine ... which is kind of odd. It's possible that this issue was actually that one, just that we weren't seeing the error message because GRUB is set to hidden by default. Though that doesn't explain why the 5.4 kernel worked with software updates earlier ... still a bit of an unknown, so keeping this open for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Po
[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Just noting that I had this same issue on my Dell XPS 9550 laptop, which has a 3840x2160 display. The workaround of setting GFXMODE=800x600 in the grub config worked for me too, thanks! And of course had the nice side effect of actually making the grub menu readable. :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Charles, very interesting. Though I wonder if yours is a different problem, partly because it's not in tty mode at all (for me it's in a graphical mode, sometimes with the Dell logo up). I can't seem to switch to tty2 using Alt-F2 or Ctrl-Alt-F2 -- what are the exact keys you're using? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Good data point, thanks. It looks like there are some significant differences between the 9550 and the 9560 that could explain that: 1) Next generation CPU: i7-6700HQ on the 9550 vs i7-7700HQ on the 9560 2) Intel HD graphics 530 on the 9550 vs 630 on the 9560 3) NVIDIA GTX 960M on the 9550 vs NVIDIA GTX 1050 on the 9560 Reference: https://www.windowscentral.com/dell-xps-15-9550-vs- xps-15-9560-whats-different-and-should-you-upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
The kernel it's trying to run (assuming it's the top one in the "advanced options" boot list) is 5.8.0-36-generic. I run apport-collect in case it helps -- boy, that's noisy in terms of number of comments. :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452439/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452441/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452440/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452438/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452437/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452435/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452434/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452436/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452430/+files/Lsusb-t.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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452429/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452427/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452431/+files/Lsusb-v.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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452426/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452428/+files/Lspci-vt.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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452425/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452432/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452433/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452424/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
apport information ** Tags added: apport-collected ** Description changed: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ben4518 F pulseaudio + /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-27 (138 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. XPS 15 9550 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-59-generic N/A + linux-backports-modules-5.4.0-59-generic N/A + linux-firmware1.187.7 + Tags: focal + Uname: Linux 5.4.0-59-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/12/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.13.1 + dmi.board.name: 0N7TVV + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 15 9550 + dmi.product.sku: 06E4 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452423/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be
[Kernel-packages] [Bug 1911352] [NEW] Black screen on boot after 20.04 upgraded to kernel 5.8
Public bug reported: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs.zip" https://bugs.launchpad.net/bugs/1911352/+attachment/5452414/+files/logs.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: New Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908800] [NEW] Wireless card crashes daily on my XPS 13 9380
Public bug reported: Hello all, Daily, or multiple times per day, the wireless card on my XPS 13 9380 crashes, forcing me to shutdown my computer and then boot it back up. I am on Ubuntu 20.04, and here is the results from dmesg -T right after such a crash happens: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 170ee3ba-1809-4276-9b34-9d4e37da0937) [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: Copy Engine register dump: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [01]: 0x00034800 23 23 164 165 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [02]: 0x00034c00 31 30 93 94 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [03]: 0x00035000 20 20 22 20 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [04]: 0x00035400 4711 4707 114 50 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [06]: 0x00035c00 7 7 12 12 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [Sat Dec 19 15:08:59 2020] ieee80211 phy0: Hardware restart was requested [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: device successfully recovered lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.187.6 Candidate: 1.187.6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bsbrom 3384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 19 15:21:02 2020 Dependencies: InstallationDate: Installed on 2020-09-05 (105 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9380 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wxgq6h@/vmlinuz-5.4.0-58-generic root=ZFS=rpool/ROOT/ubuntu_wxgq6h ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/06/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908800 Title: Wireless card crashes daily on my XPS 13 9380 Status in linux-firmware package in Ubuntu: New Bug description: Hello all, Daily, or multiple times per day, the wireless card on my XPS 13 9380 crashes, forcing me to shutdown my computer and then boot it back up. I am on Ubuntu 20.04, and here is the results from dmesg -T right after such a crash happens: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 170ee3ba-1809-4276-9b34-9d4e37da0937) [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
[Kernel-packages] [Bug 1905327] Re: USB 1.1 scanner takes much time to start working
Same with the latest kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905327 Title: USB 1.1 scanner takes much time to start working Status in linux package in Ubuntu: Incomplete Bug description: I have an old Canon Lide30 scanner. Every time I plug it in, it does not work for 10 to 15 minutes. Then, I got the following lines in the dmesg log: [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.107489] xhci_hcd :02:00.0: WARN Successful completion on short TX [ 1168.107510] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xff8f6180 flags=0x0020] [ 1168.107710] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xf4f2b180 flags=0x0020] [ 1168.107729] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 1 After this lines, the scanner works perfectly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-55-generic 5.4.0-55.61 ProcVersionSignature: Ubuntu 5.4.0-55.61-generic 5.4.73 Uname: Linux 5.4.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 23:47:32 2020 InstallationDate: Installed on 2019-11-16 (373 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-55-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-55-generic N/A linux-backports-modules-5.4.0-55-generic N/A linux-firmware1.187.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (205 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H 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/1905327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Just tried the newly released 5.8.0-31-generic, but I'm still seeing the GPFs (see attached screenshot). I'm continuing to run with the mainline 5.9.10 kernel that I mentioned previously, not ideal since I had to switch to the upstream openzfs-2.0 release which supports the 5.9 kernel. ** Attachment added: "PXL_20201201_233259297.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5440157/+files/PXL_20201201_233259297.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Interestingly 5.9.10-050910-generic (from the mainline kernel ppa that was mentioned earlier) is booting and running stably. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Anything else I can try to further debug this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905327] [NEW] USB 1.1 scanner takes much time to start working
Public bug reported: I have an old Canon Lide30 scanner. Every time I plug it in, it does not work for 10 to 15 minutes. Then, I got the following lines in the dmesg log: [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.107489] xhci_hcd :02:00.0: WARN Successful completion on short TX [ 1168.107510] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xff8f6180 flags=0x0020] [ 1168.107710] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xf4f2b180 flags=0x0020] [ 1168.107729] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 1 After this lines, the scanner works perfectly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-55-generic 5.4.0-55.61 ProcVersionSignature: Ubuntu 5.4.0-55.61-generic 5.4.73 Uname: Linux 5.4.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 23:47:32 2020 InstallationDate: Installed on 2019-11-16 (373 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-55-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-55-generic N/A linux-backports-modules-5.4.0-55-generic N/A linux-firmware1.187.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (205 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H 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 package-from-proposed third-party-packages 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/1905327 Title: USB 1.1 scanner takes much time to start working Status in linux package in Ubuntu: New Bug description: I have an old Canon Lide30 scanner. Every time I plug it in, it does not work for 10 to 15 minutes. Then, I got the following lines in the dmesg log: [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.105302] xhci_hcd :02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 1168.107489] xhci_hcd :02:00.0: WARN Successful completion on short TX [ 1168.107510] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xff8f6180 flags=0x0020] [ 1168.107710] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xf4f2b180 flags=0x0020] [ 1168.107729] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 1 After this lines, the scanner works perfectly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-55-generic 5.4.0-55.61 ProcVersionSignature: Ubuntu 5.4.0-55.61-generic 5.4.73 Uname: Linux 5.4.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 23:47:32 2020 InstallationDate: Installed on 2019-11-16 (373 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Tried the recently released ubuntu linux kernel 5.8.29 just now, still getting the GPFs. Attaching the output of "journalctl -xb" from that failed boot (I was dropped into "emergency mode"). ** Attachment added: "journalctl -xb output from failed boot of ubuntu kernel 5.8.0-29" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5435819/+files/ubuntu-kernel-5.8.0-29.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
I am encountering this issue with my setup too after updating -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
OK, after a lot of kernel package installs and rebooting... Mainline kernel version 5.8.5-050805 boots and runs successfully. But the *next* version (5.8.6-050806) generally fails to boot, exhibiting the pattern of GPFs and occasional kernel panics. Once it booted up all the way, but the system hung shortly after booting up. Ubuntu kernel version 5.4.0.52-generic continues to be very reliable on this system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Mainline kernel version 5.8.0-050800-generic boots up without any issues. Mainline kernel version *5.8.18-050818-generic* doesn't (GPF and kernel panics). I'll work backwards from 5.8.18-050818-generic to see when the GPFs and kernel panics go away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
I updated GRUB_CMDLINE_LINUX_DEFAULT. I was able to boot to multiuser mode once (kernel boot log for that is attached, titled "kern.log.debug- successful"). The system locked up shortly after I stashed a copy of that log. ** Attachment added: "Successful boot of 5.8.0-28-generic (which subsequently locked up)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5434231/+files/kern.log.debug-successful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Subsequent attempts to boot the 5.8.0-28-generic kernel exhibited GPFs and at least one full kernel panic, screenshot of that is attached. Ubuntu kernel version 5.4.0-52-generic remains the only stable option at the moment. ** Attachment added: "kernel panic with 5.8.0-28-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5434232/+files/PXL_20201113_223208755.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Ah, according to the openzfs release notes, openzfs version 0.8.4 (the current version in the ubuntu repositories) isn't compatible with kernel versions later than 5.6. Presumably this is the issue. I guess I'll stick with kernel 5.4.x until update ZFS packages are 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/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
I was able to successfully boot with upstream kernel version: 5.10.0-051000rc3-generic This kernel package notably does not include the ZFS kernel modules (and those kernel modules did not build when I installed zfs-dkms). So it does seem possible that the bug I'm encountering relates to ubuntu kernel 5.8 and the various ZFS related kernel modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] [NEW] kernel 5.8 general protection fault at boot
Public bug reported: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "An example kern.log from a failed boot" https://bugs.launchpad.net/bugs/1904054/+attachment/5433880/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: New Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage
[Kernel-packages] [Bug 1881408] Re: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) cannot establish connection after Kernel update
Meanwhile I consider the problem being a bug in another software package than the kernel but I cannot clearly find out which one (maybe systemd or libnss related). ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881408 Title: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) cannot establish connection after Kernel update Status in linux package in Ubuntu: Invalid Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 After installing updates a week ago, the wifi connection could not connect anymore. Another (minor) problem is, that the machine reboots after shutting down. The same two problems occured some years ago (and went away) after kernel updates (I guess it was Ubuntu 16.04). When I boot Ubuntu 20.04 from USB, wifi works w/o problems. I'm not sure about the Kernel as cause for the problem, but here is the list of updated packages from the day, the problem occured: updated (24.05.): dmeventd (2:1.02.145-4.1ubuntu3.18.04.2) to 2:1.02.145-4.1ubuntu3.18.04.3 dmsetup (2:1.02.145-4.1ubuntu3.18.04.2) to 2:1.02.145-4.1ubuntu3.18.04.3 elmerfem-csc (8.4-0ppa0-202005180232~61b7f5c~ubuntu18.04.1) to 8.4-0ppa0-202005220929~d3ea5ba~ubuntu18.04.1 libdevmapper-event1.02.1 (2:1.02.145-4.1ubuntu3.18.04.2) to 2:1.02.145-4.1ubuntu3.18.04.3 libdevmapper1.02.1 (2:1.02.145-4.1ubuntu3.18.04.2) to 2:1.02.145-4.1ubuntu3.18.04.3 liblvm2app2.2 (2.02.176-4.1ubuntu3.18.04.2) to 2.02.176-4.1ubuntu3.18.04.3 liblvm2cmd2.02 (2.02.176-4.1ubuntu3.18.04.2) to 2.02.176-4.1ubuntu3.18.04.3 lvm2 (2.02.176-4.1ubuntu3.18.04.2) to 2.02.176-4.1ubuntu3.18.04.3 teamviewer (15.5.3) to 15.5.6 wine-devel (5.8~bionic) to 5.9~bionic wine-devel-amd64 (5.8~bionic) to 5.9~bionic wine-devel-i386:i386 (5.8~bionic) to 5.9~bionic winehq-devel (5.8~bionic) to 5.9~bionic removed (24.05.): linux-headers-5.3.0-46 linux-headers-5.3.0-46-generic linux-image-5.3.0-46-generic linux-modules-5.3.0-46-generic linux-modules-extra-5.3.0-46-generic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben2094 F pulseaudio /dev/snd/controlC0: ben2094 F pulseaudio /dev/snd/pcmC0D0p: ben2094 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=9adebd2f-9c8c-4995-ad39-3e78503ee9a3 InstallationDate: Installed on 2019-02-02 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=929f22b6-14b8-433c-b0ba-0b1d2e5272ab ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X79-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF16:bd09/05/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrTobefilledbyO.E.M.: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. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben2188 F pulseaudio /dev/snd/controlC0: ben2188 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Noticed that I couldn't use my headset mic on any apps in the past month, but the above reports are describing the same behavioural issues as I am seeing soI think I am hitting the same problem. Using Sennheisser HD 4.40BT headphones on a System76 Gazelle. Connects default audio through headphones with the A2DP profile as expected when connecting through BT, but the Internal Microphone stays selected for input. Trying to select the HD4.4 microphone setting does nothing, and no signal of any kind comes through the input. Switching to the HFP/HSP profile also leads to a break in audio, and after the A2DP setting is shown as unavailable until I wipe the userland pulse configs. It cuts off the audio through the headset and ends up in a bad configuration where I have to turn BT off and on again to reconnect and when it does, the configuration is stuck on HFP/HSP and in mono. No audio through the headset mic can be picked up through any pulseaudio-enabled monitors, all showing zero input with whatever configuration or set-up I can muster. Running Linux pop-os 5.4.0-7642-generic #46~1598628707~20.04~040157c- Ubuntu SMP Fri Aug 28 18:02:16 UTC x86_64 -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898373] [NEW] Nvidia Driver Server Packages should suggest GUI components instead of recommend
Public bug reported: Right now installing `nvidia-driver-4(4|5)0-server` (ubuntu/multiverse) will install the entire gnome-shell stack which pulls in a lot of IMHO unrelated and unwanted software including printer services, input drivers, pulseaudio, and more graphical things normally not desired to be on a headless server. While install with `--no-install-recommends` works as expected, it doesn't include decode/encode libs and extra other libraries normally expected from a full install. I think it would be appropriate to move `nvidia-settings`, `nvidia- prime`, and other recommended packages depending on graphical components to the suggested section. Ubuntu 20.04.1 Package: nvidia-driver-450-server Version: 450.51.06-0ubuntu0.20.04.2 ** Affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Tags: packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1898373 Title: Nvidia Driver Server Packages should suggest GUI components instead of recommend Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: Right now installing `nvidia-driver-4(4|5)0-server` (ubuntu/multiverse) will install the entire gnome-shell stack which pulls in a lot of IMHO unrelated and unwanted software including printer services, input drivers, pulseaudio, and more graphical things normally not desired to be on a headless server. While install with `--no-install-recommends` works as expected, it doesn't include decode/encode libs and extra other libraries normally expected from a full install. I think it would be appropriate to move `nvidia-settings`, `nvidia- prime`, and other recommended packages depending on graphical components to the suggested section. Ubuntu 20.04.1 Package: nvidia-driver-450-server Version: 450.51.06-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1898373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
This bug is NOT invalid. This issue has remained unaddressed for years. Worse still, workarounds that used to mitigate the problem (dconf tweaks, etc) no longer seem effective. PLEASE, do not close this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.: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.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380
Unfortunately, after about a week the wireless crashes started again. I reinstalled, and they are not present on the live image as far as I can tell, though I only used it briefly. Installing the updated firmware from the PPA this time did not resolve the problem. I tried the most up- to-date version of Fedora 32, and so far I do not have this crashing problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge
[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380
It has been a week since I installed the new firmware from the PPA, and there have been no dropouts whatsoever. Thanks again for the assistance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3
[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380
So far, the updated firmware has worked flawlessly; no dropouts whatsoever. I will keep my eyes out for any changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C
[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380
I have installed the new firmware from the PPA; I will keep you informed about how it works. Thanks for your help! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C
[Kernel-packages] [Bug 1891405] Re: Regular wifi crashes on XPS 13 9380
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Confirmed Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine
[Kernel-packages] [Bug 1891405] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401208/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401209/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401211/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401210/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401198/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401204/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401203/+files/Lsusb-v.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/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401207/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System
[Kernel-packages] [Bug 1891405] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401206/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0
[Kernel-packages] [Bug 1891405] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401196/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral:
[Kernel-packages] [Bug 1891405] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1891405/+attachment/5401197/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891405 Title: Regular wifi crashes on XPS 13 9380 Status in linux package in Ubuntu: Incomplete Bug description: Within the past two weeks I've been suffering from a bunch more crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile after reboot, but will eventually throw the error below and require a reboot. [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 63f4915b-939b-493a-8e39-2c19c0a15d9a) [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [26425.815358] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump: [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800 20 19 416 417 [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00 1 0 127 0 [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107 34 226 [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00 0 30 22 20 [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [26425.940417] ieee80211 phy0: Hardware restart was requested [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [26426.285743] ath10k_pci :02:00.0: device successfully recovered lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0