[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Just ran into this on a fresh install of 18.04 MATE on a D630. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags:
[Kernel-packages] [Bug 1689342] [NEW] kernel BUG
20/0x30 May 8 09:15:02 lappy kernel: [42119.855068] __migration_entry_wait+0x1c/0x180 May 8 09:15:02 lappy kernel: [42119.855070] migration_entry_wait+0x74/0x80 May 8 09:15:02 lappy kernel: [42119.855074] do_swap_page+0x5b3/0x770 May 8 09:15:02 lappy kernel: [42119.855077] ? futex_wake+0x90/0x170 May 8 09:15:02 lappy kernel: [42119.855080] handle_mm_fault+0x873/0x1360 May 8 09:15:02 lappy kernel: [42119.855085] __do_page_fault+0x23e/0x4e0 May 8 09:15:02 lappy kernel: [42119.855088] do_page_fault+0x22/0x30 May 8 09:15:02 lappy kernel: [42119.855092] page_fault+0x28/0x30 May 8 09:15:02 lappy kernel: [42119.855094] RIP: 0033:0x7f47bb273a4c May 8 09:15:02 lappy kernel: [42119.855095] RSP: 002b:7f47ac3fae10 EFLAGS: 00010206 May 8 09:15:02 lappy kernel: [42119.855098] RAX: 005d RBX: 7f478dc00268 RCX: 00011d98 May 8 09:15:02 lappy kernel: [42119.855099] RDX: 0476 RSI: RDI: 7f47ac3fae40 May 8 09:15:02 lappy kernel: [42119.855101] RBP: 7f478dc0 R08: R09: 0005cde4 May 8 09:15:02 lappy kernel: [42119.855103] R10: 003472f83e70480e R11: 7f47ac3fae60 R12: 7f47ac3fae40 May 8 09:15:02 lappy kernel: [42119.855104] R13: 0001 R14: 7f47a98c2b80 R15: 7f47ac3fb700 May 8 09:15:02 lappy kernel: [42119.855106] Code: c0 74 e6 4d 85 c9 c6 07 01 74 30 41 c7 41 08 01 00 00 00 e9 52 ff ff ff 83 fa 01 0f 84 b0 fe ff ff 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 5d c3 f3 90 4c 8b 09 4d 85 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 2552 F pulseaudio CurrentDesktop: KDE Date: Mon May 8 10:08:58 2017 HibernationDevice: RESUME=UUID=3c460e7e-df89-4839-97db-af75c6f3b15b InstallationDate: Installed on 2016-05-06 (367 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=9e155e2a-c837-4376-bb00-98c9be381edf ro cgroup_enable=memory swapaccount=1 intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (6 days ago) dmi.bios.date: 02/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.21 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.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1689342/+attachment/4873552/+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/1689342 Title: kernel BUG Status in linux package in Ubuntu: New Bug description: After resuming the laptop from hibernation, I opened Chrome and worked in it for a few minutes and then it froze. Doing "ps aux | grep chrome" hung, as well as "sudo reboot". I can run other bash commands fine. This may or may not be related, but two weeks ago I upgrade the BIOS from 1.02.16 to 1.2.21. Since then I have the system has locked up where I can't run standard bash commands. They just return "command not found" and I can't start new shells because it can't find bash. On this bug report I was able to continue to run commands. May 8 09:14:37 lappy kernel: [42095.651680] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! May 8 09:14:37 lappy kernel: [42095.651705] invalid opcode: [#1] SMP May 8 09:14:37 lappy kernel: [42095.651717] Modules linked in: cmac ipheth rfcomm uas usb_storage ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_hda_codec_hdmi bnep bbswitch(OE) binfmt_misc hid_multitouch nls_iso8859_1 dell_led snd_hda_codec_realtek snd_hda_codec_generic i2c_designware_platform i2c_design
[Kernel-packages] [Bug 1908423] Re: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
I have the same/similar issue on my RPi 4. While playing video with Kodi the Pi randomly will hang and be unresponsive to mouse, keyboard and display frozen. I can SSH and the web server plus torrent servers are still running fine but the cpu load slowly rises to something in the 8-9 range. If left alone it will recover after maybe 30-45 minutes and when it does the kernel posts the below two messages to dmesg. Always the same two messages. I have also seen the "kworker has blocked for more than 120 seconds" message as mentioned above but not lately. Distro: Ubuntu MATE for Raspberry Pi 20.04 uname: Linux raspberry 5.8.0-1011-raspi #14-Ubuntu SMP PREEMPT Tue Dec 15 08:53:29 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux dmesg: [So Jan 10 04:31:09 2021] raspberrypi-firmware soc:firmware: mbox_send_message returned -62 [So Jan 10 04:31:09 2021] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 18446744073709551554 (-34) Based on the "dev_pm_opp_set_rate" error I assumed it was related to the cpufreq function so I changed the cpufreq governor to 'performance' and I haven't had any issues since. I'll continue testing and maybe someday try to debug the kernel but for now it's fixed by leaving the governor on performance. If I'm right then this isn't a Ubuntu bug but really a kernel bug, specific to the Raspberry Pi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 Exactly one Google search result for the exact message: https://forum.openwrt.org/t/rpi-4-failed-to-change-pllb-frequency/81840 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.spe
[Kernel-packages] [Bug 1332384] Re: [Dell Inspiron 5547/5447] Unable to scroll with the clickpad
I have exactly the same issue on Ubuntu 12.04 LTS. My right click also does not work unless I click with 2 fingers. The kernel is 3.13.0-43-generic and 64-bit. I have a Dell Inspiron 5547 as well. I'd upgrade to a newer Ubuntu release, but I have a requirement to keep this version. Is there a supported way I can upgrade the kernel to 3.16? I saw someone else mentioned that kernel fixed their touchpad issues. 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/1332384 Title: [Dell Inspiron 5547/5447] Unable to scroll with the clickpad Status in HWE Next Project: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: CID: 201401-14530 Dell Inspiron 5547 The Clickpad on this system was detected as a SynPS/2 Synaptics TouchPad, I'm not sure if this is expected, but the scrolling feature is not working on 14.04 + update(both two fingers scrolling and one finger edge scrolling). Also, the "disable while typing", three and four fingers tapping are not working as well. Steps: 1. Install 14.04 + update (3.13.0-29), boot to desktop 2. Test the touchpad Expected result: * At least edge scrolling should work Actual result: * Only left / right click, one-finger single / double tapping works. Debugging information: ubuntu@201401-14530:~$ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DLL063E:00 06CB:2934id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1609 F pulseaudio /dev/snd/controlC1: ubuntu 1609 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Jun 19 22:04:37 2014 HibernationDevice: RESUME=UUID=7454cf26-0b42-44d7-ac45-01977170fad5 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=3dfa4af3-a788-4fbe-b7db-b895afb04d77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn0598GM:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
It works great now. Thank you :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
Title:
constantly shows wrong temperature (99°C )
Status in libatasmart package in Ubuntu:
In Progress
Bug description:
Hello, here's my system info
~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
~$ apt-cache policy udisks2
udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
*** 2.1.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C
(210°F), but in reality it's 30°C
~$ sudo smartctl -A /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always
- 0
9 Power_On_Hours 0x0012 100 100 000Old_age Always
- 24
12 Power_Cycle_Count 0x0012 100 100 000Old_age Always
- 51
168 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 0
170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always
- 231
173 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 65539
192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always
- 23
194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always
- 30 (Min/Max 30/30)
218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always
- 0
231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always
- 99
241 Total_LBAs_Written 0x0012 100 100 000Old_age Always
- 337
in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
works well though:
~$ sudo hddtemp /dev/sda
/dev/sda: PNY EU SSD CS1311 240GB: 30°C
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1581594/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920847] Re: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529)
I have this issue as well on a Dell XFR booting from a CD made by Cubic. I did find if I used the kernel that came with the disk (5.11.0-27 vs 5.11.0-48) it would boot and allow install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1920847 Title: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: ACPI Error on boot: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529) Occurred on fresh install of 21.04 Computer: Dell Inspiron 5401 P130G Ubuntu Version: Description: Ubuntu 20.04.2 LTS Release: 20.04 Package Version: linux-signed-hwe-5.8 What i expected to happen: Not have this error appear What Happened: This error Appeared. A dump of the ACPI table has been provided. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 22 23:34:08 2021 InstallationDate: Installed on 2021-03-23 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Please test proposed package
Hello Alex, or anyone else affected, Accepted dkms into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
It would also be good to get this fixed in Ubuntu 19.04 codename Disco Dingo. ** Summary changed: - OBSOLETE_BY in DKMS.CONF not work + OBSOLETE_BY in DKMS.CONF does not work ** Changed in: dkms (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I also see this message in my journal but it doesn't seem to affect my system i.e. its booted and working. Jul 10 09:22:14 speedy kernel: Unpacking initramfs... Jul 10 09:22:14 speedy kernel: Initramfs unpacking failed: Decoding failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello quanxian, or anyone else affected, Accepted qemu into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg- 2ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello quanxian, or anyone else affected, Accepted qemu into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg- 1ubuntu7.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/
[Kernel-packages] [Bug 1836064] Re: glibc needs an update for linux-5.2 kernel headers (alpha)
** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836064 Title: glibc needs an update for linux-5.2 kernel headers (alpha) Status in glibc package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Released Status in glibc source package in Eoan: Triaged Status in linux source package in Eoan: Fix Released Bug description: as seen in https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410 the c-t-b-ports package ftbfs: /bin/bash ../scripts/move-if-change /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp if test -r /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \ else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi In file included from :1: ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" redefined [-Werror] #define __NR_osf_shmat 209 In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24, from ../sysdeps/unix/sysdep.h:20, from ../sysdeps/unix/alpha/sysdep.h:19, from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29, from :1: /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the location of the previous definition #define __NR_osf_shmat __NR_shmat cc1: all warnings being treated as errors Traceback (most recent call last): File "../scripts/gen-as-const.py", line 120, in main() File "../scripts/gen-as-const.py", line 116, in main consts = glibcextract.compute_c_consts(sym_data, args.cc) File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in compute_c_consts subprocess.check_call(cmd, shell=True) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie -fno-PIE -std=gnu11 -fgnu89-inline -pipe -O2 -g -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fno-stack-protector -Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 -mieee -mfp-rounding-mode=d-ftls-model=initial-exec -U_FORTIFY_SOURCE -isystem /<>/glibc-2.29/debian/include -I../include -I/<>/glibc-2.29/build-tree/alpha-libc/csu -I/<>/glibc-2.29/build-tree/alpha-libc -I../sysdeps/unix/sysv/linux/alpha/alpha -I../sysdeps/unix/sysv/linux/alpha/fpu -I../sysdeps/alpha/fpu -I../sysdeps/unix/sysv/linux/alpha -I../sysdeps/alpha/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/ieee754/ldbl-64-128 -I../sysdeps/ieee754/ldbl-opt -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/alpha -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/alpha -I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-128 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed -isystem /<>/glibc-2.29/debian/include -D_LIBC_REENTRANT -include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT -MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o /tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero exit status 1. make[4]: *** [../Makerules:271: /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1 make[4]: Leaving directory '/<>/glibc-2.29/csu' make[3]: *** [Makefile:275: csu/subdir_lib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1836064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
Could you add the ubiquity log file to the bug report or try and the beta iso image and then include the ubiquity log file? ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I have the same problem on my Vostro 3500. I'm using the 4.15.0-47-generic kernel with Gnome 3.28.2 on 18.04.2 LTS. Temperatures are at 67-81C and using Win10 on the same laptop the temperatures are 45-57C with no apps running in either OS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:r
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
The log file wasn't actually attached, could you find it again and add it? ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
Can anyone comment as to whether or not this will be considered for kernels beyond -generic and -hwe? Specifically for aws, aws-hwe, and aws-edge kernels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: New Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: New Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
Thanks Brad, I just saw that this has been in -proposed for a bit on bionic, missed that originally when looking for the file https://packages.ubuntu.com/search?searchon=contents&keywords=libperf-jvmti.so&mode=exactfilename&suite=bionic-updates&arch=any We'll keep our eyes peeled for the release. -- 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: New Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: New Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot
** 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/1840708 Title: HP Envy with AMD Ryzen 5 2500U processor hangs on boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3, kernel 5.0.0-25-generic When grub menu disappears, the screen remains blank. I include a syslog file from a failed boot. The important part is at line 1175: irq 7: nobody cared (try booting with the "irqpoll" option) This laptop boots correctly with the 4.18 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xrdp-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Invalid ** Changed in: xrdp-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in xorg-server source package in Bionic: Invalid Status in xrdp-hwe-18.04 source package in Bionic: Fix Released Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Update Released
The verification of the Stable Release Update for xrdp-hwe-18.04 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in xorg-server source package in Bionic: Invalid Status in xrdp-hwe-18.04 source package in Bionic: Fix Released Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. (comment #8) * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. (comment #3) * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. (comment #12) [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. (comment #11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841669] Re: SR-IOV interface goes down when testing network performance
** Package changed: kernel-package (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/1841669
Title:
SR-IOV interface goes down when testing network performance
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
We are testing network performance with SR-IOV on ubuntu and security
onion in Rhev Hypervisor. We are using a SuperMicro box running T-rex
traffic generator on CentOS which is connected to a gigamon to push
traffic to the Ubuntu/Security Onion VMs.
The ubuntu 16.04 vm is running on a RHVH host node and is running SR-
IOV. We have ensured that SR-IOV is enabled in the BIOS. We are
finding that packets stop coming into the interface after a few
seconds. This is because the interface is going down after a few
seconds of receiving traffic. We are running promiscuous mode and it
is required for our use case of measuring network traffic.
As a troubleshooting measure, 5.3.0-rc3 was built using the 3.2.3 iavf
SR-IOV driver. Note that the i40evf driver was renamed to iavf, which
is why the name discrepancy exists. After updating the Kernel we
stopped seeing this issue.
Non-working default security onion kernel information
root@ubuntu:~# uname -r
3.10.0-957.21.3.el7.x86_64
root@ubuntu:~# ethtool -i ens7
driver: iavf
version: 3.0.1-k
firmware-version: N/A
expansion-rom-version:
bus-info: :00:07.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
Working modified security onion kernel information
root@ubuntu:~# uname -r
5.3.0-rc3-custom
root@ubuntu:~# ethtool -i ens7
driver: i40evf
version: 3.2.3-k
firmware-version: N/A
expansion-rom-version:
bus-info: :00:07.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
We were able to perform testing using the 5.3.0 kernel, but long term
a better solution is needed as this would require supporting a
modified Linux kernel with updates, testing, etc.
From the hypervisor in /var/log/messages:
Aug 27 09:05:00 localhost libvirtd: 2019-08-27 13:05:00.522+: 10748:
error : qemuDomainAgentAvailable:9133 : Guest agent is not
responding: QEMU guest agent is not connected
Aug 27 09:05:07 localhost goferd: [ERROR][worker-0]
gofer.messaging.adapter.conn ect:33 - connect:
proton+amqps://subscription.rhsm.redhat.com:5647, failed: Conn
ection amqps://subscription.rhsm.redhat.com:5647disconnected: Condition('amqp:r
esource-limit-exceeded', 'local-idle-timeout expired')
Aug 27 09:05:07 localhost goferd: [INFO][worker-0]
gofer.messaging.adapter.conne ct:35 - retry in 106 seconds
Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the
message to VF 0 aq_err 12
Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the
message to VF 0 aq_err 12
From the VM, journalctl -xe gives:
-- The start-up result is done.
Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: PF reset warning received
Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: Scheduling reset task
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:08 ubuntu systemd-logind[1251]: Removed session 16.
-- Subject: Session 16 has been terminated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841669/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Also affects: casper (Ubuntu Eoan) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Eoan) Importance: High Status: Confirmed ** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in casper package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in casper source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 RfKill: Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX
[Kernel-packages] [Bug 1828712] Re: I/O errors when trying to loop mount an image
apport-cli contains an option for save the report from another machine. apport-cli --help says: --save=PATH In bug filing mode, save the collected information into a file instead of reporting it. This file can then be reported later on from a different machine. and: -c PATH, --crash-file=PATH Report the crash from given .apport or .crash file instead of the pending ones in /var/crash. (Implied if file is given as only argument.) However, this doesn't work with apport-collect but if the Ubuntu Kernel Bot still wants this you could open a new bug report using --save and the --crash-file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image Status in linux package in Ubuntu: Confirmed Bug description: Command sudo mount -t vfat flop1 /mnt/flop1 fails. The image is readable but the log shows many I/O errors such as May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read boot sector May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev loop0, sector 1 May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, logical block 1, async page read May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev loop0, sector 2 May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, logical block 2, async page read May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev loop0, sector 3 May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, logical block 3, async page read May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev loop0, sector 4 May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, logical block 4, async page read May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev loop0, sector 5 May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, logical block 5, async page read May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev loop0, sector 6 May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, logical block 6, async page read May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev loop0, sector 7 May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, logical block 7, async page read May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, logical block 1, async page read The command, understandably, reports "can't read superblock on /dev/loop0". The problem happens even on newly created images. Here's a sample set of commands and responses: $ mkfs.msdos -C flop1 1440 $ ls -l -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1 $ hd flop1 <--- output looks reasonable including 55 aa and two FATs ---> $ sudo mkdir /mnt/flop1 $ sudo mount -o loop flop1 /mnt/flop1 mount: /mnt/flop1: can't read superblock on /dev/loop0. $ losetup -f /dev/loop0 $ I see plenty of reports of similar on different websites but without resolution, including one on Launchpad but where the OP stopped responding so it did not get resolved. I don't know when this problem started to occur on this machine. If it's relevant, this is running under VirtualBox which reports itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host extensions' enabled. However, mounting a floppy image previously worked on this virtual machine. I have rebooted with /forcefsck to check the root (and only) filesystem. I have upgraded to the latest LTS Ubuntu, as below, but the problem persists. System info: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The machine is command-line only, i.e. no windowing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages
[Kernel-packages] [Bug 1828657] Re: Slow resume after lid close/open
** 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/1828657 Title: Slow resume after lid close/open Status in linux package in Ubuntu: Confirmed Bug description: Summary 1.) Release Info: Description: Ubuntu 19.04 Release: 19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829095] Re: Keyborad backligt does not work
** Package changed: ubuntu-meta (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/1829095 Title: Keyborad backligt does not work Status in linux package in Ubuntu: New Bug description: I have a dell XPS14 (L421X). In releases 18.04 and lower the keyboard back light used to work. However in 18.10 and 19.04 it does not The dell_laptop model is loaded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-desktop 1.431 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 15 11:44:51 2019 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829340] Re: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0
** 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/1829340 Title: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0 Status in linux package in Ubuntu: New Bug description: Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 0) PCIID: 8086:10fb subsystem 103c:17d0 I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported kernel from 18.04 v4.15. PXE boot process works well till the moment when the installer tries to load the ixgbe driver for NIC. The driver fails to initialize NIC with the following error messages in the syslog: ixgbe: Intel(r) 10 Gigabit PCI Express Network Driver - version 5.1.0-k ixgne: Copyright (c) 1999-20016 Intel Corporation ixgbe: probe of :03:00.0 failed with error -5 ixgbe: probe of :03:00.1 failed with error -5 I have used the most recent initrd and kernel from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/hwe-netboot/ubuntu-installer/amd64/ file linux initrd.gz linux: Linux/x86 Kernel, Setup Version 0x20d, bzImage, Version 4.15.0, Version 4.15.0-45, RO-rootFS, swap_dev 0x7, Normal VGA initrd.gz: gzip compressed data, was "initrd", from Unix, last modified: Wed Feb 20 06:36:36 2019, max compression Also I'd like to say that * the same issue with ixgbe 4.2.1-k if I use the installer of Ubuntu 16.04 with kernel v4.4 * ixgbe v4.2.1-k from SLES12SP2 works correctly. #this is SLES12 host with more info about ixgbe from SLES12. :~ # modinfo ixgbe filename: /lib/modules/4.4.90-92.50-default/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.2.1-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: F8D1434936208D466C73062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind
** Changed in: nplan (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630285 Title: mwifiex_pcie crashes after several bind/unbind Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in nplan package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in nplan source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in nplan source package in Yakkety: Fix Released Bug description: [Impact] netplan-configured systems with mwifiex interfaces crash if netplan attempts to unbind/bind the interface. [Test case] 1) Run 'netplan apply' on a system with mwifiex_pci driver. The system should not crash, and the mwifiex interface should remain untouched. [Regression potential] Interfaces other than those affected by unbind/bind crashes or failures should still be unbound when 'netplan apply' is run. This affects most wireless interfaces, with the notable exception of mwifiex and brcmfmac. Failure to apply netplan configuration for a legitimate mwifiex device (wireless connection driven by NetworkManager renderer using netplan) would also constitute a regression. [Original bug report] # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind Keep doing the bind/unbind actions, it would crash very soon. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
On 17/5/19 1:14 am, Kai-Heng Feng wrote: > Sorry for the late reply. Does this happen on generic kernel? > It is so good to hear from anyone on this problem, so I welcome your "late reply"! My laptop runs ubuntu studio 19.04, but studio stopped including the linux-generic package many releases ago. By the way, /lib/firmware/iwlwifi-7265D-29.ucode is the latest on this 19.04 disco system, dated 18 May 2018, so I have confirmed it as broken with at least two earlier ubuntu releases and very many kernels. I suppose we should wish iwlwifi-7265D-29 a happy birthday??? In order to answer your question, there is no reason why I cannot install it, so I will try to find time in the next few days... unfortunately I have a broken desktop and other work commitments which need to be delivered using only this laptop, so I don't want to distract myself and accidentally break something! I'll get back to you in a day or two. I am very interested in the result of the test. Regards, Brian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: Confirmed Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I installed the 5.0.0-15-generic kernel and removed iwlwifi from the /etc/modprobe.d/blacklist. The system was stable and ran very well for 4 or 5 hours. When I booted it (still generic kernel) this morning, it failed after about 20 minutes. I rebooted and teed journalctl for documentation. The failure occurred after only 4 or 5 minutes. I will attach the log from this crash. ** Attachment added: "generic kernel log during failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5265227/+files/dell-inspiron-iwlwifi-7265D-29-generic-kernel-failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: Confirmed Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828906] Re: upgrade to Linux 4.15.0-48-generic crashes display on lenovo G500
** Package changed: ubuntu-release-upgrader (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/1828906 Title: upgrade to Linux 4.15.0-48-generic crashes display on lenovo G500 Status in linux package in Ubuntu: New Bug description: Last week my Lenovo G500 laptop running ubuntu 18.04 reported an available system update of about 180 MBs, which included a kernel version update. I installed it and following the reboot, the display hung with a purple screen with bands of random colored pixels across the screen. If I reboot and hold down SHIFT to get to GRUB, it presents the following choices under Advanced Options: Ubuntu, with Linux 4.15.0-48-generic Ubuntu, with Linux 4.15.0-48-generic (recovery mode) Ubuntu, with Linux 4.15.0-47-generic Ubuntu, with Linux 4.15.0-47-generic (recovery mode) If I select 4.15.0-48-generic, I get the display hang problem described above or other forms of display misbehavior (sometimes it flashes continuously, sometimes it just hangs at a black screen, its not consistent). If I select 4.15.0-47-generic, it boots up just fine to a completely usable desktop. Every time. I've tried running boot-repair. It reported that it had repaired GRUB, but the problem persists. So I don't think its a boot parameters problem. I conclude that the problem has something to do with the display driver in 4.15.0-48-generic that was not present in 4.15.0-47-generic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.31 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon May 13 18:11:02 2019 InstallationDate: Installed on 2019-04-18 (25 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) 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: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2019-05-13 16:34:52.461061 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2019-05-13 16:35:07.526926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors
** 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/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: New Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration. Logfile snippets attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
how does this get assigned to someone so it might get fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652101
Title:
Can't create nested AppArmor namespaces
Status in AppArmor:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:
We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root,
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1
Now we enter into confinement using the AppArmor namespace and profile and
then enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur
We can now load profiles as the privileged user inside of the unprivileged
user namespace
# echo "profile test {}" | apparmor_parser -qr
The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace
# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission
denied
If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace,
and leverage the nested namespace for its nested containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"
Additionally, if you choose to reboot from the live environment without installing what happens? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822044 Title: Laptop freezes after installation is finished when pressing "Restart Now" Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: As stated in lp:1822026, the Dell Precision 7530 I'm using is using nouveau graphics drivers by default when starting a live session, and this driver is prone to errors. One of the most annoying for a new user is the following: 1. Boot into 19.04 live session 2. Launch "Install Ubuntu 19.04" and go through the installation steps 3. Once the install is done, the "Installation Complete" dialog is shown with two options: [Continue Testing][Restart Now] 4. Press [Restart Now] Expected behaviour: 4. The device restarts and boots into freshly installed Ubuntu 19.04. Actual behaviour: 4. The device freezes and even the keyboard combination SysRq+REISUB doesn't do anything. User has to force shutdown the device by pressing Power button for a few seconds, remember to remove the USB drive, then manually start the device. All the hardware-related information is available in the sosreport attachment in lp:1822026: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822026/+attachment/5249977/+files /sosreport-ubuntu-20190328033617.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
** Description changed: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. - On reboot I could not see and wireless networks. I went to the + On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. - ProblemType: Bug - DistroRelease: Ubuntu 19.04 + ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dad1060 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: - lono wireless extensions. - - enp3s0no wireless extensions. + lono wireless extensions. + + enp3s0no wireless extensions. Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 - Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) - Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 + Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: - linux-restricted-modules-5.0.0-7-generic N/A - linux-backports-modules-5.0.0-7-generic N/A - linux-firmware 1.178 + linux-restricted-modules-5.0.0-7-generic N/A + linux-backports-modules-5.0.0-7-generic N/A + linux-firmware 1.178 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no - SourcePackage: linux + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwCon
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello Mauricio, or anyone else affected, Accepted hw-detect into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/hw- detect/1.117ubuntu6.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: hw-detect (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: In Progress Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: In Progress Status in debian-installer source package in Cosmic: In Progress Status in hw-detect source package in Cosmic: In Progress Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: In Progress Status in debian-installer source package in Disco: In Progress Status in hw-detect source package in Disco: Fix Committed Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: In Progress Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comment 11. - hw-detect: low, the changes are enabled b
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello Mauricio, or anyone else affected, Accepted hw-detect into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/hw- detect/1.117ubuntu6.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: hw-detect (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags removed: verification-done-cosmic ** Tags added: verification-needed-cosmic ** Changed in: hw-detect (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: In Progress Status in debian-installer source package in Cosmic: In Progress Status in hw-detect source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: In Progress Status in debian-installer source package in Disco: In Progress Status in hw-detect source package in Disco: Fix Committed Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: In Progress Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week
[Kernel-packages] [Bug 1817321] Please test proposed package
Hello Mauricio, or anyone else affected, Accepted hw-detect into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/hw- detect/1.117ubuntu6.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: In Progress Status in debian-installer source package in Cosmic: In Progress Status in hw-detect source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: In Progress Status in debian-installer source package in Disco: In Progress Status in hw-detect source package in Disco: Fix Committed Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: In Progress Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comment 11. - hw-detect: low, the changes are enabled by a preseed option. see comment 12. - partman-iscsi: low, simple changes, plus one fix that has
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
** 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/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Incomplete Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] Jun 8 12:11:17 mc2 kernel: [30304.199102] RIP: 0010:cpuidle_enter_state+0xbd/0x450 Jun 8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 0
[Kernel-packages] [Bug 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on
** 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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Incomplete Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813463] Re: no bluetooth intel ac 9260
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1813463 Title: no bluetooth intel ac 9260 Status in bluez package in Ubuntu: New Bug description: Hi All Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 5.0. Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the bluetooth is not detected and can't be switched on. hciconfig -a Produces no result $ bluetoothctl Agent registered [bluetooth]# show No default controller available [bluetooth]# devices No default controller available [bluetooth]# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
Hello bugproxy, or anyone else affected, Accepted kexec-tools into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.16-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kexec-tools (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: kexec-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Bionic: Fix Committed Status in kexec-tools source package in Cosmic: Fix Committed Bug description: For SRU: [Impact] * The ibm,dynamic-memory-v2 device tree property replaced the original ibm,dynamic-memory property. Since kexec-tools doesn't know to look for the "-v2" property yet, it fails to successfully parse the node using the new "-v2" property. * These changes enable the new "-v2" property to be successfully parsed from the node. [Test Case] * Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` * Expected result: kexec loads without any warning/error messages [Testing] These changes were tested by Hari with a positive result on a 4.18 kernel for ppc64el. [Regression Potential] * Low. * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. Original bug description below. --- == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload * unloaded kdump kernel root@ubuntu:~# kdump-config load * Creating symlink /var/lib/kdump/vmlinuz * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K * loaded kdump k
[Kernel-packages] [Bug 1828187] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted kexec-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.16-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Bionic: Fix Committed Status in kexec-tools source package in Cosmic: Fix Committed Bug description: For SRU: [Impact] * The ibm,dynamic-memory-v2 device tree property replaced the original ibm,dynamic-memory property. Since kexec-tools doesn't know to look for the "-v2" property yet, it fails to successfully parse the node using the new "-v2" property. * These changes enable the new "-v2" property to be successfully parsed from the node. [Test Case] * Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` * Expected result: kexec loads without any warning/error messages [Testing] These changes were tested by Hari with a positive result on a 4.18 kernel for ppc64el. [Regression Potential] * Low. * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. Original bug description below. --- == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload * unloaded kdump kernel root@ubuntu:~# kdump-config load * Creating symlink /var/lib/kdump/vmlinuz * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K * loaded kdump kernel root@ubuntu:~# --- Contact Information = hbath...@in.ibm.com ---uname output--- Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- na Machine Type = na ---D
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: In Progress Status in lvm2 package in Debian: Unknown Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: New Status in lvm2 source package in Cosmic: New Status in linux source package in Disco: New Status in lvm2 source package in Disco: New Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: In Progress Status in lvm2 package in Debian: Unknown Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Changed in: lvm2 (Ubuntu Eoan) Milestone: ubuntu-16.03 => None ** Changed in: lvm2 (Ubuntu Eoan) Assignee: Andy Whitcroft (apw) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: New Status in lvm2 source package in Cosmic: New Status in linux source package in Disco: New Status in lvm2 source package in Disco: New Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: In Progress Status in lvm2 package in Debian: Unknown Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Update Released
The verification of the Stable Release Update for dkms has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in dkms package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in dkms source package in Disco: Fix Released Bug description: [Impact] The dkms version available in disco regressed in behavior in comparison to earlier series, causing `dkms uninstall` removing the module from the built tree instead of only uninstalling it. Per the dkms manpage, an uninstall operation should leave the module in the 'built' state, while currently it ends up only in the 'added' state. This breaks our current shim-signed logic, since on postinst we're uninstalling every dkms module, checking if we uninstalled it correctly by making sure it's in the 'built' state and then signing it if everything is ok. And this is now broken. This seemed to have been introduced unintentionally as the manpage still notes for `dkms uninstall`: "Uninstalls an installed module/module-version combo from the kernel/arch passed in the -k option, or the current kernel if the -k option was not passed upon. After uninstall completion, the driver will be left in the built state. To completely remove a driver, the remove action should be utilized." The bug has been made visible with the bcmwl-kernel-source driver, which, if installed before shim-signed, will then become uninstalled and not reinstalled again (because of the failed status check before signing). [Test Case] An easy way of checking if the uninstall logic has been reverted: 1. On a disco system, install the dkms and bcmwl-kernel-source packages (-proposed disabled). 2. Check the version of the module installed `dkms status`. 3. Once the installation completes, uninstall the bcmwl dkms module from the system: `dkms uninstall bcmwl/` 4. Checks that the status is not reported as 'built' (should be something like 'added' only): `dkms status bcmwl` 5. Enable disco-proposed and upgrade dkms. 6. Re-install the bcmwl-kernel-source package. 7. Once again uninstall the bcmwl dkms module: `dkms uninstall bcmwl/` 8. Check the status and notice that it is now reported as 'built': `dkms status bcmwl` Another way would be checking on a secureboot-enabled system that has Broadcom wireless installing the -proposed dkms, then bcmwl-kernel- source and finally shim-signed (reinstalling if necessary). This operation should result in the broadcom dkms module still being installed and active. But this test should be counted as an optional 'additional test'. [Regression Potential] Since this does change the dkms uninstall behavior, there is always some risk involved. One of the potential regressions could be related to kernel uninstallation, as we are reverting parts of the kernel prerm scripts along with the revert - but the risk should be low as we're actually reverting to the state we had in all series prior to disco. In overall the uninstall command of dkms might have regressed its behavior in case some other place started assuming the removals of modules from the built directory, but seeing the disco diff it's highly improbable. [Original Description] For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireles
[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
After upgrading to 19.04 disco, the system is still too unstable to be useful. The current kernel is 5.0.0-13-lowlatency (buildd@lcy01-amd64-020). I note the Intel driver has not changed after the upgrade from 18.10 cosmic, i.e. still iwlwifi-7265D-29.ucode, packaged within linux- firmware version 1.178. The details of the stack trace are different, but the outcome is the same (attached). The wifi connection is lost and kernel error messages spew out to the log. Stopping and restarting wifi makes no difference. The only "solution" is to shut down the system and reboot. Luckily I have a usb dongle that uses rtlwifi firmware, which works OK. ** Attachment added: "disco kernel log when intel driver hang is reported" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5261968/+files/bacchus-iwlwifi-hang-log-disco-2019-04-27 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: Confirmed Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
The system is now running 19.04 x64 desktop. The problem has not changed in any obvious manner, although reporting of battery status for its external logitech bluetooth mouse is now correct. Ca anyone suggest how to perform further problem determination, or perhaps even a circumvention. The 0% battery notifications appear every 10 minutes or so and are very tiresome to regularly delete (re the little boy who cried wolf). -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839214] Re: Setting vm.overcommit_kbytes = 0 made the entire system explode.
** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839214 Title: Setting vm.overcommit_kbytes = 0 made the entire system explode. Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 LTS and the newest kernel 4.4.0-157, I tried the following command: echo "vm.overcommit_memory = 2" >> /etc/sysctl.conf echo "vm.overcommit_kbytes = 0" >> /etc/sysctl.conf sysctl -p Then I can't reboot, all the commands are invalid, the system explodes. After a forced restart, I can't even connect it with ssh. #reboot reboot -bash: fork: Cannot allocate memory After some searching and inspection, I find the default value of vm.overcommit_kbytes is 0, so why set it to 0 again will get such a result? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839151] Re: acpi warnings at boot time
** 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/1839151 Title: acpi warnings at boot time Status in linux package in Ubuntu: New Bug description: slow boot with black screen $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ dmesg | grep "report a bug" [0.937327] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug $ lsmod | grep acpi toshiba_acpi 53248 0 sparse_keymap 16384 1 toshiba_acpi industrialio 73728 1 toshiba_acpi wmi28672 2 toshiba_acpi,wmi_bmof video 45056 1 toshiba_acpi $ dmesg | grep acpi [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.942577] acpi ABCD:00: ACPI dock station (docks/bays count: 1) [0.947594] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.947816] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [0.988306] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [5.169375] acpi device:37: registered as cooling_device2 [ 18.730234] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.24 [ 18.838815] toshiba_acpi: WMI event detected, hotkeys will not be monitored [ 18.907530] toshiba_acpi: Supported laptop features: touchpad special-function-keys cooling-method $ dmesg | grep "ACPI" [0.00] BIOS-e820: [mem 0xaa1ee000-0xaa976fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa99a000-0xaa99efff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf6bf000-0xaf7befff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf7bf000-0xaf7fefff] ACPI data [0.017303] ACPI: Early table checksum verification disabled [0.017551] ACPI: RSDP 0x000FE020 24 (v02 TOSASU) [0.017555] ACPI: XSDT 0xAF7FE210 A4 (v01 TOSASU TOSASU00 0100 0113) [0.017562] ACPI: FACP 0xAF7FA000 00010C (v05 TOSASU TOSASU00 0100 ACPI 0004) [0.017569] ACPI: DSDT 0xAF7DF000 017D26 (v01 TOSASU TOSASU00 ACPI 0004) [0.017573] ACPI: FACS 0xAF7B2000 40 [0.017576] ACPI: ECDT 0xAF7FD000 C1 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017580] ACPI: UEFI 0xAF7FC000 000236 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017584] ACPI: ASF! 0xAF7FB000 A5 (v32 TOSASU TOSASU00 0001 ACPI 0004) [0.017588] ACPI: HPET 0xAF7F9000 38 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017591] ACPI: APIC 0xAF7F8000 8C (v03 TOSASU TOSASU00 0001 ACPI 0004) [0.017595] ACPI: MCFG 0xAF7F7000 3C (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017599] ACPI: SLIC 0xAF7DE000 000176 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017602] ACPI: WDAT 0xAF7DD000 000224 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017606] ACPI: SSDT 0xAF7DB000 001068 (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017610] ACPI: BOOT 0xAF7D9000 28 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017614] ACPI: ASPT 0xAF7D4000 34 (v07 TOSASU TOSASU00 0001 ACPI 0004) [0.017618] ACPI: FPDT 0xAF7D2000 44 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017621] ACPI: SSDT 0xAF7D1000 000937 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017625] ACPI: SSDT 0xAF7D 000A92 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017629] ACPI: SSDT 0xAF7CF000 0004AF (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017641] ACPI: Local APIC address 0xfee0 [0.074282] ACPI: PM-Timer IO Port: 0x408 [0.074286] ACPI: Local APIC address 0xfee0 [0.074308] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.074310] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.074312] ACPI: IRQ0 used by override. [0.074314] ACPI: IRQ9 used by override. [0.074316] Using ACPI (MADT) for SMP configuration information [0.074318] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.122794] ACPI: Core revision 20181213 [0.156523] PM: Registering ACPI NVS region [mem 0xaa1ee000-0xaa976fff] (7901184 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaa99a000-0xaa99efff] (20480 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaf6bf000-0xaf7befff] (1048576 bytes) [0.156523] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.156523] ACPI: bus type PCI registered [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.160035] ACPI: Adde
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
Hello Pablo, or anyone else affected, Accepted thermald into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.7.0-5ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: thermald (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Status in thermald source package in Bionic: Fix Committed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) - SRU Justification == [Impact] * As described by the original bug reporter, CPU usage of Lenovo P52 is sub-optimal under heavy load. * My observation is the machine exhibits a sharp drop of power usage and CPU frequency and takes time to slowly ramp up again (refer to the chart at https://bit.ly/2OJphB8) * Fixed by bisecting and backporting fixes from thermald project. [Test Case] * One can stress the CPU load of the machine and collect the CPU frequency and power usage over time to check for any anamoly. The script at https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this. * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a consistent power usage can be maintained. [Regression Potential] * Medium. The fix consists of 7 commits cherry-picked from upstream, these changes will affect any machines using RAPL cooling device. The impact may not be obvious in normal daily usage but will be manifested during heavy load, suggest a longer verification period so that more people can discover any adverse effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
Let's use the "block-proposed" tag to indicate that this needs a longer period of time for verification. When you think its baked long enough please remove the tag. ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Status in thermald source package in Bionic: Fix Committed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) - SRU Justification == [Impact] * As described by the original bug reporter, CPU usage of Lenovo P52 is sub-optimal under heavy load. * My observation is the machine exhibits a sharp drop of power usage and CPU frequency and takes time to slowly ramp up again (refer to the chart at https://bit.ly/2OJphB8) * Fixed by bisecting and backporting fixes from thermald project. [Test Case] * One can stress the CPU load of the machine and collect the CPU frequency and power usage over time to check for any anamoly. The script at https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this. * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a consistent power usage can be maintained. [Regression Potential] * Medium. The fix consists of 7 commits cherry-picked from upstream, these changes will affect any machines using RAPL cooling device. The impact may not be obvious in normal daily usage but will be manifested during heavy load, suggest a longer verification period so that more people can discover any adverse effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Hello Mauricio, or anyone else affected, Accepted zfs-linux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.6.5.6-0ubuntu28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in linux package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in zfs-linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. (comment #8) * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. (comment #3) * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. (comment #12) [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. (comment #11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862723] Re: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics
** 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/1862723 Title: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics Status in linux package in Ubuntu: New Bug description: 18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD ( 18.04.3 hwe can auto load via model depends) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi2-5.3 (Ubuntu Focal) Importance: High Status: New -- 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/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: New Status in linux-raspi2-5.3 source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, unability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian, after some initial testing, seems to work better in this regard (though we saw various reports of it still being a bit flaky). We have tried pulling in the wifi firmware bits from Raspbian and using those, but the issues were still the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862831] Re: hciattach on rpi4 times out on first attempt
** Tags added: bionic eoan ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1862831 Title: hciattach on rpi4 times out on first attempt Status in linux-raspi2 package in Ubuntu: New Bug description: I've observed this in both armhf and arm64 on: 19.10.1-server 18.04.4-server core18 It does not seem to happen on rpi3, only on rpi4. If you want to use Bluetooth on rpi, one must first run: $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow On RPI4, this results in a timeout on the first attempt. Reattempting it right after will work though, 100% of the times I've tried it. In the failed attempt, the output is: bcm43xx_init Initialization timed out. And the following is the only new message to show up in dmesg when this fails: [ 270.303691] uart-pl011 fe201000.serial: no DMA platform data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1862831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862791] Re: ALC3234 - Popping sounds at the start and at the end of playback
** Package changed: ubuntu-release-upgrader (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/1862791 Title: ALC3234 - Popping sounds at the start and at the end of playback Status in linux package in Ubuntu: New Bug description: I have bought the Canonical certified DELL Inspiron 15 3585 and i have an issue with audio playback. It only happens when using built-in speakers, it doesn't happen on playback through the 3.5 mm jack output or HDMI output. I already tried disabling power save $ cat /sys/module/snd_hda_intel/parameters/power_save 0 $ cat /sys/module/snd_hda_intel/parameters/power_save_controller N i also tried tsched=0 and using aplay /dev/zero, nothing helped thus far additional info: $ lspci | grep Audio 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller $ dmesg | grep -i error [1.065246] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.119343] RAS: Correctable Errors collector initialized. [8.980071] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [9.769684] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [9.769697] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [9.769702] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.691398] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [ 11.691419] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.691425] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.727149] pcieport :00:01.7: AER: Corrected error received: :00:01.0 [ 11.727159] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.727164] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 $ dmesg | grep -i audio [0.565377] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [9.843973] snd_hda_intel :04:00.1: Handle vga_switcheroo audio client [9.855036] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:08.1/:04:00.1/sound/card0/input16 [9.905946] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3234: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [9.905950] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.905952] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [9.905954] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [9.905955] snd_hda_codec_realtek hdaudioC1D0:inputs: [9.905958] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 [9.905960] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [9.905961] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 [9.963314] input: HD-Audio Generic Headphone Mic as /devices/pci:00/:00:08.1/:04:00.6/sound/card1/input18 OS: Kubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Feb 11 16:49:19 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
I'm actually getting good results using the updated brcmfmac43455 firmware files which Raspbian is using. To use them I first removed '/lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi*' then put the brcmfmac43455-sdio* files in the same directory and rebooted. ubuntu@ubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" ubuntu@ubuntu:~$ ip address show wlan0 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether dc:a6:32:37:37:08 brd ff:ff:ff:ff:ff:ff inet 192.168.1.111/24 brd 192.168.1.255 scope global dynamic wlan0 valid_lft 85747sec preferred_lft 85747sec inet6 fe80::dea6:32ff:fe37:3708/64 scope link valid_lft forever preferred_lft forever ubuntu@ubuntu:~$ md5sum /lib/firmware/brcm/brcmfmac43455-sdio.* 963eb0d4903040974ee88b4f85cb1f4f /lib/firmware/brcm/brcmfmac43455-sdio.bin c5aeca0e33de4ae870986c517963fef7 /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob 7b983812a8aee7bf701460436c686226 /lib/firmware/brcm/brcmfmac43455-sdio.txt ubuntu@ubuntu:~$ dmesg | grep brcmfmac [ 12.265990] brcmfmac: F1 signature read @0x1800=0x15264345 [ 12.271828] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 12.284536] usbcore: registered new interface driver brcmfmac [ 12.355127] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2 [ 12.548549] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 12.579186] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 [ 13.578117] brcmfmac: power management disabled ubuntu@ubuntu:~$ iw dev phy#0 Unnamed/non-netdev interface wdev 0x2 addr 52:4f:c2:5b:63:7a type P2P-device txpower 31.00 dBm Interface wlan0 ifindex 3 wdev 0x1 addr dc:a6:32:37:37:08 ssid Linksys01146_5GHz type managed channel 44 (5220 MHz), width: 80 MHz, center1: 5210 MHz txpower 31.00 dBm For the record I'm connecting to a Linksys EA7450 wireless access point and I've restricted the 5GHz frequency to 802.11ac only. ** Tags added: bionic eoan focal rls-ff-incoming ** Tags removed: rls-ff-incoming ** Description changed: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to - detect 802.11ac APs, unability to connect and/or receive an IP address + detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. - We will provide all the information that we have. Raspbian, after some - initial testing, seems to work better in this regard (though we saw - various reports of it still being a bit flaky). We have tried pulling in - the wifi firmware bits from Raspbian and using those, but the issues - were still the same. + We will provide all the information that we have. Raspbian works better + in this regard. We have pulled in the wifi firmware bits from Raspbian + and using those, and that seems to resolve all flakiness. -- 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/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: New Status in linux-raspi2-5.3 source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue c
Re: [Kernel-packages] [Bug 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
On Tue, Feb 11, 2020 at 10:42:56PM -, Seth Forshee wrote: > This should be point at linux-5.4 and not linux-signed-5.4. Could you elaborate on exactly what should point to what? Thanks, -- Brian Murray -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in apport source package in Focal: In Progress Status in linux source package in Focal: Invalid Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
The only other Pi that I currently have is a 3B which does not have 802.11ac capabilities. https://www.raspberrypi.org/documentation/faqs/#hardware -- 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/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: New Status in linux-raspi2-5.3 source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session
You could test preview images of 20.04 by downloading them from here: http://cdimage.ubuntu.com/ubuntu/daily-live/current/ ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** No longer affects: kernel-package (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/1863219 Title: WiFi module RTL8723DE not supported @live / installed session Status in linux package in Ubuntu: Incomplete Bug description: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. Therefore, no wifi switch/icon. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860182] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [BIONIC] == The HWE kernel on bionic provides zfs 0.8.1 driver which includes an improved scrub however, the progress stats reported by the kernel are incompatible to the 0.7.x zfs driver. == Fix == Use the new zfs 8.x pool_scan_stat_t extra fields to calculate the scan progress when using zfs 8.x kernel drivers. Add detection of the kernel module version and use an approximation to the zfs 0.8.0 progress and rate reporting for newer kernels. For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5 zfs w/o problems and ignore these new fields and continue to use the 0.7.5 rate calculations. == Test == Install the HWE kernel on Bionic, create some large ZFS pools and populate with a lot of data. Issue: sudo zpool scrub poolname and then look at the progress using sudo zpool status Without the fix, the progress stats are incorrect. With the fix the duration and rate stats as a fairly good approximation of the progress. Since the newer 0.8.x zfs does scanning now in two phases the older zfs tools will only report accurate stats for phase #2 of the scan to keep it roughly compatible with the 0.7.x zfs utils output. == Regression Potential == This is a userspace reporting fix so the zpool status output is only affected by this fix when doing a scrub, so the impact of this fix is very small and limited. I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notificat
[Kernel-packages] [Bug 1864041] Update Released
The verification of the Stable Release Update for ec2-hibinit-agent has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Committed Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1871408] Re: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns
** 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/1871408 Title: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns Status in linux package in Ubuntu: New Bug description: In brief, I upgraded Kubuntu 18.04 to 20.04 Beta. STEPS TO REPRODUCE 1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and OMGUbuntu for example) can result in extenuated wait times for page loading. 2. Attempting to updatwapt leads to failures to fetch. 3. Connecting to Speedtest.net resulted in 300 mbps upload and download whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a Connection Has Timed Out Error. System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: KDE Plasma 5.18.3 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s serial: Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: UEFI: LENOVO v: N1WET31W (1.10 ) date: 04/17/2017 Battery: ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) CPU: Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 830 3: 809 4: 822 Graphics: Device-1: Intel HD Graphics 620 driver: i915 v: kernel Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.2 Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-21-generic Network: Device-1: Intel Ethernet I219-LM driver: e1000e IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 476.94 GiB Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4 Sensors: System Temperatures: cpu: 36.5 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB (33.5%) Shell: bash inxi: 3.0.38 WORKAROUND: This may have to do with a Kernel Regression or is at least Kernel related? (This is getting quickly above my pay grade.) I used Grub Customizer to boot with kernel 4.18.5-041805-generic and network connectivity/throughput is now functioning as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Tags added: rls-ff-notfixing rls-gg-incoming ** Also affects: grub2 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Tags removed: rls-ff-notfixing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in grub2 source package in Focal: Confirmed Status in linux source package in Focal: Invalid Bug description: I'm running focal devel and the latest kernel (see proc version below) Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 Dock Monitor is supported very well with multiple usb devices plugged on the monitor. However on reboot I face a black screen with no ability to enter my FDE password. Both my Laptop screen and the attached usb-c display nothing I have to hard power off and reboot without the USB-C monitor plugged in. Otherwise A reboot cycle with the usb-c unplugged works perfectly. Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic without success. I would be happy to provide much more debugging information. I will attach then to the launchpad Bug # --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mclemenceau 2988 F pulseaudio /dev/snd/controlC0: mclemenceau 2988 F pulseaudio /dev/snd/controlC1: mclemenceau 2988 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-ae0xx NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2TV18AS#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Given that all the other linux package hook symlinks are made in apport I think it would make sense to include the linux-firmware symlink there. [ 8:47AM 10484 ] [ bdmurray@impulse:~/source-trees/apport/focal ] $ head -n15 debian/apport.links /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem-5.4.py /usr/bin/apport-bug /usr/bin/ubuntu-bug /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/ubuntu-bug.1.gz /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/apport-collect.1.gz -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1
[Kernel-packages] [Bug 1872297] Re: drop dependency: linux-image-* suggests fdutils
** Changed in: linux-meta (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872297 Title: drop dependency: linux-image-* suggests fdutils Status in linux-meta package in Ubuntu: New Bug description: Floppy drives are practically nonexistent today. They are not even compatible with fairly recent motherboards anymore. Why would all "linux-image-*" packages *suggest* installing "fdutils" to support them? I suggest dropping this dependency. Maybe the next non-LTS release (20.10) is a good moment to do it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1872297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570
** Package changed: ubuntu-release-upgrader (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/1870614 Title: Unable to boot ubuntu 19.10 or newer on dell xps 9570 Status in linux package in Ubuntu: New Bug description: Hi, Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It fails with the following error quickly flashing: error: file `/boot/` not found Then followed by: error: cannot allocate kernel buffer. error: you need to load the kernel first. press any key to continue... This occurs when doing an update from 19.04 to 19.10 and also when just booting off a usb drive with 19.10. When booting off the usb drive. The first error flashes quickly before displaying the usb installer options. Selecting any install / boot option results in the second error about kernel buffer. I have tried all combinations of bios settings I can think of, such as toggling secure boot and other options. The only thing that made a difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This allows the installer to complete, but I cannot then boot off the hard drive. I have tried the same USB drive with 19.10 on a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. I have also tried many different USB drives on my 9570. I have tried a few daily builds of 20.04 with the same result. I tested with 20.04 beta as well. Note: 19.04 and earlier continues to work no problem. I have asked for help previously: * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail * https://answers.launchpad.net/ubuntu/+question/689546/+index ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.9 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 06:55:59 2020 InstallationDate: Installed on 2019-10-24 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870816] Re: received update then got stuck on blackscreen in login screen. Changed "qiuet splash" to "radeon.modeset=0" in order to boot normally.
** Tags added: regression-update ** Package changed: ubuntu-release-upgrader (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/1870816 Title: received update then got stuck on blackscreen in login screen. Changed "qiuet splash" to "radeon.modeset=0" in order to boot normally. Status in linux package in Ubuntu: Confirmed Bug description: I received an update yesterday 3/4/2020 that had important security and kernel updates, so I launched it as I usually do with any security or kernel updates I receive. It downloaded and installed the necessary files and requested a restart. I restarted and kept receiving a black screen with only my mouse visible on the login screen and nothing I tried worked until I went to Grub and pressed "e" then changed the "qiuet splash" to "radeon.modeset=0" (since my graphics card is ATI Radeon) in order to boot normally. And it worked! But that means that there's a bug in the latest update release and I don't like to change in the system files in order to boot my laptop. So please fix and let me know when can I revert back what I did and login normally without the change I made. Thank you Version: Ubuntu 19.10 GNOME: 3.34.2 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:06:55 2020 InstallationDate: Installed on 2020-03-11 (24 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-04-04 08:56:31.608736 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Tags removed: champagne -- 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/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: New Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: New Status in bluez source package in Focal: Invalid Bug description: bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873487] [NEW] package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-in
Public bug reported: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-lowlatency:5.4.0-24.28 Setting up linux-modules-nvidia-440-5.4.0-24-lowlatency (5.4.0-24.28) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-24-lowlatency.postinst: 44: 3: Bad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-24-lowlatency (--configure): installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 ErrorMessage: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1873487 Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules- nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 Status in linux-restricted-modules package in Ubuntu: New Bug description: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-low
[Kernel-packages] [Bug 1873487] Re: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-inst
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+attachment/5356226/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1873487 Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules- nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 Status in linux-restricted-modules package in Ubuntu: New Bug description: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-lowlatency:5.4.0-24.28 Setting up linux-modules-nvidia-440-5.4.0-24-lowlatency (5.4.0-24.28) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-24-lowlatency.postinst: 44: 3: Bad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-24-lowlatency (--configure): installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 ErrorMessage: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873487] Re: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-inst
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+attachment/5356227/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1873487 Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules- nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 Status in linux-restricted-modules package in Ubuntu: New Bug description: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-lowlatency:5.4.0-24.28 Setting up linux-modules-nvidia-440-5.4.0-24-lowlatency (5.4.0-24.28) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-24-lowlatency.postinst: 44: 3: Bad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-24-lowlatency (--configure): installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 ErrorMessage: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873487] Re: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-inst
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+attachment/5356229/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1873487 Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules- nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 Status in linux-restricted-modules package in Ubuntu: New Bug description: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-lowlatency:5.4.0-24.28 Setting up linux-modules-nvidia-440-5.4.0-24-lowlatency (5.4.0-24.28) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-24-lowlatency.postinst: 44: 3: Bad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-24-lowlatency (--configure): installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 ErrorMessage: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873487] Re: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-inst
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+attachment/5356228/+files/uname-a.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1873487 Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules- nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 Status in linux-restricted-modules package in Ubuntu: New Bug description: fresh install of the daily (RC1) 2020.04.17, froze up > twice during install when using the normal (i.e., not safe) graphics mode. ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ubuntu-bug -p linux-restricted-modules ubuntu@ubuntu:~$ uname -a > uname-a.log ubuntu@ubuntu:~$ cat /proc/version_signature > version.log ubuntu@ubuntu:~$ dmesg > dmesg.log ubuntu@ubuntu:~$ sudo lspci -vnvn > lspci-vnvn.log ubuntu@ubuntu:~$ ls DesktopDownloads Pictures Templates dmesg.log uname-a.log Documents Music PublicVideos lspci-vnvn.log version.log ubuntu@ubuntu:~$ ping google.com PING google.com (172.217.164.174) 56(84) bytes of data. 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=1 ttl=57 time=11.7 ms 64 bytes from iad23s69-in-f14.1e100.net (172.217.164.174): icmp_seq=2 ttl=57 time=13.9 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 11.733/12.833/13.933/1.100 ms ubuntu@ubuntu:~$ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Apr 17 15:57:30 2020 DuplicateSignature: package:linux-modules-nvidia-440-5.4.0-24-lowlatency:5.4.0-24.28 Setting up linux-modules-nvidia-440-5.4.0-24-lowlatency (5.4.0-24.28) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-24-lowlatency.postinst: 44: 3: Bad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-24-lowlatency (--configure): installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 ErrorMessage: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-440-5.4.0-24-lowlatency 5.4.0-24.28 failed to install/upgrade: installed linux-modules-nvidia-440-5.4.0-24-lowlatency package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1873487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876429] Re: Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04
** 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/1876429 Title: Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Hello, after a fresh installation of Ubuntu 20.04, the keyboard backlight on the Dell Latitude E6400 laptop does not work. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876951] Re: Ubuntu 20.04 - freeze on latest kernel
** 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/1876951 Title: Ubuntu 20.04 - freeze on latest kernel Status in linux package in Ubuntu: New Bug description: Hi, yersterday I got the latest kernel (5.4.0-28) from official 20.04 repo, it freeze my notebook in less than a minute. Today I got the 5.4.0-29 but it behaves the same. No problem with previous version 5.4.0-26. I cannot see any interesting info in syslog :-( Does someone knows what's going on? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Description changed: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + Test Case + - + 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. + 2) Choose 'View report' + 3) Observe that 'ProcFB' is not collected + + With the version of apport from -proposed 'ProcFB' will be in the + report. + + + Regression Potential + + None, as we are just adding a symlink from linux-firmware to the linux source package hook. + + Original Description + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: - + InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) - PackageArchitecture: all - SourcePackage: linux-firmware + PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: - + DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: - linux-restricted-modules-5.4.0-21-generic N/A - linux-backports-modules-5.4.0-21-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-21-generic N/A + linux-backports-modules-5.4.0-21-generic N/A + linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: In Progress Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname:
[Kernel-packages] [Bug 1877192] Re: RTL8723bs bluetooth not working on 20.04
** 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/1877192 Title: RTL8723bs bluetooth not working on 20.04 Status in linux package in Ubuntu: New Bug description: I have Ubuntu 20.04 installed on atom-based tablet ACER Aspire Switch 10. And bluetooth does not work. In fact it looks like ubuntu does not recognize bluetooth HW at all. But the system does have bluetooth module which under windows is recognized as RTK8723 (ACPI\RTK8723\some-id) At the same time WiFi works without issues (the same module, if I am not mistaken). $ lsb_release -d Description:Ubuntu 20.04 LTS $ uname -vr 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 $ dmesg | grep -i 8723 [8.087918] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [8.088914] r8723bs: module verification failed: signature and/or required key missing - tainting kernel [8.092667] RTL8723BS: module init start [8.092671] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [8.092673] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [8.303955] RTL8723BS: rtw_ndev_init(wlan0) [8.304653] RTL8723BS: module init ret =0 [ 13.200223] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [ 17.832536] RTL8723BS: rtw_set_802_11_connect(wlan0) fw_state = 0x0008 [ 17.889893] RTL8723BS: start auth [ 17.892815] RTL8723BS: auth success, start assoc [ 17.901012] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !! [ 17.901053] RTL8723BS: assoc success [ 17.913846] RTL8723BS: send eapol packet [ 17.939873] RTL8723BS: send eapol packet [ 17.942652] RTL8723BS: set pairwise key camid:4, addr:50:c7:bf:31:a1:fa, kid:0, type:AES [ 17.944712] RTL8723BS: set group key camid:5, addr:50:c7:bf:31:a1:fa, kid:1, type:TKIP $ rfkill list all 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877476] Re: HP 820 G3 resume from hibernation hangs with color bars
** 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/1877476 Title: HP 820 G3 resume from hibernation hangs with color bars Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 5.4.0-29.33-generic 5.4.30 I am using Legacy mode in BIOS to boot laptop. I hibernate (I tried "systemctl hibernate" and "sudo hibernate") to swap file (allocated size 18GB what is 2GB more than my RAM size) and both methods hibernates to file OK. After hibernation I want to resume. First resume always ends suspended on color bars after ca 1 min and 2 times backlighted screen meantime. Keyboard driver can accept CTL+ALT+DEL to restart or I can power off and power on again. Second restart always loads grub normally and after I choose default ooot option it correctly resumes from swap file but it should work in this way from the first resume try. I've tried updated grub with options: nosplash, noquiet, nomodeset and even keeping shift in BIOS to see what's going during failed resume but no success. nomodeset option doesn't show color bars, but finishes with backlighted black screen only. Keeping shift in BIOS shows: " RUB loading" without G but after minute it ends on blank backlighted screen. Keeping ESC doesn't help to see any line from boot even nosplash and noquiet is active. Normal suspend and resume from suspend works but hibernation not. Only dmesg line is concerning, but I think nomodeset should eliminate if it would be i915 problem. [ 10.015720] i915 :00:02.0: [drm:intel_dp_aux_init_backlight_funcs [i915]] Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Anyway backlight controls is working OK without nomodeset option. HP BIOS is updated from 01/05/2020 and laptop is about 4 years old. System: Host: UB820 Kernel: 5.4.0-29-generic x86_64 bits: 64 Desktop: Gnome 3.36.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: HP product: HP EliteBook 820 G3 v: N/A serial: Mobo: HP model: 807C v: KBC Version 85.79 serial: UEFI [Legacy]: HP v: N75 Ver. 01.45 date: 01/05/2020 Battery: ID-1: BAT0 charge: 34.0 Wh condition: 35.1/35.1 Wh (100%) CPU: Topology: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 800 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel Display: x11 server: X.Org 1.20.8 driver: vesa unloaded: fbdev,modesetting resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.0.4 Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-29-generic Network: Device-1: Intel Ethernet I219-LM driver: e1000e IF: enp0s31f6 state: down mac: XX:XX:XX:XX:XX:XX Device-2: Intel Wireless 8260 driver: iwlwifi IF: wlp2s0 state: up mac: XX:XX:XX:XX:XX:XX Device-3: HP HP lt4120 Snapdragon X5 LTE type: USB driver: cdc_ether IF: enxda94de160772 state: up speed: N/A duplex: N/A mac: XX:XX:XX:XX:XX:XX Drives: Local Storage: total: 704.24 GiB used: 26.12 GiB (3.7%) ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB ID-2: /dev/sdb vendor: Samsung model: MZNLN256HCHP-000H1 size: 238.47 GiB Partition: ID-1: / size: 457.45 GiB used: 26.12 GiB (5.7%) fs: ext4 dev: /dev/sda1 Sensors: System Temperatures: cpu: 38.5 C mobo: 0.0 C Fan Speeds (RPM): N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877488] Re: External mouse movement wakes computer from hibernate
** Package changed: ubuntu-release-upgrader (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/1877488 Title: External mouse movement wakes computer from hibernate Status in linux package in Ubuntu: Incomplete Bug description: When the computer is suspended, moving the mouse (External logitech) causes the computer to come out of hibernation. I can tell because the Legion logo lights up. After a little while (minute?) it evidently suspends again because the logo turns off again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 7 19:07:34 2020 InstallationDate: Installed on 2020-03-12 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
** Package changed: ubuntu-release-upgrader (Ubuntu) => bcmwl (Ubuntu) -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: New Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
** Package changed: ubuntu-release-upgrader (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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Incomplete Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878445] Re: Ubuntu 20.04 arm64 server-cloud image hits kernel panic but boots successfully on retry
** Project changed: ubuntu-ubuntu-server => 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/1878445
Title:
Ubuntu 20.04 arm64 server-cloud image hits kernel panic but boots
successfully on retry
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is the image we are using:
https://cloud-images.ubuntu.com/releases/20.04/release/ubuntu-20.04-server-cloudimg-arm64.img
When the image boots, it first hits a kernel panic. Then the Grub menu
appears, counts down and
successfully boots.
From looking a bit at the grub config file: /boot/grub/grub.cfg, it seems to
attempt the first boot without any initrd.
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.4.0-28-generic
root=PARTUUID=a1dc7417-50de-4301-b9b4-ce567c4e4f27 ro quiet splash $vt_handoff
initrd/boot/initrd.img-5.4.0-28-generic
else
linux /boot/vmlinuz-5.4.0-28-generic
root=PARTUUID=a1dc7417-50de-4301-b9b4-ce567c4e4f27 ro quiet splash $vt_handoff
panic=-1
fi
The boot without an initrd seems to hit a panic. Then grub retries
the boot with the initrd and the boot succeeds.
It goes through this sequence every time we boot the image.
The question here is if there is any way to avoid this initial panic?
We understand that we could modify the grub.cfg to always use the intird.
That clearly eliminates the issue.
However, we were hoping for another option that avoids modifying a generated
file.
It is also worth mentioning that we tried the amd64 version of this
image, and it does not have this issue (ubuntu-20.04-server-cloudimg-
amd64.img).
Here is the console output from the panic:
[2.973416] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[2.974472] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.0-28-generic
#32-Ubuntu
[2.975376] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
[2.976305] Call trace:
[2.976625] dump_backtrace+0x0/0x188
[2.977094] show_stack+0x24/0x30
[2.977524] dump_stack+0xb4/0xf8
[2.978260] panic+0x14c/0x358
[2.978916] mount_block_root+0x244/0x2fc
[2.979776] mount_root+0x44/0x4c
[2.980488] prepare_namespace+0x138/0x1b8
[2.981367] kernel_init_freeable+0x26c/0x2b0
[2.982315] kernel_init+0x18/0x108
[2.983068] ret_from_fork+0x10/0x18
[2.983889] SMP: stopping secondary CPUs
[2.985013] Kernel Offset: disabled
[2.985772] CPU features: 0x0002,22208238
[2.986313] Memory Limit: none
This is our QEMU command line to launch the image:
qemu-system-aarch64 -nographic -machine virt,gic-version=max -m 4G -cpu max
-smp 8 -drive file=ubuntu.aarch64.img,if=none,id=drive0,cache=writeback -device
virtio-blk,drive=drive0,bootindex=0 -drive file=flash0.img,format=raw,if=pflash
-drive file=flash1.img,format=raw,if=pflash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878445/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Package changed: linux-signed-5.4 (Ubuntu) => linux-signed (Ubuntu) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-signed (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: systemd (Ubuntu Groovy) Importance: High Assignee: Balint Reczey (rbalint) Status: New ** Also affects: linux-signed (Ubuntu Groovy) Importance: Medium Assignee: Colin Ian King (colin-king) Status: New ** Tags removed: rls-ff-incoming rls-gg-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux source package in Focal: New Status in linux-signed source package in Focal: New Status in systemd source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882893] Re: vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)
** 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/1882893 Title: vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4) Status in linux package in Ubuntu: New Bug description: Recently, a couple of patches were upstreamed to Linux to upgrade vmxnet3 driver to version 4. Below are the commits: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with Linux kernel. Thanks, Yuhua Zou To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883012] Re: CPU stuck for 22s
** 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/1883012 Title: CPU stuck for 22s Status in linux package in Ubuntu: New Bug description: I get regularly system freezes, so that nothing works anymore. The only thing I can do, is a hard reset. These are the last kernel logs: Jun 10 21:34:47 stefano-linux anacron[6995]: Anacron 2.3 started on 2020-06-10 Jun 10 21:34:47 stefano-linux anacron[6995]: Normal exit (0 jobs run) Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:39:03 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:39:16 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:43 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:57 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:47:41 stefano-linux kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [JS Helper:2153] Jun 10 21:47:41 stefano-linux kernel: Modules linked in: snd_usb_audio snd_usbmidi_lib gspca_vc032x uvcvideo gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc snd_hda_codec_hdmi edac_mce_amd kvm_amd kvm nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(> Jun 10 21:47:41 stefano-linux kernel: CPU: 1 PID: 2153 Comm: JS Helper Tainted: P O 5.4.0-37-generic #41-Ubuntu Jun 10 21:47:41 stefano-linux kernel: Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 5407 12/31/2019 Jun 10 21:47:41 stefano-linux kernel: RIP: 0010:smp_call_function_many+0x203/0x270 Jun 10 21:47:41 stefano-linux kernel: Code: 73 08 e8 90 0e 96 00 3b 05 5e d4 6f 01 89 c7 0f 83 9b fe ff ff 48 63 c7 48 8b 0b 48 03 0c c5 80 59 04 9e 8b 41 18 a8 01 74 0a 90 8b 51 18 83 e2 01 75 f6 eb c8 89 cf 48 c7 c2 60 ae 44 9e 4c Jun 10 21:47:41 stefano-linux kernel: RSP: 0018:98bc02edbb58 EFLAGS: 0202 ORIG_RAX: ff13 Jun 10 21:47:41 stefano-linux kernel: RAX: 0003 RBX: 8890ce86bc80 RCX: b8bbfe817680 Jun 10 21:47:41 stefano-linux kernel: RDX: 0001 RSI: RDI: 0008 Jun 10 21:47:41 stefano-linux kernel: RBP: 98bc02edbb98 R08: 8890bfedc788 R09: 8890bfedc018 Jun 10 21:47:41 stefano-linux kernel: R10: 8890bfedc788 R11: R12: 9cc88c80 Jun 10 21:47:41 stefano-linux kernel: R13: 8890ce86a640 R14: 0001 R15: 0020 Jun 10 21:47:41 stefano-linux kernel: FS: 7f3c91505700() GS:8890ce84() knlGS: Jun 10 21:47:41 stefano-linux kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 10 21:47:41 stefano-linux kernel: CR2: 7fdb7324afe0 CR3: 000396ff CR4: 003406e0 Jun 10 21:47:41 stefano-linux kernel: Call Trace: Jun 10 21:47:41 stefano-linux kernel: native_flush_tlb_others+0x55/0x170 Jun 10 21:47:41 stefano-linux kernel: flush_tlb_mm_range+0xb4/0xe0 Jun 10 21:47:41 stefano-linux kernel: tlb_flush_mmu+0xb0/0x140 Jun 10 21:47:41 stefano-linux kernel: tlb_finish_mmu+0x42/0x80 Jun 10 21:47:41 stefano-linux kernel: unmap_region+0xf9/0x130 Jun 10 21:47:41 stefano-linux kernel: __do_munmap+0x291/0x4c0 Jun 10 21:47:41 stefano-linux kernel: mmap_region+0x240/0x670 Jun 10 21:47:41 stefano-linux kernel: do_mmap+0x3b4/0x5c0 Jun 10 21:47:41 stefano-linux kernel: vm_mmap_pgoff+0xcb/0x120 Jun 10 21:47:41 stefano-linux kernel: ksys_mmap_pgoff+0x5b/0x2a0 Jun 10 21:47:41 stefano-linux kernel: ? free_cpumask_var+0x9/0x10 Jun 10 21:47:41 stefano-linux kernel: __x64_sys_mmap+0x33/0x40 Jun 10 21:47:41 stefano-linux kernel: do_syscall_64+0x57/0x190 Jun 10 21:47:41 stefano-linux kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 10 21:47:41 stefano-linux kernel: RIP: 0033:0x7f3ca311f70d Jun 10 21:47:41 stefano-linux kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 f7 0c 00 f7 d8 64 89 01 48 Jun 10 21:47:41 stefano-linux kernel: RSP: 002b:7f3c91504b08 EFLAGS: 0246 ORIG_RAX: 0009 Jun 10 21:47:41 stefano-linux kernel: RAX: ffda RBX: RCX: 7f3ca311f70d Jun 10 21:47:41 stefano-linux kernel: RDX: RSI: 0060 RDI: 7f3c31d0 Jun 10 21:47:
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
I've tested the fix on 5.4.0-38-generic and the bug persists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881107] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884058] Re: kernel warning in epyc2 nested virtualization
** 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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: New Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885267] Re: Amd64 ppa kernel mainline build failing self test.
** 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/1885267 Title: Amd64 ppa kernel mainline build failing self test. Status in linux package in Ubuntu: Incomplete Bug description: Since kernel 5.6.18 / 5.7.2 and onwards, the amd64 kernel builds (and the s390x builds) in the kernel ppa at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D are failing self tests "Test amd64/self-tests failed (rc=2, on=amd64, time=0:00:57, log=amd64 /self-tests/log)" The log shows: ++ INSTALL headers CC test_stub.o BINARY test_verifier test_verifier.c:25:10: fatal error: sys/capability.h: No such file or directory 25 | #include | ^~ compilation terminated. make[2]: *** [Makefile:398: /home/kernel/COD/linux/tools/testing/selftests/bpf/test_verifier] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests/bpf' make[1]: *** [Makefile:157: all] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests' make: *** [debian/rules.d/1-maintainer.mk:170: compileselftests] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885259] Re: Logitech webcam microphone not working
** Tags added: focal ** 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/1885259 Title: Logitech webcam microphone not working Status in linux package in Ubuntu: Incomplete Bug description: I have a Logitech C922 Pro webcam which works perfectly on an Ubuntu 19.10 installation, but when plugged into my Ubuntu 20.04 system (with all released updates), there is no sound from the microphone, either as digital input or as "microphone" This has been tested with two identical webcams (my CEO has one too) and on three Ubuntu installations plus the 19.10 where the webcam still works as expected. dmesg output on plugging in the webcam: [ 1123.265098] usb 1-8: new high-speed USB device number 14 using xhci_hcd [ 1123.415363] usb 1-8: New USB device found, idVendor=046d, idProduct=085c, bcdDevice= 0.16 [ 1123.415369] usb 1-8: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 1123.415372] usb 1-8: Product: C922 Pro Stream Webcam [ 1123.415375] usb 1-8: SerialNumber: 16FFBB9F [ 1123.416467] uvcvideo: Found UVC 1.00 device C922 Pro Stream Webcam (046d:085c) [ 1123.418343] uvcvideo 1-8:1.0: Entity type for entity Processing 3 was not initialized! [ 1123.418347] uvcvideo 1-8:1.0: Entity type for entity Extension 6 was not initialized! [ 1123.418350] uvcvideo 1-8:1.0: Entity type for entity Extension 12 was not initialized! [ 1123.418353] uvcvideo 1-8:1.0: Entity type for entity Camera 1 was not initialized! [ 1123.418356] uvcvideo 1-8:1.0: Entity type for entity Extension 8 was not initialized! [ 1123.418359] uvcvideo 1-8:1.0: Entity type for entity Extension 9 was not initialized! [ 1123.418362] uvcvideo 1-8:1.0: Entity type for entity Extension 10 was not initialized! [ 1123.418364] uvcvideo 1-8:1.0: Entity type for entity Extension 11 was not initialized! [ 1123.418811] input: C922 Pro Stream Webcam as /devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input23 [ 1147.505572] usb 1-8: reset high-speed USB device number 14 using xhci_hcd lsusb output: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader Bus 001 Device 014: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam Bus 001 Device 003: ID 04ca:006d Lite-On Technology Corp. USB Device Bus 001 Device 005: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsmod | grep usb_audio snd_usb_audio 262144 1 snd_usbmidi_lib36864 1 snd_usb_audio snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm 106496 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common snd90112 29 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi Any ideas greatly appreciated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885266] Re: iwlwifi causes random UI freezes
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885266 Title: iwlwifi causes random UI freezes Status in linux package in Ubuntu: Incomplete Bug description: The GUI randomly freezes around every 10-15 minutes. This last for about 15-20 seconds before it gets back to normal. It started a few weeks ago. I can see entries in dmesg when this happens that make me suspect that it is caused by iwlwifi and/or a related driver of the Intel Wireless-AC 9260. [ 2313.312937] [ cut here ] [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [ 2313.312995] WARNING: CPU: 4 PID: 1424 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me memstick typec ecdh_generic mei soundcore ecc [ 2313.313022] processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci ipmi_devintf usb_storage [ 2313.313053] realtek idma64 libahci virt_dma ipmi_msghandler i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 10/16/2019 [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31 [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082 [ 2313.313073] RAX: RBX: be8e67d4fcd0 RCX: 0006 [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 96d9903178c0 [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 0004 [ 2313.313075] R10: R11: 0001 R12: 96d95de38018 [ 2313.313076] R13: R14: 96d95de39e4c R15: 0c04000c [ 2313.313077] FS: () GS:96d99030() knlGS: [ 2313.313078] CS: 0010 DS: ES: CR0: 80050033 [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 003606e0 [ 2313.313080] Call Trace: [ 2313.313089] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [ 2313.313099] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [ 2313.313103] ? __dev_printk+0x5c/0x6f [ 2313.313106] ? _dev_err+0x6c/0x83 [ 2313.313110] ? stop_one_cpu+0x73/0xa0 [ 2313.313118] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [ 2313.313124] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [ 2313.313130] iwl_pcie_irq_handle_error+0xb3/0x110 [iwlwifi] [ 2313.313136] iwl_pcie_irq_msix_handler+0x180/0x4a0 [iwlwifi] [ 2313.313140] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 2313.313142] irq_thread_fn+0x28/0x60 [ 2313.313144] irq_thread+0xda/0x170
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
** Package changed: kernel-package (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/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in linux package in Ubuntu: New Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common idma64 virt_dma cfg80211 memstick mei industrialio intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid acpi_pad intel_hid int3400_thermal sparse_keymap acpi_tad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_com
[Kernel-packages] [Bug 1885380] Re: ejecting mp3-CD doesn't leave tray open
** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1885380 Title: ejecting mp3-CD doesn't leave tray open Status in eject package in Ubuntu: New Bug description: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1885380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
