[Kernel-packages] [Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
This is feature request not a bug, So I haven't attached any logs in BZ. ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander Status in linux package in Ubuntu: Opinion Bug description: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi=160226366707807=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+subscriptions -- Mailing list: https://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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Tue, Oct 13, 2020 at 01:44:31PM -, jbuncle wrote: >I had the same issue (with both Ubuntu 20.04 and 20.10). It does seem to >be resolved after installing a 5.9 Kernel with the above patch applied >(from @coiby https://www.spinics.net/lists/linux-input/msg69458.html. Glad it works for you. You may want to reply to that email with the following content to make the patch accepted by the maintainer faster, Tested-by: Your_name The receiver should be linux-in...@vger.kernel.org. And put the following addresses in the CC filed, Jiri Kosina Benjamin Tissoires coiby...@gmail.com You should also put set the reply-to header to 20201009081100.3154-1-coiby...@gmail.com in your client client so the message will show in the same thread. And make sure use the plain text format. If you don't want go through these hassles, you may send your name to me by email so I'll do it on behalf of you. > >I have scripted the process I used (download, patch, compile and install >the kernel) for anyone else that's eager to get a working Touchpad on a >Ubuntu 20 installation on Lenovo Legion 5 (Obviously there may be >unwanted side effects of doing this). This will probably require Secure >Boot to be disabled in the BIOS. > >See GitHub Gist here: >https://gist.github.com/jbuncle/7dacde983b3c33b3b816b10e2fd2308a >Command for convenience: `bash <(curl >https://gist.githubusercontent.com/jbuncle/7dacde983b3c33b3b816b10e2fd2308a/raw/build-patched-kernel.sh)` > >Note the need for updating GRUB_CMDLINE_LINUX_DEFAULT with i2c- >hid.polling_mode=1 > >(First time I've built the Linux Kernel myself or even commented on >here!) Congratulations! >Thanks to @Coiby Xu (coiby) You are welcome! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Coiby, can you please work on a DMI based workaround in gpiolib-acpi.c? It'll have higher chance to get merged. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05
[Kernel-packages] [Bug 1899883] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1899883 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899883 Title: Tiger Lake PMC core driver fixes Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: New Bug description: The patchset in https://lore.kernel.org/lkml/20201006224702.12697-1-david.e@linux.intel.com/ provides several critical fixes for intel_pmc_core driver, one is specific for Tiger Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899882] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on Status in linux package in Ubuntu: Confirmed Bug description: XPS 13 9300 -- 50H3P53 -- Dell laptop WD19TB --- 4BWNW43 -- Dell Thunderbolt dock S2319HS -- B4TYZ13 -- Dell 23" external monitor External monitor remains black when waking system after suspending. Works OK when log out then log in or when reboot. Using HDMI cable from dock to monitor. From /var/log/syslog: Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here ] Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == PORT_A || port == PORT_E)) Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at drivers/gpu/drm/i915/display/intel_ddi.c:3179 intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common snd_soc_hd ac_hda snd_hda_codec_hdmi 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_compress snd_hda_codec_realtek ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t rigger industrialio_triggered_buffer iwlwifi kfifo_buf hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi cros_ec_i shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid hid video pinctrl_icelake pinctrl_intel Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg Tainted: GW 5.4.0-48-generic #52-Ubuntu Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 4c 89 e7 e8 8a c7 ff Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 EFLAGS: 00010282 Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: 9f1eebeca000 RCX: Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: 9dd955d5 RDI: 0246 Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP: b3bf012538a8 R08: 9dd955a0 R09: 0035 Oct 14 21:09:41 lt9 kernel: [32059.746857] R10: 9dd95980 R11: 9dd9559f R12: 9f1eebeca000 Oct 14 21:09:41 lt9 kernel: [32059.746858] R13: 9f1e1bb67000 R14: 9f1eebb8 R15: 9f1eebeca120 Oct 14 21:09:41 lt9 kernel: [32059.746861] FS: 7fd341ab0a80() GS:9f1eff78() knlGS: Oct 14 21:09:41 lt9 kernel: [32059.746863] CS: 0010 DS: ES: CR0: 80050033 Oct 14 21:09:41 lt9 kernel: [32059.746865] CR2: 0177088fa000 CR3: 00046e046003 CR4: 00760ee0 Oct 14 21:09:41 lt9 kernel: [32059.746866] PKRU: 5554 Oct 14
[Kernel-packages] [Bug 1899797] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1899797 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899797] Re: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899882] Re: hdmi monitor on
@John, could you try the oem kernel!? ** Changed in: linux (Ubuntu) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on Status in linux package in Ubuntu: Confirmed Bug description: XPS 13 9300 -- 50H3P53 -- Dell laptop WD19TB --- 4BWNW43 -- Dell Thunderbolt dock S2319HS -- B4TYZ13 -- Dell 23" external monitor External monitor remains black when waking system after suspending. Works OK when log out then log in or when reboot. Using HDMI cable from dock to monitor. From /var/log/syslog: Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here ] Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == PORT_A || port == PORT_E)) Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at drivers/gpu/drm/i915/display/intel_ddi.c:3179 intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common snd_soc_hd ac_hda snd_hda_codec_hdmi 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_compress snd_hda_codec_realtek ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t rigger industrialio_triggered_buffer iwlwifi kfifo_buf hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi cros_ec_i shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid hid video pinctrl_icelake pinctrl_intel Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg Tainted: GW 5.4.0-48-generic #52-Ubuntu Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 4c 89 e7 e8 8a c7 ff Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 EFLAGS: 00010282 Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: 9f1eebeca000 RCX: Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: 9dd955d5 RDI: 0246 Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP: b3bf012538a8 R08: 9dd955a0 R09: 0035 Oct 14 21:09:41 lt9 kernel: [32059.746857] R10: 9dd95980 R11: 9dd9559f R12: 9f1eebeca000 Oct 14 21:09:41 lt9 kernel: [32059.746858] R13: 9f1e1bb67000 R14: 9f1eebb8 R15: 9f1eebeca120 Oct 14 21:09:41 lt9 kernel: [32059.746861] FS: 7fd341ab0a80() GS:9f1eff78() knlGS: Oct 14 21:09:41 lt9 kernel: [32059.746863] CS: 0010 DS: ES: CR0: 80050033 Oct 14 21:09:41 lt9 kernel: [32059.746865] CR2: 0177088fa000 CR3: 00046e046003 CR4: 00760ee0 Oct 14 21:09:41 lt9 kernel: [32059.746866] PKRU:
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Tue, Oct 13, 2020 at 05:27:44AM -, Azizkhan wrote: >> i2c-hid.polling_mode=1 to the kernel boot parameters to make the >touchpad work. >you mean that I can just flash 5.9 kernel and then add to grub this line: >GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1 >i2c-hid.polling_mode=1" This patch hasn't been included in Linux 5.9. And I'm not sure when this patch will be accepted by the subsystem maintainer and eventually reach your distribution. But you can following the instructions in #211 and #212 to try this solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Additional notes to #211: Actually rebooting your machine is not necessary for simply testing the module. You can remove the old kernel first, $ sudo rmmod i2c-hid and then insert the new module with the parameter "polling_mode=1" $ sudo insmod i2c-hid.ko polling_mode=1 For have persistent effect, you need to add i2c-hid.polling_mode=1 to the kernel boot parameters to make the touchpad work after installing this new i2c-hid module following the instructions in #211. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5
[Kernel-packages] [Bug 1899883] [NEW] Tiger Lake PMC core driver fixes
Public bug reported: The patchset in https://lore.kernel.org/lkml/20201006224702.12697-1-david.e@linux.intel.com/ provides several critical fixes for intel_pmc_core driver, one is specific for Tiger Lake. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: somerville ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899883 Title: Tiger Lake PMC core driver fixes Status in linux package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: New Status in linux-oem-5.6 source package in Groovy: New Bug description: The patchset in https://lore.kernel.org/lkml/20201006224702.12697-1-david.e@linux.intel.com/ provides several critical fixes for intel_pmc_core driver, one is specific for Tiger Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899882] [NEW] hdmi monitor on
Public bug reported: XPS 13 9300 -- 50H3P53 -- Dell laptop WD19TB --- 4BWNW43 -- Dell Thunderbolt dock S2319HS -- B4TYZ13 -- Dell 23" external monitor External monitor remains black when waking system after suspending. Works OK when log out then log in or when reboot. Using HDMI cable from dock to monitor. >From /var/log/syslog: Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here ] Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == PORT_A || port == PORT_E)) Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at drivers/gpu/drm/i915/display/intel_ddi.c:3179 intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common snd_soc_hd ac_hda snd_hda_codec_hdmi 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_compress snd_hda_codec_realtek ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t rigger industrialio_triggered_buffer iwlwifi kfifo_buf hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi cros_ec_i shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid hid video pinctrl_icelake pinctrl_intel Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg Tainted: GW 5.4.0-48-generic #52-Ubuntu Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 4c 89 e7 e8 8a c7 ff Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 EFLAGS: 00010282 Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: 9f1eebeca000 RCX: Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: 9dd955d5 RDI: 0246 Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP: b3bf012538a8 R08: 9dd955a0 R09: 0035 Oct 14 21:09:41 lt9 kernel: [32059.746857] R10: 9dd95980 R11: 9dd9559f R12: 9f1eebeca000 Oct 14 21:09:41 lt9 kernel: [32059.746858] R13: 9f1e1bb67000 R14: 9f1eebb8 R15: 9f1eebeca120 Oct 14 21:09:41 lt9 kernel: [32059.746861] FS: 7fd341ab0a80() GS:9f1eff78() knlGS: Oct 14 21:09:41 lt9 kernel: [32059.746863] CS: 0010 DS: ES: CR0: 80050033 Oct 14 21:09:41 lt9 kernel: [32059.746865] CR2: 0177088fa000 CR3: 00046e046003 CR4: 00760ee0 Oct 14 21:09:41 lt9 kernel: [32059.746866] PKRU: 5554 Oct 14 21:09:41 lt9 kernel: [32059.746868] Call Trace: Oct 14 21:09:41 lt9 kernel: [32059.746930] ? intel_set_cpu_fifo_underrun_reporting+0x89/0x2a0 [i915] Oct 14 21:09:41 lt9 kernel: [32059.746984] intel_ddi_pre_enable+0x98/0x340 [i915] Oct 14 21:09:41 lt9 kernel: [32059.747000] ? drm_dp_mst_topology_put_port+0x27/0x40 [drm_kms_helper] Oct 14 21:09:41 lt9 kernel: [32059.747053]
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
For those who want to try the polling mode i2c-hid, here are the instructions to build a single i2c-hid module without building a whole kernel or downloading the whole kernel source code, 1. After you download the attached file which contains patched i2c-hid-core.c and other headers for building, run make to build this module, $ make make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory '/usr/lib/modules/5.9.0-1-MANJARO/build' AR /home/coiby/Desktop/kernel/other/i2c-hid_standalone/built-in.a CC [M] /home/coiby/Desktop/kernel/other/i2c-hid_standalone/i2c-hid-core.o CC [M] /home/coiby/Desktop/kernel/other/i2c-hid_standalone/i2c-hid-dmi-quirks.o LD [M] /home/coiby/Desktop/kernel/other/i2c-hid_standalone/i2c-hid.o MODPOST /home/coiby/Desktop/kernel/other/i2c-hid_standalone/Module.symvers CC [M] /home/coiby/Desktop/kernel/other/i2c-hid_standalone/i2c-hid.mod.o LD [M] /home/coiby/Desktop/kernel/other/i2c-hid_standalone/i2c-hid.ko make[1]: Leaving directory '/usr/lib/modules/5.9.0-1-MANJARO/build' 2. Copy i2c-hid.ko to override the current one whose path can be found by modinfo $ modinfo i2c-hid.ko filename: /lib/modules/5.9.0-1-MANJARO/kernel/drivers/hid/i2c-hid/i2c-hid.ko.xz $ cp i2c-hid.ko /lib/modules/5.9.0-1-MANJARO/kernel/drivers/hid/i2c-hid /i2c-hid.ko.xz 3. run depmod $ sudo depmod 4. reboot the system and play with your touchpad ** Attachment added: "i2c-hid_standalone.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5422428/+files/i2c-hid_standalone.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip
[Kernel-packages] [Bug 1899858] Re: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards
Can you please upload dmesg under 20.04? ** Changed in: linux (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/1899858 Title: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards Status in linux package in Ubuntu: Incomplete Bug description: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards. Either the module (ath9k) is missing or the "improved" version does not work. I am currently running Ubuntu MATE 18.04.5. Since this is no longer supported, I tried to install 20.04.1. Unfortunately this version does not support my WiFi hardware (versions 13.04-19.10 do). So I am stuck at 18.04 until 20.04 is actually ready to be released. (Is it an alpha version?) I tried a BrosTrend WiFi adapter from another computer since I have the driver on CD. That dose not work either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2340 F pulseaudio /dev/snd/controlC0: robert 2340 F pulseaudio CurrentDesktop: MATE Date: Wed Oct 14 21:04:17 2020 InstallationDate: Installed on 2019-12-22 (297 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889410] Re: Integrated Webcam always stops working after updates
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889410 Title: Integrated Webcam always stops working after updates Status in linux package in Ubuntu: Expired Bug description: I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu since version 16.04. Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04) on this laptop, the integrated webcam and mic works perfectly as intended. As soon as an update is installed (this happens to me now in 20.04) the webcam stops working. At the begining, this problem could be solved by simply uninstalling cheese and restarting: sudo apt-get --purge remove cheese sudo apt-get install cheese But another update on the system and now the webcam is again dead. This happened also in 16.04 and 18.04. No solution on internet seems to work. For now I use Droidcam along my cellphone. I can provide further details. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mijail 1834 F pulseaudio /dev/snd/controlC0: mijail 1834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-08 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: TOSHIBA Satellite S55-A NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite S55-A dmi.product.sku: PSKK6U dmi.product.version: PSKK6U-00X00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Expired Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] Re: Battery drain during sleep. System suspended before kernel suspends all tasks
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889083] Re: Touchpad hanging/jumping and Numpad not working - ASUS VivoBook M433IA
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889083 Title: Touchpad hanging/jumping and Numpad not working - ASUS VivoBook M433IA Status in linux package in Ubuntu: Expired Bug description: This issue is related to the issue 1810183 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183 This issue arises on a similar ASUS model, the M433IA, with the ryzen 4700 cpu, on Ubuntu 20.04.1 LTS Other than the integrated numpad not being illuminated and working, the touchpad itself has several issues: - The mouse sometimes hangs on 'scrolling', even using only one finger. - The pointer jumps from time to time, or even starts rapidly jumping up and down approx. 5cm. - The mouse sometimes is clicking without input (while jumping) - The mouse sometimes stops working completely, with no movement nor ability to click. This behavior happens with and without the synaptics drivers. Only work around is the usage of an external mouse. Ubuntu is installed in a dual-boot config and there are no issues when using Windows. The BIOS is updated to the latest version. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelina 1472 F pulseaudio /dev/snd/controlC0: angelina 1472 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 15:38:27 2020 InstallationDate: Installed on 2020-07-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X421IA_M433IA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=0185abb8-457b-4aaf-ac34-a228a22d286d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X421IA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X421IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX421IA.303:bd05/22/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX421IA_M433IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX421IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X421IA_M433IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882968] Re: ath10k_pci failed to wake target for write32
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899784] Re: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/al
*** This bug is a duplicate of bug 1883976 *** https://bugs.launchpad.net/bugs/1883976 Please stop Sophos Antivirus while upgrading/installing kernel related packages: $ sudo systemctl stop sav-protect.service ** This bug has been marked a duplicate of bug 1883976 package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899784 Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: no details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-51-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex978 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 15:26:10 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-51-generic:(not installed) Unpacking linux-modules-extra-5.4.0-51-generic (5.4.0-51.56) ... dpkg: error processing archive /tmp/apt-dpkg-install-V8BhvG/2-linux-modules-extra-5.4.0-51-generic_5.4.0-51.56_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-02 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F5S09J02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e353e192-f8f6-4408-bd84-7fe991c224ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: linux Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S09J02 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F5S09J02:pvrThinkPadX260:rvnLENOVO:rn20F5S09J02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S09J02 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899866] [NEW] bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to install module
Public bug reported:
When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package, the
process fails to build the module.
Below is the build log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.9.0-050900-generic
(x86_64)
Mon 12 Oct 2020 02:45:20 PM MDT
make: Entering directory '/usr/src/linux-headers-5.9.0-050900-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note:
...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1654:6:
error: implicit declaration of function ‘segment_eq’
[-Werror=implicit-function-declaration]
1654 | if (segment_eq(get_fs(), KERNEL_DS))
| ^~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:283:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:1784: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.9.0-050900-generic'
** Affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
--
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/1899866
Title:
bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to
install module
Status in bcmwl package in Ubuntu:
New
Bug description:
When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package,
the process fails to build the module.
Below is the build log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.9.0-050900-generic
(x86_64)
Mon 12 Oct 2020 02:45:20 PM MDT
make: Entering directory '/usr/src/linux-headers-5.9.0-050900-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1654:6:
error: implicit declaration of function ‘segment_eq’
[-Werror=implicit-function-declaration]
1654 | if (segment_eq(get_fs(), KERNEL_DS))
| ^~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
[Kernel-packages] [Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
SRU patches: https://lists.ubuntu.com/archives/kernel- team/2020-October/114076.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels Status in linux-kvm package in Ubuntu: New Bug description: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. [Regression potential] - I'm not aware of any. General consensus is that these options should have been =m all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
** Description changed: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. + + + [Regression potential] + + - I'm not aware of any. General consensus is that these options should + have been =m all along. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels Status in linux-kvm package in Ubuntu: New Bug description: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. [Regression potential] - I'm not aware of any. General consensus is that these options should have been =m all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
This is going to confuse the situation but your kernel log CurrentDmesg.txt shows the kernel keeps crashing in the video4linux webcam code. I don't *think* that's related to this bug, but it is filling your kernel log with crash reports. As for this bug... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Kernel-packages] [Bug 1874588] Re: [amdgpu] Flickering screen after waking up from Suspend
That said, it's unclear what kernel "5.16" is :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874588 Title: [amdgpu] Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Fix Released Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1874588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874588] Re: [amdgpu] Flickering screen after waking up from Suspend
Closed per comment #8 where the original reporter mentions the problem is fixed. Anyone else still experiencing issues, please open a new bug for each issue. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1874588 Title: [amdgpu] Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Fix Released Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1874588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
** Changed in: linux (Ubuntu) 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
This is the debdiff for focal. thx. ** Patch added: "alsa-lib_1.2.2-2.1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5422370/+files/alsa-lib_1.2.2-2.1ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746638] Re: [nouveau] [GeForce 6150SE nForce 430] PC freezes and crashes
OK "Won't Fix" because the original reporter can no longer contribute to the bug. If anyone else still experiences similar problems then please open new bugs. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746638 Title: [nouveau] [GeForce 6150SE nForce 430] PC freezes and crashes Status in linux package in Ubuntu: Won't Fix Status in xserver-xorg-video-nouveau package in Ubuntu: Won't Fix Bug description: When using the nouveau graphics driver my pc freezes and crashes. WORKAROUND: Use the proprietary nvidia driver. WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Thu Feb 1 01:36:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] [1043:8234] InstallationDate: Installed on 2017-11-23 (69 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050] Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 1 01:34:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 1241:1166MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
This is the debdiff for groovy. thx. ** Description changed: - This bug is for tracking purpose. + [Impact] + Recently the ucm added some amixer settings, like this one: + cset "name='rt711 ADC 23 Mux' 'MIC2'" + This setting is needed for Dell soundwire audio machines, and only + this setting is set correctly, the headset-mic could work. And we + already backported this ucm to focal. But the alsa-lib ctl parse + doesn't support the enum value in the '' yet, so this amixer setting + can't be set correctly under current focal and groovy, we need to + backport a patch from alsa-lib master branch. + + [Fix] + Backport a patch from upstream, this patch is not in the groovy + yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this + patch. + + [Test Case] + On the Dell soundwire audio machine, run alsactl init, then check if + the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set + correctly, it means the alsalib enum ctl parse support both "" and '' + now. + + + [Regression Risk] + This could introduce failure on setting enum amixer settings, users + will experience the failure of audio device like the speaker can't output + sound, the mic can't record sound. But this possibility is very low since + we have tested this SRU on many LENOVO and Dell machines (with and without + soundwire audio), all worked as fine as before. ** Patch added: "alsa-lib_1.2.3.2-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5422368/+files/alsa-lib_1.2.3.2-1ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899858] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899858 Title: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards Status in linux package in Ubuntu: Confirmed Bug description: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards. Either the module (ath9k) is missing or the "improved" version does not work. I am currently running Ubuntu MATE 18.04.5. Since this is no longer supported, I tried to install 20.04.1. Unfortunately this version does not support my WiFi hardware (versions 13.04-19.10 do). So I am stuck at 18.04 until 20.04 is actually ready to be released. (Is it an alpha version?) I tried a BrosTrend WiFi adapter from another computer since I have the driver on CD. That dose not work either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2340 F pulseaudio /dev/snd/controlC0: robert 2340 F pulseaudio CurrentDesktop: MATE Date: Wed Oct 14 21:04:17 2020 InstallationDate: Installed on 2019-12-22 (297 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899858] [NEW] Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards
Public bug reported: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards. Either the module (ath9k) is missing or the "improved" version does not work. I am currently running Ubuntu MATE 18.04.5. Since this is no longer supported, I tried to install 20.04.1. Unfortunately this version does not support my WiFi hardware (versions 13.04-19.10 do). So I am stuck at 18.04 until 20.04 is actually ready to be released. (Is it an alpha version?) I tried a BrosTrend WiFi adapter from another computer since I have the driver on CD. That dose not work either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2340 F pulseaudio /dev/snd/controlC0: robert 2340 F pulseaudio CurrentDesktop: MATE Date: Wed Oct 14 21:04:17 2020 InstallationDate: Installed on 2019-12-22 (297 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "hardinfo_report.html" https://bugs.launchpad.net/bugs/1899858/+attachment/5422341/+files/hardinfo_report.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899858 Title: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards Status in linux package in Ubuntu: New Bug description: Distribution 20.04.1 does not support Atheros 802.11n wireless LAN cards. Either the module (ath9k) is missing or the "improved" version does not work. I am currently running Ubuntu MATE 18.04.5. Since this is no longer supported, I tried to install 20.04.1. Unfortunately this version does not support my WiFi hardware (versions 13.04-19.10 do). So I am stuck at 18.04 until 20.04 is actually ready to be released. (Is it an alpha version?) I tried a BrosTrend WiFi adapter from another computer since I have the driver on CD. That dose not work either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2340 F pulseaudio /dev/snd/controlC0: robert 2340 F pulseaudio CurrentDesktop: MATE Date: Wed Oct 14 21:04:17 2020 InstallationDate: Installed on 2019-12-22 (297 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A
[Kernel-packages] [Bug 1899857] [NEW] [SRU] alsa-lib: support the enum value settings both in "" and in ''
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-lib (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-lib (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1894184 somerville ** Package changed: alsa-utils (Ubuntu) => alsa-lib (Ubuntu) ** Also affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Groovy) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-1894184 somerville ** Changed in: alsa-lib (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899857] [NEW] [SRU] alsa-lib: support the enum value settings both in "" and in ''
You have been subscribed to a public bug: This bug is for tracking purpose. ** Affects: alsa-lib (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New -- [SRU] alsa-lib: support the enum value settings both in "" and in '' https://bugs.launchpad.net/bugs/1899857 You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899721] Re: Dell XPS 9300 stops responding
Thanks for taking a look! Looks like I had the unofficial ubuntu docker installed (from https://get.docker.com/). docker-ce-cli/focal,now 5:19.03.13~3-0~ubuntu-focal amd64 [installed] docker-ce/focal,now 5:19.03.13~3-0~ubuntu-focal amd64 [installed] I'm switching to: docker.io/focal-updates,now 19.03.8-0ubuntu1.20.04 amd64 [installed] and will see how I go. Kim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899721 Title: Dell XPS 9300 stops responding Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on a new Dell XPS 13 9300 a few weeks ago and have been experiencing a number of hangs, where keyboard and mouse stop responding, requiring a reboot. I have two LG 27" monitors connected, one of which acts as a usb hub for an external apple keyboard and trackpad. I've attached a journal from the last boot that crashed using journalctl -b -1 --no-hostname -k > dmesg.txt Any help would be appreciated. Regards, Kim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kim3083 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 13:36:34 2020 InstallationDate: Installed on 2020-09-16 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=17be153f-3281-48bf-86c6-7d4af7253015 ro quiet splash pci=noaer mitigations=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd08/13/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
This is to confirm the issue as being reported here. I have the same issue as with other two systems that I’m trying to certify with 20.04LTS. Both systems could not be deployed. Below is the snapshot. Thanks Alec ** Attachment added: "Boot-Issue-when-deployimg-20.04LTS-for-hardware-server-certification" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+attachment/5422312/+files/Boot-up-issue-with-Maas-deploying-20.04LTS.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut Status in linux package in Ubuntu: Confirmed Bug description: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor:
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
** Tags added: blocks-hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut Status in linux package in Ubuntu: Confirmed Bug description: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug
[Kernel-packages] [Bug 1876963] Re: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04
New bug report created here: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1899848 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876963 Title: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04 Status in linux package in Ubuntu: Expired Bug description: Hi, I am am experiencing slow wifi for a Linksys WMP54GS v1.0 wireless PCI card with Ubuntu Server 20.04 installed, e.g. apt-get has taken 18 minutes 41 seconds to fetch 459Kb. Following the advice from https://ubuntuforums.org/showthread.php?t=2214110, I have installed the firmware-b43-installer package. The card is recognised and is sometimes allocated an IP. When it is connected, it is very slow. Using the wireless-info tool the logs for the wireless system configuration is given below. As shown in the logs the b43-pci-bridge driver is outputting an error message concerning the swiotlb is full. Has anybody managed to get the Linksys WMP54GS v1.0 card working on Ubuntu Server 20.04 using the b43 firmware supplied in package firmware-b43-installer? Since the log was produced I have also tired setting the REG_DOMAIN in /etc/default/crda but still does not work. ## wireless info START ## Report from: 04 May 2020 09:24 UTC + Booted last: 04 May 2020 00:00 UTC + Script from: 22 Oct 2018 03:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal # kernel Linux 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, maybe-ubiquity # desktop ### sed: can't read /root/.dmrc: No such file or directory Could not be determined. # lspci # 04:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) Subsystem: Packard Bell B.V. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [1631:e035] Kernel driver in use: 8139too 04:07.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Linksys WMP54GS v1.0 802.11g Wireless-G PCI Adapter with SpeedBooster [1737:0015] Kernel driver in use: b43-pci-bridge # lsusb # Bus 001 Device 005: ID 040b:650a Weltrend Semiconductor Bus 001 Device 004: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 002: ID 046a:010e Cherry GmbH USB Wireless Device Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub # PCMCIA card info ## 'pccardctl' is not installed (package "pcmciautils"). # rfkill ./wireless-info: line 192: rfkill: command not found # secure boot ### 'mokutil' is not installed (package "mokutil"). # lsmod # b43 417792 0 cordic 16384 1 b43 bcma 65536 1 b43 mac80211 843776 1 b43 cfg80211 704512 2 b43,mac80211 libarc4 16384 1 mac80211 mxm_wmi 16384 1 nouveau wmi 32768 2 mxm_wmi,nouveau ssb 73728 1 b43 # interfaces # ifconfig ## 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback brd inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth_lan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether brd 3: wlan0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether brd # iwconfig ## eth_lan0 no wireless extensions. lo no wireless extensions. wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off # route # # resolv.conf ### [777 root '/etc/resolv.conf' -> '../run/systemd/resolve/stub- resolv.conf'] nameserver 127.0.0.53 options edns0 # network managers ## Installed: None found. Running: None found. # NetworkManager info
[Kernel-packages] [Bug 1899848] [NEW] Broken WiFi Install on Ubuntu (MATE) 20.10 for BCM4306 (rev 03)
Public bug reported: Device ID: Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) WiFi worked correctly in Ubuntu MATE 20.04. Now I'm getting very slow throughput and constant error messages like the following: b43-pci-bridge :03:02.0: swiotlb buffer is full (sz: 2390 bytes), total 0 (slots), used 0 (slots) It sounds like this may be related to errors introduced in b43-fwcutter 1:019-5 with installing the wrong firmware, as reported in Debian bugs #958566 and #960279. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firmware-b43-installer 1:019-6 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Oct 14 14:52:18 2020 InstallationDate: Installed on 2019-12-08 (311 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all RebootRequiredPkgs: bcmwl-kernel-source bcmwl-kernel-source SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to groovy on 2020-10-12 (2 days ago) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1899848 Title: Broken WiFi Install on Ubuntu (MATE) 20.10 for BCM4306 (rev 03) Status in b43-fwcutter package in Ubuntu: New Bug description: Device ID: Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) WiFi worked correctly in Ubuntu MATE 20.04. Now I'm getting very slow throughput and constant error messages like the following: b43-pci-bridge :03:02.0: swiotlb buffer is full (sz: 2390 bytes), total 0 (slots), used 0 (slots) It sounds like this may be related to errors introduced in b43-fwcutter 1:019-5 with installing the wrong firmware, as reported in Debian bugs #958566 and #960279. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firmware-b43-installer 1:019-6 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Oct 14 14:52:18 2020 InstallationDate: Installed on 2019-12-08 (311 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all RebootRequiredPkgs: bcmwl-kernel-source bcmwl-kernel-source SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to groovy on 2020-10-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1899848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899848] Re: Broken WiFi Install on Ubuntu (MATE) 20.10 for BCM4306 (rev 03)
I attempted to install "bcmwl-kernel-source" as an alternative. As documentation indicated, this did not work with my hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1899848 Title: Broken WiFi Install on Ubuntu (MATE) 20.10 for BCM4306 (rev 03) Status in b43-fwcutter package in Ubuntu: New Bug description: Device ID: Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) WiFi worked correctly in Ubuntu MATE 20.04. Now I'm getting very slow throughput and constant error messages like the following: b43-pci-bridge :03:02.0: swiotlb buffer is full (sz: 2390 bytes), total 0 (slots), used 0 (slots) It sounds like this may be related to errors introduced in b43-fwcutter 1:019-5 with installing the wrong firmware, as reported in Debian bugs #958566 and #960279. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firmware-b43-installer 1:019-6 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Oct 14 14:52:18 2020 InstallationDate: Installed on 2019-12-08 (311 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all RebootRequiredPkgs: bcmwl-kernel-source bcmwl-kernel-source SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to groovy on 2020-10-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1899848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892973] Re: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
https://pastebin.pl/view/48fb2f2c journalctl -b-1 https://pastebin.pl/view/4d6cc063 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1898808] [NEW] [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
You have been subscribed to a public bug: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected bionic focal uec-images -- [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut https://bugs.launchpad.net/bugs/1898808 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1899503] Re: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD
The following is a reply from the ssd provider. I could could independently find info online regarding new firmwares. Note that Sandisk was folded into Western Digital. "These are newest WD branded drives and WD already confirmed they are the newest firmware / no upgrades are available." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899503 Title: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD Status in linux package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/oem-priority/+bug/1872383 OS: Ubuntu 20.04 Kernel Affected: 5.4.0-48-generic and mainline/5.8.12-050812-generic Device: Sandisk Skyhawk NVME SSD FileSystem: Ext4 Eerror (Caused by newly formatted and mounted Ext4 partition. Can confirm the errors are thrown by the ext4lazyInit kernel thread) - [ 6305.633884] print_req_error: 20 callbacks suppressed [ 6305.633887] blk_update_request: operation not supported error, dev nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 [ 6305.639529] blk_update_request: operation not supported error, dev nvme0n1, sector 340812289 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 Sandisk Skyhawk nvme firmware version/info Node SN Model Namespace Usage Format FW Rev /dev/nvme0n1 A04506C0 SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A /dev/nvme1n1 A04507FB SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A Both identical drives have same issue so not related to a single defective drive. lspci output 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] 01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Skyhawk Series NVME SSD [15b7:2001] (rev 01) 03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01) 03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev
[Kernel-packages] [Bug 1899503] Re: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD
The drive in question is also known as (aka rebranded as) Western Digital Ultrastar DC SN620 series after Sandisk acquisition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899503 Title: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD Status in linux package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/oem-priority/+bug/1872383 OS: Ubuntu 20.04 Kernel Affected: 5.4.0-48-generic and mainline/5.8.12-050812-generic Device: Sandisk Skyhawk NVME SSD FileSystem: Ext4 Eerror (Caused by newly formatted and mounted Ext4 partition. Can confirm the errors are thrown by the ext4lazyInit kernel thread) - [ 6305.633884] print_req_error: 20 callbacks suppressed [ 6305.633887] blk_update_request: operation not supported error, dev nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 [ 6305.639529] blk_update_request: operation not supported error, dev nvme0n1, sector 340812289 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 Sandisk Skyhawk nvme firmware version/info Node SN Model Namespace Usage Format FW Rev /dev/nvme0n1 A04506C0 SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A /dev/nvme1n1 A04507FB SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A Both identical drives have same issue so not related to a single defective drive. lspci output 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] 01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Skyhawk Series NVME SSD [15b7:2001] (rev 01) 03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01) 03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01) 03:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01) 20:00.0 PCI bridge [0604]: Advanced Micro
[Kernel-packages] [Bug 1876963] Re: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04
Similar problem, same hardware. Really low throughput, and my logs are getting spammed with the following error since upgrading from Ubuntu MATE 20.04 to 20.10 beta. It worked fine in 20.04: b43-pci-bridge :03:02.0: swiotlb buffer is full (sz: 2390 bytes), total 0 (slots), used 0 (slots) According to the bcm43xx Ubunti Wiki, my hardware isn't supported by "bcmwl-kernel-source". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876963 Title: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04 Status in linux package in Ubuntu: Expired Bug description: Hi, I am am experiencing slow wifi for a Linksys WMP54GS v1.0 wireless PCI card with Ubuntu Server 20.04 installed, e.g. apt-get has taken 18 minutes 41 seconds to fetch 459Kb. Following the advice from https://ubuntuforums.org/showthread.php?t=2214110, I have installed the firmware-b43-installer package. The card is recognised and is sometimes allocated an IP. When it is connected, it is very slow. Using the wireless-info tool the logs for the wireless system configuration is given below. As shown in the logs the b43-pci-bridge driver is outputting an error message concerning the swiotlb is full. Has anybody managed to get the Linksys WMP54GS v1.0 card working on Ubuntu Server 20.04 using the b43 firmware supplied in package firmware-b43-installer? Since the log was produced I have also tired setting the REG_DOMAIN in /etc/default/crda but still does not work. ## wireless info START ## Report from: 04 May 2020 09:24 UTC + Booted last: 04 May 2020 00:00 UTC + Script from: 22 Oct 2018 03:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal # kernel Linux 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, maybe-ubiquity # desktop ### sed: can't read /root/.dmrc: No such file or directory Could not be determined. # lspci # 04:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) Subsystem: Packard Bell B.V. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [1631:e035] Kernel driver in use: 8139too 04:07.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Linksys WMP54GS v1.0 802.11g Wireless-G PCI Adapter with SpeedBooster [1737:0015] Kernel driver in use: b43-pci-bridge # lsusb # Bus 001 Device 005: ID 040b:650a Weltrend Semiconductor Bus 001 Device 004: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 002: ID 046a:010e Cherry GmbH USB Wireless Device Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub # PCMCIA card info ## 'pccardctl' is not installed (package "pcmciautils"). # rfkill ./wireless-info: line 192: rfkill: command not found # secure boot ### 'mokutil' is not installed (package "mokutil"). # lsmod # b43 417792 0 cordic 16384 1 b43 bcma 65536 1 b43 mac80211 843776 1 b43 cfg80211 704512 2 b43,mac80211 libarc4 16384 1 mac80211 mxm_wmi 16384 1 nouveau wmi 32768 2 mxm_wmi,nouveau ssb 73728 1 b43 # interfaces # ifconfig ## 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback brd inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth_lan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether brd 3: wlan0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether brd # iwconfig ## eth_lan0 no wireless extensions. lo no wireless extensions. wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off # route # #
[Kernel-packages] [Bug 1892728] Re: ec2-hibinit-agent needs to properly initialize swap file
** Description changed:
- With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return
- errors"), applied to v5.6-rc1, running swapon on a file that has holes
- returns an error (EINVAL); hibinit-agent is creating the swap file just
- using fallocate(), without touching the whole file by deafult, so there
- might be holes, swapon fails and hibernation cannot be performed.
+ SRU Justification
+
+ Impact: Running swapon on ext4 with a file with holes fails in the
+ Groovy 5.8 kernel. This prevents using swap files created using
+ fallocate(), which prevents hibernation in EC2.
+
+ Fix: Commit 424de74af0d0679e99660904a5f472acd85bdb73 from linux-next
+ implements swap_activate aops to fix this issue.
+
+ Test Case: Run swapon with a file allocated using fallocate() in an ext4
+ filesystem. With the fix this should be successful, and it should be
+ possible to hibernate/resume an EC2 instance using such a swapfile.
+
+ Regression Potential: The code changes only impact activating swap on
+ ext4, so regressions are possible for this operation. All other
+ operations should not be impacted.
+
+ ---
+
+
+ With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return
errors"), applied to v5.6-rc1, running swapon on a file that has holes returns
an error (EINVAL); hibinit-agent is creating the swap file just using
fallocate(), without touching the whole file by deafult, so there might be
holes, swapon fails and hibernation cannot be performed.
To prevent this problem we need to touch the swap file before using it
and this can be done setting "touch-swap = True" in /etc/hibinit-
config.cfg.
The downside of this setting is that a new instance requires more time
to be properly "initialized" the first time it boots due to the extra
I/O required to touch the swap file (this additional I/O can be quite
consistent in large instances, like c5.18xlarge for example), but I
don't see a better way to make sure the file is all allocated without
holes, so I guess we need to turn on this option if we want to use
hibernation w/ kernels >= 5.6.
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892728
Title:
ec2-hibinit-agent needs to properly initialize swap file
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification
Impact: Running swapon on ext4 with a file with holes fails in the
Groovy 5.8 kernel. This prevents using swap files created using
fallocate(), which prevents hibernation in EC2.
Fix: Commit 424de74af0d0679e99660904a5f472acd85bdb73 from linux-next
implements swap_activate aops to fix this issue.
Test Case: Run swapon with a file allocated using fallocate() in an
ext4 filesystem. With the fix this should be successful, and it should
be possible to hibernate/resume an EC2 instance using such a swapfile.
Regression Potential: The code changes only impact activating swap on
ext4, so regressions are possible for this operation. All other
operations should not be impacted.
---
With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return
errors"), applied to v5.6-rc1, running swapon on a file that has holes returns
an error (EINVAL); hibinit-agent is creating the swap file just using
fallocate(), without touching the whole file by deafult, so there might be
holes, swapon fails and hibernation cannot be performed.
To prevent this problem we need to touch the swap file before using it
and this can be done setting "touch-swap = True" in /etc/hibinit-
config.cfg.
The downside of this setting is that a new instance requires more time
to be properly "initialized" the first time it boots due to the extra
I/O required to touch the swap file (this additional I/O can be quite
consistent in large instances, like c5.18xlarge for example), but I
don't see a better way to make sure the file is all allocated without
holes, so I guess we need to turn on this option if we want to use
hibernation w/ kernels >= 5.6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892728/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897963] Re: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode
Could this also be applied to the bionic branch? Thanks and best regards! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897963 Title: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: Basically a null pointer dereference was happening while using a lenovo usb-c dock. The issue has been addressed upstream with commit: https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4 Apparently the dock kept sending altmode information repeatedly, and the kernel did not expect this to happen, a check was added to make sure it only observes the amount of altmodes limited by the standard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 15:40:24 2020 InstallationDate: Installed on 2020-09-30 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-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/1897963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899514] Re: Dependency update needed
Somehow it's fixed -- 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/1899514 Title: Dependency update needed Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 20.04.1 here. Upon executing "sudo ubuntu-drivers install", I get the following output: linux-modules-nvidia-450-generic-hwe-20.04 : Depends: nvidia-kernel- common-450 (<= 450.66-1) but 450.80.02-0ubuntu0.20.04.2 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1899514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899832] [NEW] CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
Public bug reported: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** No longer affects: cloud-images ** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels Status in linux-kvm package in Ubuntu: New Bug description: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
Kernel SRU request submitted for focal: https://lists.ubuntu.com/archives/kernel-team/2020-October/thread.html#114069 changing status to 'In Progress' for focal. ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * A problem occurs with 32-bit ino_t values on 64-bit architectures (like s390x). * Without this patch, cephfs kernel client does not work properly on s390x: the initial symtom is missing the first created file/directory on cephfs mount point as reported in https://tracker.ceph.com/issues/46828. [Fix] * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit ino_t" * backport for focal: https://launchpadlibrarian.net/501822049/0001 -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch [Test Case] * IBM Development team and Test team have carried out simple testing and stress testing by automatically creating many Ceph clusters on s390x (with different configuration each time), doing the cephfs kernel mounting, checking inode numbers, running stress tests. The same procedures were done on x86_64 arch by Test team. [Regression Potential] * There is a certain regression risk with this patch, since: * common ceph filesystem code in fs/ceph/ is modified * the inode handling is touched * ceph is used for supplemental volumes * and as the original author of this patch (Jeff Layton) wrote in the commit message, the potential issue might happen on 32-bit arches only and he also provided workaround for those arches. [Other] * The above patch/commit was upstream accepted with kernel 5.9. * Cherry picking the patch/commit to groovy works fine, hence this SRU. * For focal a cherry pick does not apply cleanly, hence a backport got added to LP 1899582. __ Backport provided for git-commit to 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebce3eb2f7ef9f6ef01a60874ebd232450107c9a Backport patch attached for commit ebce3eb upstream. It was applied and tested on top of Ubuntu commit : linux (5.4.0-48.52) focal; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
Kernel test builds based on groovy master-next (cherry-pick) and focal master-next (backport) are available here for further testing: https://people.canonical.com/~fheimes/lp1899582/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * A problem occurs with 32-bit ino_t values on 64-bit architectures (like s390x). * Without this patch, cephfs kernel client does not work properly on s390x: the initial symtom is missing the first created file/directory on cephfs mount point as reported in https://tracker.ceph.com/issues/46828. [Fix] * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit ino_t" * backport for focal: https://launchpadlibrarian.net/501822049/0001 -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch [Test Case] * IBM Development team and Test team have carried out simple testing and stress testing by automatically creating many Ceph clusters on s390x (with different configuration each time), doing the cephfs kernel mounting, checking inode numbers, running stress tests. The same procedures were done on x86_64 arch by Test team. [Regression Potential] * There is a certain regression risk with this patch, since: * common ceph filesystem code in fs/ceph/ is modified * the inode handling is touched * ceph is used for supplemental volumes * and as the original author of this patch (Jeff Layton) wrote in the commit message, the potential issue might happen on 32-bit arches only and he also provided workaround for those arches. [Other] * The above patch/commit was upstream accepted with kernel 5.9. * Cherry picking the patch/commit to groovy works fine, hence this SRU. * For focal a cherry pick does not apply cleanly, hence a backport got added to LP 1899582. __ Backport provided for git-commit to 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebce3eb2f7ef9f6ef01a60874ebd232450107c9a Backport patch attached for commit ebce3eb upstream. It was applied and tested on top of Ubuntu commit : linux (5.4.0-48.52) focal; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899258] Re: touchpad not work
All my Fn buttons are working exept the 2 buttons used for luminosity - and + (F11 and F12) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899826] [NEW] backport upstream fixes for 5.9 Linux support
Public bug reported:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a later
change, so one can backport this with just the following 4 changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add linux/blkdev.h
include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning, so
the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping the
accounting for inactive anonymous pages and reclaimable pages on the
slab. This change removes a very minor component of the free memory
calculation and speeds up arc free stats calculations. There is a
potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block allocation
queue due to API changes, so should not change behaviour for current 5.8
kernels, only change behaviour for newer kernels with the newer kernel
API. Hence for the released 5.8 groovy kernel the code will not be
changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to build
on newer kernels, so the risk on this change is effectively zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
** Affects: zfs-linux (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
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/1899826
Title:
backport upstream fixes for 5.9 Linux support
Status in zfs-linux package in Ubuntu:
In Progress
Bug description:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a
later change, so one can backport this with just the following 4
changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add
linux/blkdev.h include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning,
so the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping
the accounting for inactive anonymous pages and reclaimable pages on
the slab. This change removes a very minor component of the free
memory calculation and speeds up arc free stats calculations. There is
a potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block
allocation queue due to API changes, so should not change behaviour
for current 5.8 kernels, only change behaviour for newer kernels with
the newer kernel API. Hence for the released 5.8 groovy kernel the
code will not be changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to
build on newer kernels, so the risk on this change is effectively
zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+subscriptions
--
[Kernel-packages] [Bug 1899258] Re: touchpad not work
The number of IRQ 9 (acpi) seems to be unreasonably high, i.e. 10 in ProcInterrupts.txt I tried on my laptop (command: "uptime ; cat /proc/interrupts | grep acpi"), and it is 15859 after 13 mins (~8000 when uptime = 0 min). If you see 10 right after booting, the hardware / firmware may be mis- behaving. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Hello, I got that kind of error too, but it was hardware related. My NIC had PXE enabled but was not recognized by the kernel (igb & "NVM Checksum Is Not Valid"). I had to boot with a live CD to confirm the NIC issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Invalid Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell inspiron 5758 i5-5200 (dearest-team) - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899258] Re: touchpad not work
The below is likely the reason that fn keys do not work, i.e. irq 9 (acpi) are disabled because it is not handled. [9.932829] irq 9: nobody cared (try booting with the "irqpoll" option) [9.932832] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.0-48-generic #52-Ubuntu [9.932833] Hardware name: LENOVO 81WE/LNVNB161216, BIOS EMCN13WW 03/06/2020 [9.932833] Call Trace: [9.932835] [9.932840] dump_stack+0x6d/0x9a [9.932842] __report_bad_irq+0x3a/0xaf [9.932843] note_interrupt.cold+0xb/0x61 [9.932844] handle_irq_event_percpu+0x73/0x80 [9.932845] handle_irq_event+0x3b/0x5a [9.932846] handle_fasteoi_irq+0x9c/0x150 [9.932847] do_IRQ+0x55/0xf0 [9.932849] common_interrupt+0xf/0xf [9.932849] [9.932851] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [9.932852] Code: ff e8 1f d4 80 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 52 3d 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [9.932853] RSP: 0018:b86b400e3e38 EFLAGS: 0246 ORIG_RAX: ffde [9.932854] RAX: 893d12a6ad00 RBX: a3169000 RCX: 001f [9.932854] RDX: RSI: 6b86e1b8 RDI: [9.932854] RBP: b86b400e3e78 R08: 00025009bec1 R09: 7fff [9.932855] R10: 893d12a69a00 R11: 893d12a699e0 R12: 893d0f97f400 [9.932855] R13: 0001 R14: 0001 R15: 893d0f97f400 [9.932857] ? cpuidle_enter_state+0xa1/0x450 [9.932857] cpuidle_enter+0x2e/0x40 [9.932859] call_cpuidle+0x23/0x40 [9.932859] do_idle+0x1dd/0x270 [9.932860] cpu_startup_entry+0x20/0x30 [9.932862] start_secondary+0x167/0x1c0 [9.932863] secondary_startup_64+0xa4/0xb0 [9.932864] handlers: [9.932866] [<14286725>] acpi_irq [9.932867] Disabling IRQ #9 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1719731] Re: Suspending Lubuntu 16.04.3 results in network manager stops working
** Tags removed: manager network suspending suspension ** Tags added: suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719731 Title: Suspending Lubuntu 16.04.3 results in network manager stops working Status in linux package in Ubuntu: Confirmed Bug description: Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the network manager stops working or better it behaves weird. I noticed 4 behaviors in different occasions: 1) Enable networking and enable wifi are toggled but the connection I used before suspending is not shown (others are). 2) Enable networking and enable wifi are toggled but no Wi-Fi connections are displayed. 3) The icon changes to loading but it gets stuck, sometimes it just stays like that until I restart the network manager or sometimes it unstucks and connects, but instead of showing the "internet bars" for Wi-Fi it shows the icon as when you connect to a wired connection. 3)The network manager menu is grey and you can't click anything (no connections are shown). The only way I have is either to restart nm-applet or restart Lubuntu. I have seen this behavior for maybe 3 days, therefore I am assuming one package was updated and the update messes up with the suspending system. The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power Manager is 1.4.4-4ubuntu2. Can someone investigate? Has anyone else experienced this? If more info are needed I will try to do my best :) Update: seems it the error I mentioned in my last message was reported on XFCE: https://bugzilla.xfce.org/show_bug.cgi?id=12317 don't know if it is any useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883905] Re: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL
Hui Wang also provided some workaround for touchpad at LP:1899258. If kernel updates do not fix touchpad problem, you can also try the kernel parameters. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883905 Title: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL Status in linux package in Ubuntu: Incomplete Bug description: Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and Ubuntu 20.04. Touchpad works on Windows. The touchpad does not show up in xinput --list and in the devices (included in the attachment). Its manufacturer is Elantech, at least I suppose it is, based on an output from acpidump which has shown: 27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48 TY.p.ELAN0633._H on one line. If it is in fact my touchpad and its ID is 0633, then it is not included in elan_i2c_core.c file in my ubuntu kernel source (IDs end at 0632). I tried to modify it myself and compile a new, custom kernel, but I am quite new to linux so I failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maciek 3356 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 14:50:45 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=9baf434c-2f39-433d-b9ec-ed69c897ef46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883905] Re: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL
The id ELAN0633 has been added since Ubuntu-5.4.0-34.38. Please update kernel (sudo apt update && sudo apt upgrade -y) and verify whether the touchpad works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883905 Title: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL Status in linux package in Ubuntu: Incomplete Bug description: Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and Ubuntu 20.04. Touchpad works on Windows. The touchpad does not show up in xinput --list and in the devices (included in the attachment). Its manufacturer is Elantech, at least I suppose it is, based on an output from acpidump which has shown: 27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48 TY.p.ELAN0633._H on one line. If it is in fact my touchpad and its ID is 0633, then it is not included in elan_i2c_core.c file in my ubuntu kernel source (IDs end at 0632). I tried to modify it myself and compile a new, custom kernel, but I am quite new to linux so I failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maciek 3356 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 14:50:45 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=9baf434c-2f39-433d-b9ec-ed69c897ef46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838258] Re: Unable to configure VLAN on an additional OSA interface
** Tags added: fr-585 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Incomplete Status in iproute2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: fr-79 -- You 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 OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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 1815691] Re: disk not detected on an Intel NUC7i5BNHXF
** Tags added: fr-295 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815691 Title: disk not detected on an Intel NUC7i5BNHXF Status in linux package in Ubuntu: Expired Status in ubiquity package in Ubuntu: Invalid Status in linux source package in Disco: Expired Status in ubiquity source package in Disco: Invalid Bug description: I attempted to install Ubuntu from multiple ISOs, made with dd to a USB disk, onto an Intel NUC7i5BNHXF and none of them were able to detect the disk on the system. I was able to successfully install Ubuntu 16.04! using the image identified linked to from here: https://www.ubuntu.com/download/iot/intel-nuc-desktop Attached you will find the syslog files from the the different live environments from which I was unable to install Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892728] Re: ec2-hibinit-agent needs to properly initialize swap file
It seems the kernel needs to be fixed, because fallocate changed in the kernel
according to Andrea:
https://lkml.org/lkml/2020/9/4/259
** Package changed: ec2-hibinit-agent (Ubuntu Groovy) => linux (Ubuntu Groovy)
** Changed in: linux (Ubuntu Groovy)
Assignee: Balint Reczey (rbalint) => (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/1892728
Title:
ec2-hibinit-agent needs to properly initialize swap file
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Groovy:
Incomplete
Bug description:
With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly
return errors"), applied to v5.6-rc1, running swapon on a file that
has holes returns an error (EINVAL); hibinit-agent is creating the
swap file just using fallocate(), without touching the whole file by
deafult, so there might be holes, swapon fails and hibernation cannot
be performed.
To prevent this problem we need to touch the swap file before using it
and this can be done setting "touch-swap = True" in /etc/hibinit-
config.cfg.
The downside of this setting is that a new instance requires more time
to be properly "initialized" the first time it boots due to the extra
I/O required to touch the swap file (this additional I/O can be quite
consistent in large instances, like c5.18xlarge for example), but I
don't see a better way to make sure the file is all allocated without
holes, so I guess we need to turn on this option if we want to use
hibernation w/ kernels >= 5.6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892728/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892728] [NEW] ec2-hibinit-agent needs to properly initialize swap file
You have been subscribed to a public bug:
With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return
errors"), applied to v5.6-rc1, running swapon on a file that has holes
returns an error (EINVAL); hibinit-agent is creating the swap file just
using fallocate(), without touching the whole file by deafult, so there
might be holes, swapon fails and hibernation cannot be performed.
To prevent this problem we need to touch the swap file before using it
and this can be done setting "touch-swap = True" in /etc/hibinit-
config.cfg.
The downside of this setting is that a new instance requires more time
to be properly "initialized" the first time it boots due to the extra
I/O required to touch the swap file (this additional I/O can be quite
consistent in large instances, like c5.18xlarge for example), but I
don't see a better way to make sure the file is all allocated without
holes, so I guess we need to turn on this option if we want to use
hibernation w/ kernels >= 5.6.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Balint Reczey (rbalint)
Status: Incomplete
** Affects: linux (Ubuntu Groovy)
Importance: High
Assignee: Balint Reczey (rbalint)
Status: Incomplete
** Tags: fr-205 id-5f47d0f8b8ce963bb1e25973
--
ec2-hibinit-agent needs to properly initialize swap file
https://bugs.launchpad.net/bugs/1892728
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
That's great news. Let's keep this bug open for the moment as "incomplete" and if you don't report back after ~6 weeks or so it will automatically be closed. -- 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/1899249 Title: OpenZFS writing stalls, under load Status in Native ZFS for Linux: Unknown Status in zfs-linux package in Ubuntu: Incomplete Bug description: Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry Pi 8GB. ZFS deduplication, and LZJB compression is enabled. This issue seems to occur, intermittently, after some time (happens with both SMB access, via Samba, and when interacting with the system, via SSH), and never previously occurred, until a few months ago, and I sometimes have to force a reboot of the system (at the cost of some data loss), in order to use it again. The "dmesg" log reports: [25375.911590] z_wr_iss_h D0 2161 2 0x0028 [25375.911606] Call trace: [25375.911627] __switch_to+0x104/0x170 [25375.911639] __schedule+0x30c/0x7c0 [25375.911647] schedule+0x3c/0xb8 [25375.911655] io_schedule+0x20/0x58 [25375.911668] rq_qos_wait+0x100/0x178 [25375.911677] wbt_wait+0xb4/0xf0 [25375.911687] __rq_qos_throttle+0x38/0x50 [25375.911700] blk_mq_make_request+0x128/0x610 [25375.911712] generic_make_request+0xb4/0x2d8 [25375.911722] submit_bio+0x48/0x218 [25375.911960] vdev_disk_io_start+0x670/0x9f8 [zfs] [25375.912181] zio_vdev_io_start+0xdc/0x2b8 [zfs] [25375.912400] zio_nowait+0xd4/0x170 [zfs] [25375.912617] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [25375.912839] zio_vdev_io_start+0x248/0x2b8 [zfs] [25375.913057] zio_execute+0xac/0x110 [zfs] [25375.913096] taskq_thread+0x2f8/0x570 [spl] [25375.913108] kthread+0xfc/0x128 [25375.913119] ret_from_fork+0x10/0x1c [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds. [25375.919916] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.934835] txg_syncD0 2333 2 0x0028 [25375.934850] Call trace: [25375.934869] __switch_to+0x104/0x170 [25375.934879] __schedule+0x30c/0x7c0 [25375.934887] schedule+0x3c/0xb8 [25375.934899] schedule_timeout+0x9c/0x190 [25375.934908] io_schedule_timeout+0x28/0x48 [25375.934946] __cv_timedwait_common+0x1a8/0x1f8 [spl] [25375.934982] __cv_timedwait_io+0x3c/0x50 [spl] [25375.935205] zio_wait+0x130/0x2a0 [zfs] [25375.935423] dsl_pool_sync+0x3fc/0x498 [zfs] [25375.935650] spa_sync+0x538/0xe68 [zfs] [25375.935867] txg_sync_thread+0x2c0/0x468 [zfs] [25375.935911] thread_generic_wrapper+0x74/0xa0 [spl] [25375.935924] kthread+0xfc/0x128 [25375.935935] ret_from_fork+0x10/0x1c [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds. [25375.942780] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.957702] zbackup D0 75339 5499 0x [25375.957716] Call trace: [25375.957732] __switch_to+0x104/0x170 [25375.957742] __schedule+0x30c/0x7c0 [25375.957750] schedule+0x3c/0xb8 [25375.957789] cv_wait_common+0x188/0x1b0 [spl] [25375.957823] __cv_wait+0x30/0x40 [spl] [25375.958045] zil_commit_impl+0x234/0xd30 [zfs] [25375.958263] zil_commit+0x48/0x70 [zfs] [25375.958481] zfs_create+0x544/0x7d0 [zfs] [25375.958698] zpl_create+0xb8/0x178 [zfs] [25375.958711] lookup_open+0x4ec/0x6a8 [25375.958721] do_last+0x260/0x8c0 [25375.958730] path_openat+0x84/0x258 [25375.958739] do_filp_open+0x84/0x108 [25375.958752] do_sys_open+0x180/0x2b0 [25375.958763] __arm64_sys_openat+0x2c/0x38 [25375.958773] el0_svc_common.constprop.0+0x80/0x218 [25375.958781] el0_svc_handler+0x34/0xa0 [25375.958791] el0_svc+0x10/0x2cc [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds. [25375.965564] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.980479] zbackup D0 95187 5499 0x [25375.980493] Call trace: [25375.980514] __switch_to+0x104/0x170 [25375.980525] __schedule+0x30c/0x7c0 [25375.980536] schedule+0x3c/0xb8 [25375.980578] cv_wait_common+0x188/0x1b0 [spl] [25375.980612] __cv_wait+0x30/0x40 [spl] [25375.980834] zil_commit_impl+0x234/0xd30 [zfs] [25375.981052] zil_commit+0x48/0x70 [zfs] [25375.981280] zfs_write+0xa3c/0xb90 [zfs] [25375.981498] zpl_write_common_iovec+0xac/0x120 [zfs] [25375.981726] zpl_iter_write+0xe4/0x150 [zfs] [25375.981766] new_sync_write+0x100/0x1a8 [25375.981776] __vfs_write+0x74/0x90 [25375.981784] vfs_write+0xe4/0x1c8
[Kernel-packages] [Bug 1899805] Re: UC20 kernel missing /firmware/regulatory.db
https://lists.ubuntu.com/archives/kernel-team/2020-October/114068.html ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: bot-stop-nagging ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899805 Title: UC20 kernel missing /firmware/regulatory.db Status in linux package in Ubuntu: Triaged Bug description: UC20 kernel missing /firmware/regulatory.db and /firmware/regulatory.db.p7s Whilst present in the UC18 kernel snap. At runtime, this causes failure to load regulatory database, and perform wifi scan. [ 27.510199] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: fr-374 -- 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: Triaged Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in netplan.io 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 netplan.io source package in Bionic: New Status in linux-firmware source package in Eoan: Won't Fix Status in linux-firmware-raspi2 source package in Eoan: Won't Fix Status in linux-raspi2-5.3 source package in Eoan: Won't Fix Status in netplan.io source package in Eoan: Won't Fix Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: Triaged Status in linux-raspi source package in Focal: New Status in netplan.io 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 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Tags added: fr-249 -- You 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 Status in grub2 source package in Groovy: Confirmed Status in linux source package in Groovy: 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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Tags added: fr-27 -- 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: Confirmed Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Confirmed 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=bluez=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 1883229] Re: Ubuntu server installation on S3260M4 server fails
** Tags added: fr-217 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server fails Status in subiquity: Incomplete Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSC-C3K-M4SRB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1db32ed4-cafc-4d2c-b57c-d0b6a3943066 ro ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/06/2020 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: C3X60M4.4.1.1.13.0306200116 dmi.board.name: UCSC-C3K-M4SRB dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-17622-03 dmi.chassis.type: 23 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-5829-03 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrC3X60M4.4.1.1.13.0306200116:bd03/06/2020:svnCiscoSystemsInc:pnUCSC-C3K-M4SRB:pvrA0:rvnCiscoSystemsInc:rnUCSC-C3K-M4SRB:rvr73-17622-03:cvnCiscoSystemsInc:ct23:cvr68-5829-03: dmi.product.name: UCSC-C3K-M4SRB dmi.product.version: A0 dmi.sys.vendor: Cisco Systems Inc --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1898817] Re: Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled server image
wait, raspi images must already be using v5.4 kernel on bionic See https://launchpad.net/ubuntu/+source/linux-raspi-5.4 Why are you upgrading firmware, without upgrading the kernel to v5.4? Why are you using obsolete images, from the archived location, instead of the most recent ones? v4.15 kernel; raspi flavour; on bionic is not supported anymore. It has rolled over to the v5.4 kernel to ensure adequate support for all the pi board variants. ** Package changed: linux-raspi2 (Ubuntu) => linux-raspi-5.4 (Ubuntu) ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: New => Incomplete -- 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/1898817 Title: Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled server image Status in linux-firmware-raspi2 package in Ubuntu: Incomplete Status in linux-raspi-5.4 package in Ubuntu: Incomplete Bug description: [Impact] Wifi device disappear after upgrading linux-firmware-raspi2. Can reproduce on rpi3b, rpi3b+, and rpi3a+. This only happens on 18.04.3 preinstalled server image, with 4.15 kernel. [Test Case] 1. dd the image in an SD card: http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot rpi device with the sd card 3. Upgrade the linux-firmware-raspi2 package using following command: sudo apt update sudo apt install linux-firmware-raspi2 4. Reboot: sudo reboot 5. Check with command: ip a Expected Result wlan0 is still there and workable. Actual Result wlan0 device disappeared. [Additional Info] Command output: ubuntu@ubuntu:~$ sudo apt update Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [1,096 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main Translation-en [360 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [2,084 B] Get:8 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted Translation-en [23.0 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [1,471 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe Translation-en [351 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 Packages [5,068 B] Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse Translation-en [6,920 B] Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main arm64 Packages [9,992 B] Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main Translation-en [4,764 B] Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe arm64 Packages [9,932 B] Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe Translation-en [4,588 B] Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages [803 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/main Translation-en [269 kB] Get:19 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted arm64 Packages [1,172 B] Get:20 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted Translation-en [20.4 kB] Get:21 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages [933 kB] Get:22 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe Translation-en [239 kB] Get:23 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse arm64 Packages [2,360 B] Get:24 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse Translation-en [2,908 B] Fetched 5,867 kB in 6s (962 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 178 packages can be upgraded. Run 'apt list --upgradable' to see them. ubuntu@ubuntu:~$ sudo apt install linux-firmware-raspi2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-firmware-raspi2 1 upgraded, 0 newly installed, 0 to remove and 177 not upgraded. Need to get 5,200 kB of archives. After this operation, 11.4 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 linux-firmware-raspi2 arm64 1.20200601+arm64-0ubuntu2~18.04.1 [5,200 kB] Fetched 5,200 kB in 3s (1,944 kB/s) (Reading database ... 62519 files and directories currently installed.) Preparing to unpack
[Kernel-packages] [Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key
** Tags added: fr-797 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898716 Title: Please trust Canonical Livepatch Service kmod signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: New Status in linux source package in Focal: New Bug description: [Impact] * Currently Canonical Livepatch service is signing kernel modules that are not trusted by the default Ubuntu kernels * to make Canonical Livepatch service out of the box compatible with SecureBoot, please add Canonical Livepatch service key as trusted in the kernel by default * if user wants to distrust the key, they can remove it via mokx, dbx, and we can revoke it by signing revocation with 'canonical master ca'. [Test Case] * Boot kernel * Check the built-in keyring to ensure that Livepatch key is trusted by the built-in keyring Bad: $ sudo keyctl list %:.builtin_trusted_keys 1 key in keyring: 204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 4182e0d0113d4a8f460783380c9e618ef1597bf5 Good: $ sudo keyctl list %:.builtin_trusted_keys 2 keys in keyring: 637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc 1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969 [Regression Potential] * Kernel keyring size will increase by one key. And thus kernel image will too. [Other Info] * Current livepatch key fingerprints mokutil uses der format $ openssl x509 -inform der -in /snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA kernel use pem format $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA [Target kernels] bionic and up, across the board, but maybe excluding fips kernels?! [Patch] https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
Responding to comment #15: The 5.8.13 upstream stable update was included in the ubuntu linux kernel version 5.8.0-21.22 in groovy. The 5.4 kernel update including 5.4.69 has not been released yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
And, after 18 hours+, I was able to archive a ZFS snapshot, using BorgBackup, with the WBT settings, suggested, earlier: tyson@ubuntu:~$ sudo zfs send Yaesu@Crucial-2TB-1951E22FA633 | borg create --stats BorgStore::Yaesu@Crucial-2TB-1951E22FA633 - ^[[A^[[A-- Archive name: Yaesu@Crucial-2TB-1951E22FA633 Archive fingerprint: 32d64e2a13eb543e4846cc34ac2c3609fe192127e3bf6d324a0fa9d61b988c19 Time (start): Tue, 2020-10-13 15:49:51 Time (end): Wed, 2020-10-14 10:01:46 Duration: 18 hours 11 minutes 54.87 seconds Number of files: 1 Utilization of max. archive size: 0% -- Original size Compressed sizeDeduplicated size This archive:1.89 TB 1.75 TB617.36 GB All archives:7.44 TB 5.87 TB 1.99 TB Unique chunks Total chunks Chunk index: 842436 2607257 -- The "dmesg" log is clean, too: tyson@ubuntu:~$ dmesg [0.00] Booting Linux on physical CPU 0x00 [0x410fd083] [0.00] Linux version 5.4.0-1018-raspi (buildd@bos02-arm64-052) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #20-Ubuntu SMP Sun Sep 6 05:11:16 UTC 2020 (Ubuntu 5.4.0-1018.20-raspi 5.4.55) [0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4 [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: UEFI not found. [0.00] Reserved memory: created CMA memory pool at 0x2c00, size 64 MiB [0.00] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [0.00] On node 0 totalpages: 2061312 [0.00] DMA zone: 3792 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 242688 pages, LIFO batch:63 [0.00] DMA32 zone: 12288 pages used for memmap [0.00] DMA32 zone: 770048 pages, LIFO batch:63 [0.00] Normal zone: 16384 pages used for memmap [0.00] Normal zone: 1048576 pages, LIFO batch:63 [0.00] percpu: Embedded 32 pages/cpu s92120 r8192 d30760 u131072 [0.00] pcpu-alloc: s92120 r8192 d30760 u131072 alloc=32*4096 [0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0.00] Detected PIPT I-cache on CPU0 [0.00] CPU features: detected: EL2 vector hardening [0.00] CPU features: kernel page table isolation forced ON by KASLR [0.00] CPU features: detected: Kernel page table isolation (KPTI) [0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware [0.00] Built 1 zonelists, mobility grouping on. Total pages: 2028848 [0.00] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:B8:1A:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash [0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off [0.00] software IO TLB: mapped [mem 0x3740-0x3b40] (64MB) [0.00] Memory: 7898140K/8245248K available (11772K kernel code, 1236K rwdata, 4244K rodata, 6144K init, 1076K bss, 281572K reserved, 65536K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x38/0x3e0 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 39001 entries in 153 pages [0.00] rcu: Hierarchical RCU implementation. [0.00] Tasks RCU enabled. [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [0.00] GIC: Using split EOI/Deactivate mode [0.00] arch_timer: cp15 timer(s) running at 54.00MHz (phys). [0.00] clocksource: arch_sys_counter: mask: 0xff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns [0.05] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns [0.000200] Console: colour dummy device 80x25 [0.000221] printk: console [tty1] enabled [0.000273] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=216000) [0.000288] pid_max: default: 32768 minimum: 301 [0.000495] LSM: Security Framework initializing [0.000543] Yama: becoming mindful. [0.000631] AppArmor: AppArmor
[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
@fginther: glad to hear that - thanks a lot! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * A problem occurs with 32-bit ino_t values on 64-bit architectures (like s390x). * Without this patch, cephfs kernel client does not work properly on s390x: the initial symtom is missing the first created file/directory on cephfs mount point as reported in https://tracker.ceph.com/issues/46828. [Fix] * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit ino_t" * backport for focal: https://launchpadlibrarian.net/501822049/0001 -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch [Test Case] * IBM Development team and Test team have carried out simple testing and stress testing by automatically creating many Ceph clusters on s390x (with different configuration each time), doing the cephfs kernel mounting, checking inode numbers, running stress tests. The same procedures were done on x86_64 arch by Test team. [Regression Potential] * There is a certain regression risk with this patch, since: * common ceph filesystem code in fs/ceph/ is modified * the inode handling is touched * ceph is used for supplemental volumes * and as the original author of this patch (Jeff Layton) wrote in the commit message, the potential issue might happen on 32-bit arches only and he also provided workaround for those arches. [Other] * The above patch/commit was upstream accepted with kernel 5.9. * Cherry picking the patch/commit to groovy works fine, hence this SRU. * For focal a cherry pick does not apply cleanly, hence a backport got added to LP 1899582. __ Backport provided for git-commit to 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebce3eb2f7ef9f6ef01a60874ebd232450107c9a Backport patch attached for commit ebce3eb upstream. It was applied and tested on top of Ubuntu commit : linux (5.4.0-48.52) focal; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899802] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1899802 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander Status in linux package in Ubuntu: Incomplete Bug description: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi=160226366707807=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899805] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1899805 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899805 Title: UC20 kernel missing /firmware/regulatory.db Status in linux package in Ubuntu: Incomplete Bug description: UC20 kernel missing /firmware/regulatory.db and /firmware/regulatory.db.p7s Whilst present in the UC18 kernel snap. At runtime, this causes failure to load regulatory database, and perform wifi scan. [ 27.510199] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899805] [NEW] UC20 kernel missing /firmware/regulatory.db
Public bug reported: UC20 kernel missing /firmware/regulatory.db and /firmware/regulatory.db.p7s Whilst present in the UC18 kernel snap. At runtime, this causes failure to load regulatory database, and perform wifi scan. [ 27.510199] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: core20 regression-release uc20 ** Tags added: core20 regression-release uc20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899805 Title: UC20 kernel missing /firmware/regulatory.db Status in linux package in Ubuntu: Incomplete Bug description: UC20 kernel missing /firmware/regulatory.db and /firmware/regulatory.db.p7s Whilst present in the UC18 kernel snap. At runtime, this causes failure to load regulatory database, and perform wifi scan. [ 27.510199] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
@xnox, @fheimes, we are preparing a groovy respin which will pick this up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * A problem occurs with 32-bit ino_t values on 64-bit architectures (like s390x). * Without this patch, cephfs kernel client does not work properly on s390x: the initial symtom is missing the first created file/directory on cephfs mount point as reported in https://tracker.ceph.com/issues/46828. [Fix] * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit ino_t" * backport for focal: https://launchpadlibrarian.net/501822049/0001 -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch [Test Case] * IBM Development team and Test team have carried out simple testing and stress testing by automatically creating many Ceph clusters on s390x (with different configuration each time), doing the cephfs kernel mounting, checking inode numbers, running stress tests. The same procedures were done on x86_64 arch by Test team. [Regression Potential] * There is a certain regression risk with this patch, since: * common ceph filesystem code in fs/ceph/ is modified * the inode handling is touched * ceph is used for supplemental volumes * and as the original author of this patch (Jeff Layton) wrote in the commit message, the potential issue might happen on 32-bit arches only and he also provided workaround for those arches. [Other] * The above patch/commit was upstream accepted with kernel 5.9. * Cherry picking the patch/commit to groovy works fine, hence this SRU. * For focal a cherry pick does not apply cleanly, hence a backport got added to LP 1899582. __ Backport provided for git-commit to 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebce3eb2f7ef9f6ef01a60874ebd232450107c9a Backport patch attached for commit ebce3eb upstream. It was applied and tested on top of Ubuntu commit : linux (5.4.0-48.52) focal; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] Re: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded
@xnox, we are preparing a groovy respin which will pick this up. ** Changed in: linux (Ubuntu Groovy) Milestone: groovy-updates => ubuntu-20.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded Status in Release Notes for Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: [Impact] Groovy armhf LPAE kernel fails to load kmods (and thus fail to boot). [Fix] Enable CONFIG_ARM_MODULE_PLTS for armhf [Regression potential] Quoting the arch/arm/Kconfig: "This [option] allows modules to be allocated in the generic vmalloc area after the dedicated module memory area has been exhausted. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Disabling this is usually safe for small single-platform configurations. " --- qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] Re: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded
** Also affects: linux (Ubuntu Groovy) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Groovy) Milestone: ubuntu-20.10 => groovy-updates ** Changed in: ubuntu-release-notes Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded Status in Release Notes for Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: [Impact] Groovy armhf LPAE kernel fails to load kmods (and thus fail to boot). [Fix] Enable CONFIG_ARM_MODULE_PLTS for armhf [Regression potential] Quoting the arch/arm/Kconfig: "This [option] allows modules to be allocated in the generic vmalloc area after the dedicated module memory area has been exhausted. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Disabling this is usually safe for small single-platform configurations. " --- qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899802] [NEW] [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
Public bug reported: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi=160226366707807=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander Status in linux package in Ubuntu: New Bug description: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi=160226366707807=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746638] Re: [nouveau] [GeForce 6150SE nForce 430] PC freezes and crashes
I don't use any flavor of Ubuntu anymore and do not have this hardware to test. Feel free to take over of this issue if is relevant to you. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746638 Title: [nouveau] [GeForce 6150SE nForce 430] PC freezes and crashes Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: When using the nouveau graphics driver my pc freezes and crashes. WORKAROUND: Use the proprietary nvidia driver. WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Thu Feb 1 01:36:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] [1043:8234] InstallationDate: Installed on 2017-11-23 (69 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050] Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 1 01:34:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 1241:1166MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899522] Re: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.
The underlying problem is that the file '/usr/share/nvidia/nvidia- application-profiles-450.80.02-key-documentation' is present in both packages, so they run into a conflict when attempting to install both. ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1899522 Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Confirmed Bug description: During sudo apt-get upgrade, there was an error while this package was installing. On restarting my computer, the resolution was set to 800*600 and my gpu (nvidia 1060 6gb) wasn't recognized. Uninstalling the driver and reverting to the nouveu drivers fixed the resolution issue and reinstalling the nvidia-450 drivers via software & updates allowed for everything to go back to normal. Steps to reproduce: On a machine with an nvidia 1060 6gb, run sudo apt-get update followed by sudo apt-get upgrade, this should result in an error during dpkg. Restart the computer to see the driver issue with display resolution and gpu not labelled correctly. Steps to resolve for the time being: Uninstall and reinstall nvidia-450 via software & updates, restart computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 18:12:58 2020 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2 Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over (450.51.06-0ubuntu0.20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-OfgM3I/33-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 InstallationDate: Installed on 2020-10-01 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450-server Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1899522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874588] Re: [amdgpu] Flickering screen after waking up from Suspend
I have a radeon 5700XT with 2 screens running at 144Hz and have this problem when I wake up my fresh install unbutu out of sleep. Workaround: For the moment I set the frequency ON BOTH monitor at 60Hz, and I cancel the setting to get back at 144Hz, and it works. If I put only one on my double screen at 60Hz, flickering continue ON BOTH. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874588 Title: [amdgpu] Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Incomplete Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1874588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] Re: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded
@xnox: yes, we usually respin before release with only hot-fixes on top. The other patch you mentioned was just applied in Groovy and pushed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Groovy armhf LPAE kernel fails to load kmods (and thus fail to boot). [Fix] Enable CONFIG_ARM_MODULE_PLTS for armhf [Regression potential] Quoting the arch/arm/Kconfig: "This [option] allows modules to be allocated in the generic vmalloc area after the dedicated module memory area has been exhausted. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Disabling this is usually safe for small single-platform configurations. " --- qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
OK removed those from /etc/default/grub, ran update-grub, rebooted [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash vt.handoff=7 same problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899784] Re: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/al
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899784 Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: no details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-51-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex978 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 15:26:10 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-51-generic:(not installed) Unpacking linux-modules-extra-5.4.0-51-generic (5.4.0-51.56) ... dpkg: error processing archive /tmp/apt-dpkg-install-V8BhvG/2-linux-modules-extra-5.4.0-51-generic_5.4.0-51.56_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-02 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F5S09J02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e353e192-f8f6-4408-bd84-7fe991c224ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: linux Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S09J02 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F5S09J02:pvrThinkPadX260:rvnLENOVO:rn20F5S09J02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S09J02 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899784] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899784 Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: no details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-51-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex978 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 15:26:10 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-51-generic:(not installed) Unpacking linux-modules-extra-5.4.0-51-generic (5.4.0-51.56) ... dpkg: error processing archive /tmp/apt-dpkg-install-V8BhvG/2-linux-modules-extra-5.4.0-51-generic_5.4.0-51.56_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-02 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F5S09J02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e353e192-f8f6-4408-bd84-7fe991c224ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: linux Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S09J02 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F5S09J02:pvrThinkPadX260:rvnLENOVO:rn20F5S09J02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S09J02 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899784] [NEW] package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/
Public bug reported: no details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-51-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex978 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 15:26:10 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-51-generic:(not installed) Unpacking linux-modules-extra-5.4.0-51-generic (5.4.0-51.56) ... dpkg: error processing archive /tmp/apt-dpkg-install-V8BhvG/2-linux-modules-extra-5.4.0-51-generic_5.4.0-51.56_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-02 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F5S09J02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e353e192-f8f6-4408-bd84-7fe991c224ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: linux Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S09J02 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F5S09J02:pvrThinkPadX260:rvnLENOVO:rn20F5S09J02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S09J02 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package 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/1899784 Title: package linux-modules-extra-5.4.0-51-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: no details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-51-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex978 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 15:26:10 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-51-generic:(not installed) Unpacking linux-modules-extra-5.4.0-51-generic (5.4.0-51.56) ... dpkg: error processing archive /tmp/apt-dpkg-install-V8BhvG/2-linux-modules-extra-5.4.0-51-generic_5.4.0-51.56_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-51-generic/kernel/drivers/net/ethernet/alteon/acenic.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-02 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F5S09J02 ProcFB: 0
[Kernel-packages] [Bug 1899687] Re: linux-modules-nvidia-450-server-generic uninstallable
This should be resolved now that the linux-restricted-modules which generate `linux-modules-nvidia-450-server-generic` have been released. It was a consequence of the nvidia driver packages being released to the archive prematurely and the time it takes for a kernel update to advance through the publication process. Both are process problems and can lead to this package install failure. The nvidia driver packages should have had a "release hold" applied to prevent the premature release. Unfortunately, this is a manual process and was missed. One thing we will do as part of a retrospective for this release is determine if the release infrastructure or other tooling can be used to enforce this in the future. I'm setting this to 'invalid' as the install issue with linux- restricted-modules has resolved itself. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Invalid -- 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/1899687 Title: linux-modules-nvidia-450-server-generic uninstallable Status in linux-restricted-modules package in Ubuntu: Triaged Bug description: linux-modules-nvidia-450-server-generic appears to be uninstallable on bionic currently. I hit this on actual hardware, but here's a reproduction in lxd for a clean-room demonstration: ubuntu@blanka:~$ lxc launch ubuntu:bionic 450srv Creating 450srv Error: Failed instance creation: Invalid instance name: Name must not be a number ubuntu@blanka:~$ lxc launch ubuntu:bionic nv450srv Creating nv450srv Starting nv450srv ubuntu@blanka:~$ lxc exec nv450srv -- apt update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [1355 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [269 kB] Get:6 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [151 kB] Get:7 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [20.4 kB] Get:8 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1069 kB] Get:9 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [239 kB] Get:10 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [12.3 kB] Get:11 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [2908 B] Get:12 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8570 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic/universe Translation-en [4941 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/multiverse Translation-en [108 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [1681 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [360 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [169 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1672 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [352 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [31.4 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [6920 B] Get:24 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [10.0 kB] Get:25 http://archive.ubuntu.com/ubuntu bionic-backports/main Translation-en [4764 B] Get:26 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [10.3 kB] Get:27 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [4588 B] Fetched 21.4 MB in 3s (6391 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 7 packages can be upgraded. Run 'apt list --upgradable' to see them. ubuntu@blanka:~$ lxc exec nv450srv -- apt install linux-modules-nvidia-450-server-generic Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-450-server-generic : Depends: nvidia-kernel-common-450-server (<= 450.51.06-1) but 450.80.02-0ubuntu0.18.04.3 is to be installed
[Kernel-packages] [Bug 1899687] Re: linux-modules-nvidia-450-server-generic uninstallable
Actually, I'm going to set this to 'triaged'. We can then use this as the motivation for getting the `release hold` issue fixed. ** Changed in: linux-restricted-modules (Ubuntu) Status: Invalid => Triaged -- 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/1899687 Title: linux-modules-nvidia-450-server-generic uninstallable Status in linux-restricted-modules package in Ubuntu: Triaged Bug description: linux-modules-nvidia-450-server-generic appears to be uninstallable on bionic currently. I hit this on actual hardware, but here's a reproduction in lxd for a clean-room demonstration: ubuntu@blanka:~$ lxc launch ubuntu:bionic 450srv Creating 450srv Error: Failed instance creation: Invalid instance name: Name must not be a number ubuntu@blanka:~$ lxc launch ubuntu:bionic nv450srv Creating nv450srv Starting nv450srv ubuntu@blanka:~$ lxc exec nv450srv -- apt update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [1355 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [269 kB] Get:6 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [151 kB] Get:7 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [20.4 kB] Get:8 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1069 kB] Get:9 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [239 kB] Get:10 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [12.3 kB] Get:11 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [2908 B] Get:12 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8570 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic/universe Translation-en [4941 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/multiverse Translation-en [108 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [1681 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [360 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [169 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1672 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [352 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [31.4 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [6920 B] Get:24 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [10.0 kB] Get:25 http://archive.ubuntu.com/ubuntu bionic-backports/main Translation-en [4764 B] Get:26 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [10.3 kB] Get:27 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [4588 B] Fetched 21.4 MB in 3s (6391 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 7 packages can be upgraded. Run 'apt list --upgradable' to see them. ubuntu@blanka:~$ lxc exec nv450srv -- apt install linux-modules-nvidia-450-server-generic Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-450-server-generic : Depends: nvidia-kernel-common-450-server (<= 450.51.06-1) but 450.80.02-0ubuntu0.18.04.3 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1899687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
Kernel SRU request submitted for groovy: https://lists.ubuntu.com/archives/kernel-team/2020-October/thread.html#114060 changing status to 'In Progress' for groovy. ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: Frank Heimes (fheimes) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * A problem occurs with 32-bit ino_t values on 64-bit architectures (like s390x). * Without this patch, cephfs kernel client does not work properly on s390x: the initial symtom is missing the first created file/directory on cephfs mount point as reported in https://tracker.ceph.com/issues/46828. [Fix] * cherry-pick for groovy: ebce3eb2f7ef9f6ef01a60874ebd232450107c9a ebce3eb2f7ef "ceph: fix inode number handling on arches with 32-bit ino_t" * backport for focal: https://launchpadlibrarian.net/501822049/0001 -ceph-fix-inode-number-handling-on-arches-with-32-bit.patch [Test Case] * IBM Development team and Test team have carried out simple testing and stress testing by automatically creating many Ceph clusters on s390x (with different configuration each time), doing the cephfs kernel mounting, checking inode numbers, running stress tests. The same procedures were done on x86_64 arch by Test team. [Regression Potential] * There is a certain regression risk with this patch, since: * common ceph filesystem code in fs/ceph/ is modified * the inode handling is touched * ceph is used for supplemental volumes * and as the original author of this patch (Jeff Layton) wrote in the commit message, the potential issue might happen on 32-bit arches only and he also provided workaround for those arches. [Other] * The above patch/commit was upstream accepted with kernel 5.9. * Cherry picking the patch/commit to groovy works fine, hence this SRU. * For focal a cherry pick does not apply cleanly, hence a backport got added to LP 1899582. __ Backport provided for git-commit to 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebce3eb2f7ef9f6ef01a60874ebd232450107c9a Backport patch attached for commit ebce3eb upstream. It was applied and tested on top of Ubuntu commit : linux (5.4.0-48.52) focal; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Please remove "i8042.nopnp=1 pci=nocrs" and see if it helps, 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/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899776] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Thanks, see #1899776 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899776] [NEW] Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Public bug reported: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: New Bug description: Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic #23-Ubuntu) but was advised to report a new bug. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2131 F pulseaudio /dev/snd/controlC1: tim2131 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 14 13:15:38 2020 InstallationDate: Installed on 2020-06-03 (132 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago) dmi.bios.date: 06/19/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2020-10-14 07:51 EDT--- Sorry for not responfing earlier. After installing a new system I can see that the update happening: $ cat /proc/cmdline root=/dev/mapper/vgubuntu-root crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M However it still turns out that - if using an encrypted volume - it's not possible to unlock the volume from the kdump kernel for a ~2GB VM as the 320MB are still not sufficient. Bumping the VM memory to 4GB will allow the kdump kernel to unlock the volume. I think that either 512M should be the lowest value used for the crashkernel, or at least a warning should be emitted, alerting the system administrator that for a < 4GB machine kdump is not going to work with an encrypted root/dump volume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
It's probably a different bug. Please file a new one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
