[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
If you tell me how to "gather the full kernel log from when the system booted to black screen", I might try that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I followed this advice (mentioned above):
https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button
It seems that "quiet splash" is the actual problem, not "nomodeset"
(solution).
I edited the GRUB entry as follows (with results added):
1) With only "quiet splash" (no "nomodeset"), default installation,
fresh install of Kubuntu 24.04: only black screen, nothing happens.
2) Add "nomodeset" to "quiet splash": everything works perfectly. Also
works permanently with editing of /etc/default/grub.
3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete
"nomodeset", if previously added): everything works perfectly (see
Reddit link above).
4) Delete "nomodeset", after having added it to /etc/default/grub and
updated grub previously, but leave the 'original' "quiet splash":
computer hangs, completely unresponsive, after showing the following
code:
Booting a command list
Loading Linux 6.8.0-31-generic ...
Loading initial ramdisk ...
5) Again, boot without both "quiet splash" or "nomodeset": everything works
perfectly. Also works permanently with /etc/default/grub.
It went quite fast, but after "Loading initial ramdisk ..." I think the next
code line was "enabling secure boot". It might be a problem with "secure boot"
and "quiet splash". Secure boot is enabled in both my installations, so I can't
try the other option ("secure boot" disabled in the EFI BIOS before
installation).
Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the
words "quiet splash" (leave the quotation marks '').
- Run sudo update-grub
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
---
For those affected by this issue, this was my fix:
Install 24.04, reboot, at the desktop, open a terminal window and add
the following PPAs:
sudo add-apt-repository ppa:cappelikan/ppa
sudo apt update
sudo apt install mainline
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Run mainline-gtk, install kernel version 6.7.10
run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic"
to top of list, making it the default option. Save and reboot.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I think this bug also affects Intel GPUs. I did an installation today that resulted in a black screen without "nomodeset". See: https://bugs.launchpad.net/ubuntu/+bug/2063877 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
... oh yes, I had the same problem with AMD Radeon Integrated Graphics; see the same bug report: https://bugs.launchpad.net/ubuntu/+bug/2063877 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04
Strangely changing the installed system to use the 'nouveau' Nvidia driver does NOT fix the problem. If it help I can try a fresh 24.04 install without initially installing the propitiatory Nvidia driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: Invalid Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04
Bug occurs with released 24.04 where the kernel is 6.8.0-31-generic Strangely the live version of 24.04 booted on same machine form the released desktop ISO image does NOT have the problem with the same kernel version. The Precision 5520 had hybrid graphics with both integrated Intel (HD P630) and discrete Nvidia (GM197GLM) processors. The live system is using the 'nouveau' driver for the Nvidia graphics. I suspect the problem is being indirectly caused by the Nvidia drivers HDMI HD Audio support combined with the Intel AVS audio driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: Invalid Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04
alsa-info from a Dell Precision 5520 ** Attachment added: "alsa-info.txt.1IMNEYShPL" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+attachment/5770168/+files/alsa-info.txt.1IMNEYShPL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04
Problem lies in the Intel kernel driver 'snd_soc_avs' which is becoming active but fail to support the HDA sound hardware correctly. Workaround is to blacklist 'snd_soc_avs'. Problem is well know and seems to be already in Kernel 6.7. See for example https://bbs.archlinux.org/viewtopic.php?id=294655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025198] Re: Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution
Since my last comment, I did some changes: I did append intel_iommu=off to GRUB_CMDLINE_LINUX_DEFAULT and it seems to help. My laptop is responding faster now to command. When internet is not working (showing network, but not responding) I use this command and it fix the issue (I don't think it will fix the issue permanently): sudo systemctl restart NetworkManager The only thing that I have been unable to fix so far is the resolution of the main monitor that is still look like it is diluted and not clear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025198 Title: Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Since I installed Ubuntu 22.04 my laptop is slow I lose my internet connection intermittently. The main display resolution is not clean. The image rendering seems diluted and unclear, especially at the edges of the screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 27 20:33:17 2023 InstallationDate: Installed on 2023-06-21 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2025198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025198] [NEW] Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution
Public bug reported: Since I installed Ubuntu 22.04 my laptop is slow I lose my internet connection intermittently. The main display resolution is not clean. The image rendering seems diluted and unclear, especially at the edges of the screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 27 20:33:17 2023 InstallationDate: Installed on 2023-06-21 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025198 Title: Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Since I installed Ubuntu 22.04 my laptop is slow I lose my internet connection intermittently. The main display resolution is not clean. The image rendering seems diluted and unclear, especially at the edges of the screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 27 20:33:17 2023 InstallationDate: Installed on 2023-06-21 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2025198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Re: nfs mount in fstab on vers. 5.15.0.53 doesn't work
I would like to post an update on this issue.
I just updated my system to kernel 5.15.0.56 trough the standard repository
update and the problem seems to be resolved.
Shared NAS folders are now mounted through the entries in fstab.
>From my point of view this issue can be closed since it's working now with the
>new kernel.
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/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Re: nfs mount in fstab on vers. 5.15.0.53 doesn't work
I executed the given command (apport-collect 1997905) under Kernel v
5.15.0.52 since I can't login to 5.15.0.53.
Upload of the report failed so I attach it to this message.
Thanks for your help
** Attachment added: "report from apport-collect 1997905"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997905/+attachment/5632831/+files/apport.linux.fb73tktf.apport
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632828/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632827/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632829/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632830/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Confirmed
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632824/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632818/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632823/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632826/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632821/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632825/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632820/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632822/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632817/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632819/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632815/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632814/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] HookError_ubuntu.txt
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632816/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
_MarkForUpload: True
dmi.bios.date: 10/14/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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/1997905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997905] Re: nfs mount in fstab on vers. 5.15.0.53 doesn't work
apport information
** Tags added: apport-collected vanessa
** Description changed:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
- PS. I report this under Kernel v 5.15.0.52 since I can't login into v
- 5.15.0.53
+ PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: fred 1669 F pulseaudio
+ /dev/snd/controlC1: fred 1669 F pulseaudio
+ /dev/snd/controlC0: fred 1669 F pulseaudio
+ CasperMD5json: {
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 21
+ InstallationDate: Installed on 2022-11-02 (23 days ago)
+ InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
+ IwConfig:
+ lono wireless extensions.
+
+ enp6s0no wireless extensions.
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB:
+ 0 amdgpudrmfb
+ 1 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
+ RelatedPackageVersions:
+ linux-restricted-modules-5.15.0-52-generic N/A
+ linux-backports-modules-5.15.0-52-generic N/A
+ linux-firmware 20220329.git681281e4-0ubuntu3.6
+ RfKill:
+ 0: hci0: Bluetooth
+ Soft blocked: no
+ Hard blocked: no
+ Tags: vanessa
+ Uname: Linux 5.15.0-52-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom crontab dip lpadmin nordvpn plugdev sambashare sudo
users
+ _MarkForUpload: True
+ dmi.bios.date: 10/14/2020
+ dmi.bios.release: 5.13
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 5603
+ dmi.board.asset.tag: Default string
+ dmi.board.name: PRIME A320M-K
+ 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.:bvr5603:bd10/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
+ 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
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1997905/+attachment/5632813/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997905
Title:
nfs mount in fstab on vers. 5.15.0.53 doesn't work
Status in linux package in Ubuntu:
Incomplete
Bug description:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-11-02 (23 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp6s0no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB:
0 amdgpudrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=958d1e22-cd87-48a8-a9a0-606feef74317 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: vanessa
Uname:
[Kernel-packages] [Bug 1997905] [NEW] nfs mount in fstab on vers. 5.15.0.53 doesn't work
Public bug reported: I added the same mounting commands in fstab as I used for Kernel v5.15.0.52. However the mounting will not complete. I can't get to the login window (it hangs on the Linux-Mint-Logo.. nfs-common is installed on the system. I used the syntax: :/ nfs _netdev defaults 0 0 Thanks PS. I report this under Kernel v 5.15.0.52 since I can't login into v 5.15.0.53 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "just lspci-vnvn.log (can upload only 1 file)" https://bugs.launchpad.net/bugs/1997905/+attachment/5632724/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997905 Title: nfs mount in fstab on vers. 5.15.0.53 doesn't work Status in linux package in Ubuntu: New Bug description: I added the same mounting commands in fstab as I used for Kernel v5.15.0.52. However the mounting will not complete. I can't get to the login window (it hangs on the Linux-Mint-Logo.. nfs-common is installed on the system. I used the syntax: :/ nfs _netdev defaults 0 0 Thanks PS. I report this under Kernel v 5.15.0.52 since I can't login into v 5.15.0.53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Thank you Christian,
I think I managed to repair my system.
Here is how I did, if it can help others.
By the way, Jonas, it is impossible to remove broken files/folders, so the
strategy I suggest is to destroy the dataset and restore it from a backup,
while running from a bootable media.
One can backup everything in the dataset except the corrupted files, and
finally try to restore these by other means: reinstalling package, or using
eventual backups for personnal files.
I scanned every dataset with find and fstat, as suggested in this thread, until
fstat got stalled, for example with /var (I did it for /, /var, /opt and /home,
which all had their own datasets):
```
sudo find /var -mount -exec echo '{}' \; -exec stat {} \;
```
At the same time I monitored kernel errors:
```
tail -f /var/log/kern.log
```
When it freezes on a file, its name is printed by the echo command (this is the
last thing printed out), and a stack trace appears in the log.
I was lucky, only one file got corrupted: `/var/lib/app-
info/icons/ubuntu-impish-universe/48x48/plasma-workspace_preferences-
desktop-color.png`.
Each time a corrupted file is found, it is necessary to restart the scan from
the beginning, while excluding it, example:
```
sudo find /var -mount -not -path
'/var/lib/app-info/icons/ubuntu-impish-universe/*' -exec echo '{}' \; -exec
stat {} \;
```
Apparently, my corrupted file did not belong to any package (I checked with
`apt-file search `), and in the end, I figured out it was recreated
automatically, I don´t know how...
Otherwise, I would have reinstalled the package after restoring the rest.
I backed up the whole /var with tar:
```
sudo tar --exclude=/var/lib/app-info/icons/ubuntu-impish-universe/48x48 --acls
--xattrs --numeric-owner --one-file-system -zcpvf backup_var.tar.gz /var
```
At first I did not put --numeric-owner, but the owners where all messed up, and
it prevented it from going to graphical mode (GDM was complaining not the have
write access to some /var/lib/gdm3/.config/)
It is probably because by default, owner/group are saved as text, and are
assigned different uid/gid on the bootable media.
The backup process shall not get stalled, otherwise there might be other
corrupted files, not seen by fstat, I don't know if it is possible.
In order to be extra sure about non-corruption of my root dir (/), I
also created a backup of it, looking for a possible freeze, but it did
not occur.
I created a bootable USB media with Ubuntu 21.04, and booted it.
I accessed my ZFS pool:
```
sudo mkdir /mnt/install
sudo zpool import -f -R /mnt/install rpool
zfs list
```
I destroyed and recreated the dataset for /var (with options from my
installation notes):
```
sudo zfs destroy -r rpool/root/var
sudo zfs create -o quota=16G -o mountpoint=/var rpool/root/var
```
It is necessary to reopen the pool, otherwise, a simple mount does not allow
populating the new dataset (for me, /var was created in the root dataset):
```
sudo zpool export -a
sudo zpool import -R /mnt/install rpool
sudo zfs mount -l -a
zfs list
```
Now we can restore the backup:
```
sudo tar --acls --xattrs -zxpvf /home/user/backup_var.tar.gz -C /mnt/install
```
Check if the new dataset has the correct size and content:
```
zfs list
ll /mnt/install/var
```
Close and reboot:
```
sudo zfs umount -a
sudo reboot
```
Of course, it can get more complex if the corrupted files are more sensitive
system files.
It might be necessary to chroot in order to reinstall the packages where
corrupted files come from.
Hope it helps...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
>z_sa_hdl)) failed
Status in Native ZFS for Linux:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-raspi package in Ubuntu:
Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
Confirmed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux-raspi source package in Impish:
Confirmed
Status in ubuntu-release-upgrader source package in Impish:
Confirmed
Status in zfs-linux source package in Impish:
Fix Released
Bug description:
Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
panic in the kernel log which was also hanging Disk I/O for all
Chrome/Electron Apps.
I have narrowed down a few important notes:
- It does not happen with module version 0.8.4-1ubuntu11 built and included
with 5.8.0-29-generic
- It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
on the same kernel and also on 5.8.18-acso (a custom kernel).
- For whatever reason multiple Chrome/Electron apps were affected,
specifically Discord, Chrome and Mattermost. In all cases they seem
(but I
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
As many people here, I upgraded my encrypted ZFS Ubuntu system to 21.10, unaware of the issues with ZFS, I only used 5.13.0-19 for a day, and began to notice odd things, like: incapacity to suspend to RAM, freezes, some process were impossible to kill. I updated my kernel to 5.13.0-20 and then 5.13.0-21, but I still have issues with my ZFS encrypted filesystem. It seems the kernel update does not fix everything. Even now it is unable to suspend (it says some process refuse to suspend), which is really annoying for a laptop. Moreoever, automatically scheduled "updatedb" and "apt update" get stuck. Even system shutdown often takes a long time, to the point I have to force it with power button. Many times it seems to get stuck waiting for AppArmor. In addition I keep getting errors with stack traces in dmesg, I put an example in attachment. Now I am wondering what I should do to repair it ? I considered trying to downgrade my kernel to 5.11.0-37 which was my version before upgrading to 21.10, but it was automatically removed, and it does not seem very easy to put it back. I am wondering if it is worth the hassle. Besides, the ZFS version was also upgraded in the process, and it is not clear to me whether I could keep the new version with the old kernel, or not. It seems to have evolved from 0.8.4-1ubuntu11.3 to 2.0.2-1ubuntu5.1, and then 2.0.2-1ubuntu5.2, and 2.0.6-1ubuntu2 (though oddly I cannot find any trace of this last version being installed in apt logs). I am wondering if rolling back to 0.8.4 can do any good ? My whole system is based on ZFS, if I have to reinstall it all, it will take me days to put everything back. Is there a real corruption on the filesystem, which would be interpreted as such by an older ZFS version, or is it just new 2.0.x versions that are disturbed by it ? Would there be a way to fix the corruption ? Deleting some files or changing meta-data ? Any help would be greatly appreciated ! Thank you. ** Attachment added: "zfs_panic_trace_2025.log" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+attachment/5540947/+files/zfs_panic_trace_2025.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-raspi source package in Impish: New Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call
[Kernel-packages] [Bug 1925799] Re: touchpad not detected
solved thanks to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893663 Touchpad works fine after applying the change explained there: this work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893663/comments/12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491383/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491382/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491380/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491381/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491379/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491378/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491376/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491377/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491375/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491374/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491373/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491372/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491371/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491370/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491369/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491367/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491368/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491366/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491365/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925799/+attachment/5491364/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925799] [NEW] touchpad not detected
Public bug reported: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-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: 06/19/2020 dmi.bios.release: 2.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2DA dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWE2U38T dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected focal fujitsu groovy i2c-hid touchpad ** Tags added: apport-collected groovy ** Description changed: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: fred 1391 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-04-21 (1 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVWE2U38T + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=42255c71-58a4-41f7-8a2e-020ded88a596 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-50-generic N/A + linux-backports-modules-5.8.0-50-generic N/A + linux-firmware1.190.3 + Tags: groovy + Uname: Linux 5.8.0-50-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: 06/19/2020 + dmi.bios.release: 2.12 + dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.bios.version: Version 2.12 + dmi.board.name: FJNB2DA + dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.board.version: A2 + dmi.chassis.type: 31 + dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/19/2020:br2.12:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVWE2U38T:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DA:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvr: + dmi.product.family: LIFEBOOK-JR + dmi.product.name: FMVWE2U38T + dmi.product.sku: SK00 + dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925799 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook W3/E2 (FMVWE2U38) Ubuntu 20.04LTS (5.8.0-50.56-generic 5.8.18) Touchscreen & stylus work perfectly, but touchpad doesn't (not detected) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1391 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-21 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: F
[Kernel-packages] [Bug 1919492] Re: Hirsute update: v5.11.7 upstream stable release
Julian, you can see which upstream kernel it is based on with: /proc/version /proc/version_signature -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919492 Title: Hirsute update: v5.11.7 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact:    The upstream process for stable tree updates is quite similar    in scope to the Ubuntu SRU process, e.g., each patch has to    demonstrably fix a bug, and each patch is vetted by upstream    by originating either directly from a mainline/stable Linux tree or    a minimally backported form of that patch. The following upstream    stable patches should be included in the Ubuntu kernel:    v5.11.7 upstream stable release    from git://git.kernel.org/ Linux 5.11.7 KVM: arm64: Fix nVHE hyp panic host context restore mm/page_alloc.c: refactor initialization of struct page for holes in memory layout mm/memcg: rename mem_cgroup_split_huge_fixup to split_page_memcg and add nr_pages argument mm/memcg: set memcg when splitting page mm/madvise: replace ptrace attach requirement for process_madvise mm/userfaultfd: fix memory corruption due to writeprotect mm/highmem.c: fix zero_user_segments() with start > end KVM: arm64: Fix exclusive limit for IPA size KVM: arm64: Reject VM creation when the default IPA size is unsupported KVM: arm64: nvhe: Save the SPE context early KVM: arm64: Avoid corrupting vCPU context register in guest exit KVM: arm64: Fix range alignment when walking page tables KVM: arm64: Ensure I-cache isolation between vcpus of a same VM KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged KVM: x86: Ensure deadline timer has truly expired before posting its IRQ x86/entry: Fix entry/exit mismatch on failed fast 32-bit syscalls x86/sev-es: Use __copy_from_user_inatomic() x86/sev-es: Correctly track IRQ states in runtime #VC handler x86/sev-es: Check regs->sp is trusted before adjusting #VC IST stack x86/sev-es: Introduce ip_within_syscall_gap() helper x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2 kasan: fix KASAN_STACK dependency for HW_TAGS kasan, mm: fix crash with HW_TAGS and DEBUG_PAGEALLOC binfmt_misc: fix possible deadlock in bm_register_write powerpc: Fix missing declaration of [en/dis]able_kernel_vsx() powerpc: Fix inverted SET_FULL_REGS bitop powerpc/64s: Fix instruction encoding for lis in ppc_function_entry() efi: stub: omit SetVirtualAddressMap() if marked unsupported in RT_PROP table sched: Simplify set_affinity_pending refcounts sched: Fix affine_move_task() self-concurrency sched: Optimize migration_cpu_stop() sched: Simplify migration_cpu_stop() sched: Collate affine_move_task() stoppers sched/membarrier: fix missing local execution of ipi_sync_rq_state() sched: Fix migration_cpu_stop() requeueing linux/compiler-clang.h: define HAVE_BUILTIN_BSWAP* zram: fix broken page writeback zram: fix return value on writeback_store include/linux/sched/mm.h: use rcu_dereference in in_vfork() stop_machine: mark helpers __always_inline memblock: fix section mismatch warning seqlock,lockdep: Fix seqcount_latch_init() powerpc/64s/exception: Clean up a missed SRR specifier hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR perf/core: Flush PMU internal buffers for per-CPU events mptcp: fix memory accounting on allocation error mptcp: put subflow sock on connect error net: expand textsearch ts_state to fit skb_seq_state perf/arm_dmc620_pmu: Fix error return code in dmc620_pmu_device_probe() drm/nouveau: fix dma syncing for loops (v2) io_uring: perform IOPOLL reaping if canceler is thread itself arm64: mm: use a 48-bit ID map when possible on 52-bit VA builds configfs: fix a use-after-free in __configfs_open_file nvme-fc: fix racing controller reset and create association drm/ttm: Fix TTM page pool accounting block: rsxx: fix error return code of rsxx_pci_probe() NFSv4.2: fix return value of _nfs4_get_security_label() NFS: Don't gratuitously clear the inode cache when lookup failed NFS: Don't revalidate the directory permissions on a lookup failure SUNRPC: Set memalloc_nofs_save() for sync tasks arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory cpufreq: qcom-hw: Fix return value check in qcom_cpufreq_hw_cpu_init() cpufreq: qcom-hw: fix dereferencing freed memory 'data' net: macb: Add default usrio config to default gem config powerpc/sstep: Fix VSX instruction emulation sh_eth: fix TRSCER mask for R7S72100 net: phy: ti: take into account all possible interrupt sources mlxsw: spectrum_router: Ignore routes using a deleted
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I have this issue on Hirsuite. Is this only fixed in 5.8 and 5.10 but not 5.11? $ uname -a Linux example 5.11.8-051108-generic #202103200636 SMP Sat Mar 20 11:17:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I got the 5.11.8 kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.8/ because 5.11.0 caused GPU hangs for me on Intel 4770K Haswell. -- You 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 grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released 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. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. 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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
https://lists.cs.columbia.edu/pipermail/kvmarm/2020-September/042543.html this patch will slove this bug。 Can you test it？ ** Changed in: linux (Ubuntu) Status: Expired => New ** Also affects: kunpeng920 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: New Status in linux package in Ubuntu: New Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904895] Re: Network does not work after restart from Windows 10
Kai-Heng Feng (kaihengfeng), yes but when I reported this bug it was after I had fixed it. I could not report this bug when I had no internet connectivity. However, now that I run dmesg when after enabled the "Enable PME" setting on the NIC driver on Windows and restarted again, it still says "e1000e :00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None" despite not working. [0.199867] pci :00:19.0: [8086:153b] type 00 class 0x02 [0.199881] pci :00:19.0: reg 0x10: [mem 0xefc0-0xefc1] [0.199886] pci :00:19.0: reg 0x14: [mem 0xefc3d000-0xefc3dfff] [0.199892] pci :00:19.0: reg 0x18: [io 0xf080-0xf09f] [0.199937] pci :00:19.0: PME# supported from D0 D3hot D3cold ... [0.852959] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode ... [0.943948] e1000e :00:19.0 :00:19.0 (uninitialized): registered PHC clock [1.022272] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 74:d0:2b:9e:e9:58 [1.022274] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection [1.022314] e1000e :00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FF-0FF ... [ 40.746594] e1000e :00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None ** Attachment added: "This dmesg output is when there is no internet connectivity" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+attachment/5439657/+files/dmesg-when-offline.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: Incomplete Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904895] Re: Network does not work after restart from Windows 10
Alex Hung (alexhung), yes lspci shows the NIC. This is from "lspci -vvv": 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) DeviceName: Onboard LAN Subsystem: ASUSTeK Computer Inc. Ethernet Connection I217-V Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e ** Description changed: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. - - Under the "Power Management" tab, I unchecked the checkbox option "Allow - the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: Incomplete Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All
[Kernel-packages] [Bug 1904895] Re: Network does not work after restart from Windows 10
2020-11-18 15:37:54
Device PCI\VEN_8086_153B_859F1043_04\3&11583659&0 was
configured.
Driver Name: oem24.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Date: 09/29/2020
Driver Version: 12.19.0.16
Driver Provider: Intel
Driver Section: E153B.10.0.1.19H1
Driver Rank: 0xFF2001
Matching Device Id: PCI\VEN_8086_153B
Outranked Drivers: net1ic64.inf:PCI\VEN_8086_153B:00FF2001
Device Updated: true
Parent Device: ACPI\PNP0A08\0
--
2020-11-18 15:37:54
Device PCI\VEN_8086_153B_859F1043_04\3&11583659&0 had a
problem starting.
Driver Name: oem24.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: e1dexpress
Lower Filters:
Upper Filters:
Problem: 0x15
Problem Status: 0x0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904895
Title:
Network does not work after restart from Windows 10
Status in linux package in Ubuntu:
Confirmed
Bug description:
I got a Intel I217-V integrated on the motherboard, it is an Ethernet
NIC.
$ lspci
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V
(rev 04)
Before this worked good, but yesterday it stopped working after
restarting the computer from Windows 10. I suspect there might have
been some Windows update maybe.
It seems to work again after I went into the Device Manager in Windows
and turned off power management settings.
Under the "Power Management" tab, I unchecked the checkbox option
"Allow the computer to turn off this device to save power".
Under the "Advanced" tab, I selected the "Enable PME" option and
changed it from "Enabled" to "Disabled".
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.29.34
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shockzor 1889 F pulseaudio
/dev/snd/controlC0: shockzor 1889 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Nov 19 17:23:08 2020
HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9
InstallationDate: Installed on 2013-12-26 (2519 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.8.0-29-generic N/A
linux-backports-modules-5.8.0-29-generic N/A
linux-firmware1.190.1
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904895] Re: Network does not work after restart from Windows 10
I think so, but that it is in some sleeping state. Because it worked to do "ethtool eth0" and "ifconfig". I read on the web that someone had success with reset it by doing: $ echo 1 > /sys/devices/pci\:00/:00:19.0/reset But I never tried that. I think Windows does not power it off, but puts it into some sleep state. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904895] [NEW] Network does not work after restart from Windows 10
Public bug reported: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** 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/1904895 Title: Network does not work after restart from Windows 10 Status in linux package in Ubuntu: New Bug description: I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC. $ lspci 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe. It seems to work again after I went into the Device Manager in Windows and turned off power management settings. Under the "Power Management" tab, I unchecked the checkbox option "Allow the computer to turn off this device to save power". Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.29.34 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shockzor 1889 F pulseaudio /dev/snd/controlC0: shockzor 1889 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:23:08 2020 HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9 InstallationDate: Installed on 2013-12-26 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
** Also affects: kunpeng920/ubuntu-20.04-hwe 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/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: New Status in kunpeng920 upstream-kernel series: Incomplete Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
pls refer to this follow link issue: https://bugs.launchpad.net/kunpeng920/+bug/1859756 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
=》Patch to disable hisi_sec2 temporarily sent.
=》https://lists.ubuntu.com/archives/kernel-team/2020-June/110647.html
Can you test this following patch which have sent this lkml to enable
sec2 driver for ubuntu verson?
[PATCH] crypto: hisilicon - update SEC driver module parameter
As stress-ng running SEC engine on the Ubuntu OS,
we found that SEC only supports two threads each with one TFM
based on the default module parameter 'ctx_q_num'.
If running more threads, stress-ng will fail since it cannot
get more TFMs.
In order to fix this, we adjusted the default values
of the module parameters to support more TFMs.
Signed-off-by: Longfang Liu
Signed-off-by: Zaibo Xu
---
drivers/crypto/hisilicon/sec2/sec_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto/hisilicon/sec2/sec_main.c
b/drivers/crypto/hisilicon/sec2/sec_main.c
index a4cb58b..57de51f 100644
--- a/drivers/crypto/hisilicon/sec2/sec_main.c
+++ b/drivers/crypto/hisilicon/sec2/sec_main.c
@@ -30,9 +30,9 @@
#define SEC_SQE_SIZE 128
#define SEC_SQ_SIZE(SEC_SQE_SIZE * QM_Q_DEPTH)
-#define SEC_PF_DEF_Q_NUM 64
+#define SEC_PF_DEF_Q_NUM 256
#define SEC_PF_DEF_Q_BASE 0
-#define SEC_CTX_Q_NUM_DEF 24
+#define SEC_CTX_Q_NUM_DEF 2
#define SEC_CTX_Q_NUM_MAX 32
#define SEC_CTRL_CNT_CLR_CE0x301120
@@ -191,7 +191,7 @@ static const struct kernel_param_ops sec_ctx_q_num_ops = {
};
static u32 ctx_q_num = SEC_CTX_Q_NUM_DEF;
module_param_cb(ctx_q_num, _ctx_q_num_ops, _q_num, 0444);
-MODULE_PARM_DESC(ctx_q_num, "Queue num in ctx (24 default, 2, 4, ..., 32)");
+MODULE_PARM_DESC(ctx_q_num, "Queue num in ctx (2 default, 2, 4, ..., 32)");
static const struct kernel_param_ops vfs_num_ops = {
.set = vfs_num_set,
--
2.8.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867900
Title:
CPU stress test fails with focal kernel
Status in kunpeng920:
Incomplete
Status in kunpeng920 ubuntu-18.04-hwe series:
Incomplete
Status in kunpeng920 ubuntu-20.04 series:
Incomplete
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
We have several crypto accelerators for Hisilicon 1620 but unfortunately one
of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2
makes kernel to run crypto functions without accelerator.
[Fix]
Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver.
[Test]
$ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz
--times --af-alg 0
$ echo $?
[Regression Potential]
This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other
platform.
==
[Bug Description]
CPU stress test fails with focal kernel
[Steps to Reproduce]
1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable
2) sudo apt-add-repository -y ppa:hardware-certification/public
3) sudo apt install -y canonical-certification-server
4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux
5) Run CPU stress test with `sudo certify-advanced`
[Actual Results]
Failed with
stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such
device)
[Expected Results]
Passed
[Reproducibility]
100%
[Additional information]
Same test with bionic-update kernel passed
[Resolution]
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
this following patch will fix sec2 boot bug: crypto: hisilicon/sec2 - modify the SEC probe process https://www.spinics.net/lists/linux-crypto/msg47550.html can you open CONFIG_CRYPTO_TEST=m and CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=m to test acc driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867587] Re: [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch
** Summary changed: - [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE kernel branch + [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867587 Title: [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description] SAS patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] scsi: hisi_sas: Rename hisi_sas_cq.pci_irq_mask scsi: hisi_sas: Add prints for v3 hw interrupt converge and automatic affinity scsi: hisi_sas: Modify the file permissions of trigger_dump to write only scsi: hisi_sas: Replace magic number when handle channel interrupt scsi: hisi_sas: replace spin_lock_irqsave/spin_unlock_restore with spin_lock/spin_unlock scsi: hisi_sas: use threaded irq to process CQ interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. this aboving sec2 optimize code have a small bug, we have fixing it and can you revert aboving four patches? crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM this aboving 11 ACC patches is not problem and you merge it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
from log: Hardware name: Huawei XA320 V2 /BC82HPNB, BIOS 0.95 08/15/2019 this server is x6000, I think that it is not enabled sec driver. Can you provide this lscpi information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859269] Re: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch
I have confirmed that our internal test team have completed 28 testcases and not find any bug. now also are adding some testcase to test this Roce module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859269 Title: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.5rc6 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] Â Â 1) Â Â 2) Â Â 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] Â Â (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] RDMA/hns: Delete unnecessary callback functions for cq RDMA/hns: Rename the functions used inside creating cq RDMA/hns: Redefine the member of hns_roce_cq struct RDMA/hns: Redefine interfaces used in creating cq IB/umem: remove the dmasync argument to ib_umem_get RDMA/hns: Modify appropriate printings RDMA/hns: Fix non-standard error codes RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code RDMA/hns: Simplify doorbell initialization code RDMA/hns: Replace not intuitive function/macro names RDMA/hns: Modify fields of struct hns_roce_srq RDMA/hns: Delete unnecessary uar from hns_roce_cq RDMA/hns: Remove unnecessary structure hns_roce_sqp RDMA/hns: Delete unnecessary variable max_post RDMA/hns: Remove unsupported modify_port callback RDMA: Connect between the mmap entry and the umap_priv structure RDMA/hns: Fix build error again RDMA/hns: Fix memory leak on 'context' on error return path RDMA/hns: Bugfix for qpc/cqc timer configuration RDMA/hns: Fix to support 64K page for srq RDMA/hns: Delete BITS_PER_BYTE redefinition RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size() RDMA/hns: Release qp resources when failed to destroy qp RDMA/hns: Fix a spelling mistake in a macro RDMA/hns: Modify return value of restrack functions RDMA/hns: Modify variable/field name from vlan to vlan_id RDMA/hns: Fix wrong parameters when initial mtt of srq->idx_que RDMA/hns: remove a redundant le16_to_cpu RDMA/hns: Prevent memory leaks of eq->buf_list RDMA/hns: Correct the value of srq_desc_size RDMA/hns: Correct the value of HNS_ROCE_HEM_CHUNK_LEN RDMA/hns: Add support for reporting wc as software mode RDMA/hns: Bugfix for posting a wqe with sge RDMA/hns: Fix coding style issues RDMA/hns: Replace custom macros HNS_ROCE_ALIGN_UP RDMA/hns: Remove redundant print information RDMA/hns: Delete unnessary parameters in hns_roce_v2_qp_modify() RDMA/hns: Update the value of qp type RDMA/hns: Remove unused function hns_roce_init_eq_table() RDMA/hns: Avoid printing address of mtt page RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs update 01120 RDMA/hns: Get pf capabilities from firmware RDMA/hns: Add interfaces to get pf capabilities from firmware RDMA/hns: Remove some redundant variables related to capabilities RDMA/hns: Add support for extended atomic in userspace [Status] (In Progress): RDMA/hns: Delete unnecessary callback functions for cq (In Progress): RDMA/hns: Rename the functions used inside creating cq (In Progress): RDMA/hns: Redefine the member of hns_roce_cq struct (In Progress): RDMA/hns: Redefine interfaces used in creating cq (In Progress): IB/umem: remove the dmasync argument to ib_umem_get (In Progress): RDMA/hns: Modify appropriate printings (In Progress): RDMA/hns: Fix non-standard error codes (In Progress): RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code (In Progress): RDMA/hns: Simplify doorbell initialization code (In Progress): RDMA/hns: Replace not intuitive function/macro names (In Progress): RDMA/hns: Modify fields of struct hns_roce_srq (In Progress): RDMA/hns: Delete unnecessary uar from hns_roce_cq (In Progress): RDMA/hns: Remove unnecessary structure hns_roce_sqp (In Progress): RDMA/hns: Delete unnecessary variable max_post (In Progress): RDMA/hns: Remove unsupported modify_port callback (In Progress): RDMA: Connect between the mmap entry and the umap_priv structure (Fix committed): RDMA/hns: Fix build error again (Fix committed): RDMA/hns: Fix memory leak on 'context' on error return path (Fix committed): RDMA/hns: Bugfix for qpc/cqc timer configuration (Fix committed): RDMA/hns: Fix to support 64K page for srq (In Progress): RDMA/hns: Delete BITS_PER_BYTE redefinition (Fix committed): RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size() (Fix committed): RDMA/hns: Release
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
ubuntu@ubuntu:~$ dmesg | grep sfc [ 29.360735] hisi-sfc-v3xx HISI0341:00: hw version 0x351 ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.4.0-14-generic #17~d20200214t082755~5d13e758ee67~lp1860401 SMP Fri Feb 14 08:28 aarch64 aarch64 aarch64 GNU/Linux ubuntu@ubuntu:~$ cat /proc/mtd dev:size erasesize name mtd0: 0100 1000 "spi-PRP0001:00" ubuntu@ubuntu:~$ lsmod | grep sfc spi_hisi_sfc_v3xx 16384 0 ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
I use your provided deb to test this sfc driver. this sfc driver have been enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue pls ensuring this aboving patchset will merge into ubuntu 20.04 kernel verison. 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/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description]  hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce]   1)   2)   3) [Actual Results] [Expected Results] [Reproducibility] [Additional information]   (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue   net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem  net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
I can not find "treewide: Use sizeof_member() macro but found a similiar. Do you mean this patch? commit c593642c8be046915ca3a4a300243a68077cd207 Author: Pankaj Bharadiya Date: Mon Dec 9 10:31:43 2019 -0800 treewide: Use sizeof_field() macro Replace all the occurrences of FIELD_SIZEOF() with sizeof_field() except at places where these are defined. Later patches will remove the unused definition of FIELD_SIZEOF(). you can ignore this patchset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description]  hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce]   1)   2)   3) [Actual Results] [Expected Results] [Reproducibility] [Additional information]   (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue   net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem  net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP
[Kernel-packages] [Bug 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch
** Summary changed: - [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch + [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
thank you! I will test it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
** Description changed: [Bug Description]  hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce]   1)   2)   3) [Actual Results] [Expected Results] [Reproducibility] [Additional information]   (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue   net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem  net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver + update 0120 + net: hns3: pad the short frame before sending to the hardware + + [Status] (In Progress): net: hns3: support tx-scatter-gather-fraglist feature (In Progress): net: hns3: add support for configuring VF MAC from the host (In Progress): net: hns3: add support for configuring bandwidth of VF on the host (In Progress): net: hns3: add support for setting VF trust (In Progress): net: hns3: add support for spoof check setting (In Progress): net: hns3: add support for setting VF link status on the host (In Progress): net: hns3: make array tick_array static, makes object smaller (Fix committed): net: hns3: fix a wrong reset interrupt status mask (Fix committed): net: hns3: cleanup of stray struct hns3_link_mode_mapping (Fix committed): net: hns3: fix ETS bandwidth validation bug (Fix committed): net: hns3: reallocate SSU' buffer size when
[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
=>Is this bug duplicate of bug 1853999? No, it should inject diff error type. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: Triaged Status in linux source package in Focal: Fix Released Bug description: "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854550] Re: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices
if this patch merge into this linus 5.5 version, whether we can backport ubuntu 18.04.4 update version or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854550 Title: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Triaged Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Triaged Bug description: "[Steps to reproduce] Enable memleak, and do as follows: root@(none)$ echo 0 > /sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:10/phy-0:0:10/sas_phy/phy-0:0:10/enable [ 79.857888] hisi_sas_v2_hw HISI0162:01: dev[7:1] is gone root@(none)$ echo scan > /sys/kernel/debug/kmemleak [ 131.656603] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) root@(none)$ more /sys/kernel/debug/kmemleak unreferenced object 0x041da5c66000 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 5e c6 a5 1d 04 ff ff 01 00 00 00 00 00 00 00 .^.. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] kmem_cache_alloc+0x188/0x260 [<(ptrval)>] bsg_setup_queue+0x48/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041d8c075400 (size 128): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 40 25 97 1d 00 ff ff 00 00 00 00 00 00 00 00 .@%. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_realloc_tag_set_tags.part.70+0x48/0xd8 [<(ptrval)>] blk_mq_alloc_tag_set+0x1dc/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041da5c65e00 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_alloc_tag_set+0x254/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 root@(none)$ [solution] Fix by doing the queue removal in one place - in sas_rphy_remove() - instead of unregistering the queue in sas_rphy_remove() and finally cleaning up the queue in calling blk_cleanup_queue() from sas_end_device_release() or sas_expander_release(). Function bsg_remove_queue() can handle a NULL pointer q, so remove the precheck in sas_rphy_remove(). " scsi: scsi_transport_sas: Fix memory leak when removing devices To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1854550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Thanks Mauricio, We were able to get it to work with the netinstall iso and the kernel parameters you provided. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Released Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Released Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact]  * It's not possible to access iBFT (iSCSI Boot Firmware Table) information    (settings for network interface, initiator, and target) in the installer    because the 'iscsi_ibft' module is not present in udeb packages.  * Even if it was, the installer does not handle iBFT information at all,    thus any settings are ignored, and iSCSI-related configuration has to    be done manually or with workarounds.  * This impacts user-experience and automatic installation on systems and    deployments which actually do provide the iBFT feature and information,    but cannot use it practically.  * With proper iBFT support in the installer (kernel module in udeb package    and automatic iSCSI-related configuration) users will be able to rely on    iBFT to install/deploy Ubuntu on their servers and datacenters.  * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,    and configure network/iSCSI according to iBFT information in disk-detect.    This is done in disk-detect so that the iSCSI LUNs are detected as disks    (useful in case of no other disks in the system so the installer doesn't    complain nor wait too long) and that any partman-related preseed options    are not required and may be still available for the user. [Test Case]  * linux package / kernel module in udeb:    $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko    Check the module loads in the installer environment.    See comment with example for disco.  * d-i/hw-detect/partman-iscsi package:    See comments 11, 12, 13. [Regression Potential]  * linux package: low, the kernel module is not loaded by default,    and only checks whether iBFT information is present in firmware,    then exposes that in sysfs in read-only mode.  * d-i/hw-detect/partman-iscsi:    - d-i: kernel version update to include iscsi_ibft module,   based on kernel released to -updates plus one week   monitoring bug reports -- it should be OK.   Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64   on baremetal -- see comment 11.    - hw-detect: low, the changes are enabled by a preseed option. see comment 12.    - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info]  * This has been verified both by the developer with a simple iSCSI    iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)    and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello, we are also running in to this same issue. I see that the bug appears to be fixed as of June 24th, but how would an end user like myself be able to get a hold of this? It appears the Ubuntu Server minimal iso is still an old version that does not contain the fix? 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/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Released Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Released Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact]  * It's not possible to access iBFT (iSCSI Boot Firmware Table) information    (settings for network interface, initiator, and target) in the installer    because the 'iscsi_ibft' module is not present in udeb packages.  * Even if it was, the installer does not handle iBFT information at all,    thus any settings are ignored, and iSCSI-related configuration has to    be done manually or with workarounds.  * This impacts user-experience and automatic installation on systems and    deployments which actually do provide the iBFT feature and information,    but cannot use it practically.  * With proper iBFT support in the installer (kernel module in udeb package    and automatic iSCSI-related configuration) users will be able to rely on    iBFT to install/deploy Ubuntu on their servers and datacenters.  * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,    and configure network/iSCSI according to iBFT information in disk-detect.    This is done in disk-detect so that the iSCSI LUNs are detected as disks    (useful in case of no other disks in the system so the installer doesn't    complain nor wait too long) and that any partman-related preseed options    are not required and may be still available for the user. [Test Case]  * linux package / kernel module in udeb:    $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko    Check the module loads in the installer environment.    See comment with example for disco.  * d-i/hw-detect/partman-iscsi package:    See comments 11, 12, 13. [Regression Potential]  * linux package: low, the kernel module is not loaded by default,    and only checks whether iBFT information is present in firmware,    then exposes that in sysfs in read-only mode.  * d-i/hw-detect/partman-iscsi:    - d-i: kernel version update to include iscsi_ibft module,   based on kernel released to -updates plus one week   monitoring bug reports -- it should be OK.   Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64   on baremetal -- see comment 11.    - hw-detect: low, the changes are enabled by a preseed option. see comment 12.    - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info]  * This has been verified both by the developer with a simple iSCSI    iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)    and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
I find this "Mellonox 25Gigabit-64bit-SFP28-2port– PCIe3.0 X8–15B3-1015-2" card can require 260M CMA memory. If we insert 2 or 3...4 Mellonox card, this card will fail to init it, so we should disable this cma config or set 1024M or above CMA memory. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Got it fixed by in with my MIO-892: /etc/pulse/daemon.conf: default-sample-rate = 48000 /etc/modprobe.d/azalia-microphone.conf #Valid values for position_fix are: #0 = Auto #1 = None #2 = POSBUF #3 = FIFO size options snd-hda-intel position_fix=0 For Echo/Noise Cancellation: /etc/pulse/default.pa load-module module-echo-cancel use_master_format=1 aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" source_name=echoCan$ set-default-source echoCancel_source set-default-sink echoCancel_sink Its mainly taken from the arch-wiki - but only 'this' combination worked for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
i've the same Problem on Ubuntu 18.10. I'm running a Asus P9D-X (no Onboard Sound) with a Asus MIO 892 (Realtek)-Card which is detected as Intel-HDA: 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) cat /proc/asound/cards : 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xd321 irq 35 head -n 1 /proc/asound/card0/codec* : Codec: Realtek ALC892 lsmod | grep "^snd" | cut -d " " -f 1 : snd_seq_dummy snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_oxygen snd_oxygen_lib snd_mpu401_uart snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Tested on Dell Precission 5520 with Ubuntu 18.04. This suffer from a consistently high power usage in the Intel (Power saving) mode. Proposed Packages install fine. After reboot switching Prime profile did not seem applied with logout+login. Reboot was required. After a further 'apt upgrade' which pull in some new updated the Prime profile switch work with just a logout+login. I assume I got a gdm3 update which was required. Looking at power graphs from the 'Power Statistics' tool i am getting much better power usage (first time under 10W). Thanks for the work. Will add a second comment if anything crops up after more usage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
hi daniel
this bug also affect this ubuntu 18.04.0 version which using bionic
kernel branch(kernel 4.15), because this patchset have merged into
mainline linus kernel 4.16rc1 (after kernel 4.15).
I want to add this bionic tag, but i fail it. Can you add this bionic
tag to merge this patchset into bionic branch.
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/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Fix Released
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
** Also affects: linux
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/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Fix Released
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
whether this patchset will merge into ubuntu 16.04.4 version or not? this
patchset will important for our DO5 board, Can you check it please?
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/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in linux package in Ubuntu:
Confirmed
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
hi daniel: whether this following mainline patchset have merge into this artful branch or not? If do not merge this patchset, this xwindow function will fail it. Can you confirm it and provide this artful branch in order to test it for me 505a1b5 vgaarb: Factor out EFI and fallback default device selection a37c0f4 vgaarb: Select a default VGA device even if there's no legacy VGA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
this patch will solve commit #10 bug, please merge this patch. 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/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
hi daniel please take care of this following patchset, other distro exist some xwindow crash issue. https://lists.freedesktop.org/archives/dri- devel/2017-November/159002.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/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
Starting Hostname Service... Ubuntu 17.10 ubuntu ttyAMA0 [ 68.535458] Internal error: Attempting to execute userspace memory: 8604 [#1] SMP [ 68.543288] Modules linked in: nls_iso8859_1 joydev input_leds shpchp ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ppdev lp parport ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hid_generic usbhid hid marvell hibmc_drm ttm aes_ce_blk drm_kms_helper aes_ce_cipher crc32_ce syscopyarea crct10dif_ce sysfillrect sysimgblt ghash_ce fb_sys_fops sha2_ce sha1_ce drm hisi_sas_v2_hw hisi_sas_main megaraid_sas libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk crypto_simd cryptd [ 68.607986] CPU: 39 PID: 2746 Comm: llvmpipe-1 Not tainted 4.13.0-16-generic #19-Ubuntu [ 68.615975] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.29 07/17/2017 [ 68.622576] task: 8013b88ecb00 task.stack: 8013b8dc4000 [ 68.628485] PC is at 0x0 [ 68.631026] LR is at ttm_bo_vm_fault+0x218/0x520 [ttm] [ 68.636151] pc : [<>] lr : [] pstate: 00400145 [ 68.643533] sp : 8013b8dc7ac0 [ 68.646834] x29: 8013b8dc7ac0 x28: [ 68.652134] x27: 0cb63000 x26: [ 68.657434] x25: 0208 x24: [ 68.662734] x23: 8013dd0e5240 x22: 8013dd0e50b0 [ 68.668034] x21: 0cb53000 x20: 8013b324d518 [ 68.67] x19: 093b8c08 x18: [ 68.678633] x17: x16: [ 68.683933] x15: x14: [ 68.689232] x13: x12: 8013ddcadc00 [ 68.694531] x11: x10: 8013e5f62900 [ 68.699831] x9 : 001000eb x8 : 01dd85b8 [ 68.705130] x7 : x6 : 8013b8dc7bf8 [ 68.710430] x5 : x4 : 0008 [ 68.715730] x3 : 0cb53000 x2 : [ 68.721029] x1 : x0 : 8013ddcadc00 [ 68.726329] Process llvmpipe-1 (pid: 2746, stack limit = 0x8013b8dc4000) [ 68.733364] Stack: (0x8013b8dc7ac0 to 0x8013b8dc8000) [ 68.739098] 7ac0: 8013b8dc7c00 082585a4 8013b8dc7cc0 0d73 [ 68.746914] 7ae0: 8013b324d518 08e2 8013b958bfe0 8013b888a580 [ 68.754731] 7b00: 8013b324d518 8013b888a5e8 0003 [ 68.762547] 7b20: 8013ddcadc00 8013ddcadc00 0cb53000 0cd5b000 [ 68.770363] 7b40: 8013b35824b0 8013b3582ed8 8013b35824d0 [ 68.778180] 7b60: 00b53000 8013b888a580 00680f4f [ 68.785996] 7b80: 140440fb 8013bd2908f0 [ 68.793813] 7ba0: 001002f2 8013b324d590 8013b324d590 [ 68.801629] 7bc0: 01dd85b8 001000eb 8013e5f62900 [ 68.809445] 7be0: 8013ddcadc00 00040d00 [ 68.817262] 7c00: 8013b8dc7c30 0825ca7c 8013b8dc7cc0 0d73 [ 68.825078] 7c20: 8013b8dc7c70 0825e628 [ 68.832894] 7c40: 0065 093b8000 8013b324d518 0825e52c [ 68.840710] 7c60: 0065 08165b38 8013b8dc7d30 0825eaac [ 68.848527] 7c80: 0054 8013b324d518 0cb53000 0040 [ 68.856343] 7ca0: 8013b888a580 0054 [ 68.864160] 7cc0: 8013b324d518 014200ca0054 001000eb 0cb53000 [ 68.871976] 7ce0: 8013b8625328 8013b958bfe0 [ 68.879792] 7d00: [ 68.887609] 7d20: 00040d00 8013b8dc7d60 08a80e10 [ 68.895425] 7d40: 8013b8dc7ec0 8013b88ecb00 0cb53000 9206 [ 68.903241] 7d60: 8013b8dc7dc0 08a81054 0cb53000 9206 [ 68.911058] 7d80: 8013b8dc7ec0 8013b8dc7ec0 08a97238 0024 [ 68.918874] 7da0: 9206 0cb53000 8013b88ecb00 [ 68.926690] 7dc0: 8013b8dc7df0 08081244 093b8000 9206 [ 68.934507] 7de0: 0cb53000 00040d00 08083508 [ 68.942323] 7e00: 8017f2d1b000 0d939338 [ 68.950139] 7e20: 2000 0200 8017fbce8090 fbcec080 [ 68.957955] 7e40: 08083930 8017f2d1b000 [ 68.965771]
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
I use this following 17.10 ISO to test this xwindow for D05 board. http://cdimage.ubuntu.com/releases/17.10/release/ubuntu-17.10-server- arm64.iso Then set this next step: sudo apt install ubuntu-desktop sudo reboot. this desktop will crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://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 1696477] Re: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1696440 *** https://bugs.launchpad.net/bugs/1696440 Thank you! On Jun 7, 2017 11:11 AM, "Apport retracing service" < 1696...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 1696440 *** > https://bugs.launchpad.net/bugs/1696440 > > Thank you for taking the time to report this crash and helping to make > this software better. This particular crash has already been reported > and is a duplicate of bug #1696440, so is being marked as such. Please > look at the other bug report to see if there is any missing information > that you can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Please continue to report any other bugs you may > find. > > ** Tags removed: need-duplicate-check > > ** This bug has been marked a duplicate of bug 1696440 >package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 128 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1696477 > > Title: > package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error > exit status 128 > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Im not sure what to do! > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-79-generic (not installed) > ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 > Uname: Linux 4.4.0-78-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: fred 1763 F pulseaudio > Date: Wed Jun 7 10:53:36 2017 > ErrorMessage: subprocess new pre-installation script returned error exit > status 128 > HibernationDevice: RESUME=UUID=eb37730f-e499-4cfb-882f-d3d6754f541a > InstallationDate: Installed on 2017-06-02 (4 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd > (Foxlink) >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP HP Notebook > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed > root=UUID=76523522-9d82-411c-9552-a2c7931bfda7 ro quiet splash > vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc N/A > SourcePackage: linux > Title: package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 128 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/19/2016 > dmi.bios.vendor: Insyde > dmi.bios.version: F.09 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 81EB > dmi.board.vendor: HP > dmi.board.version: 61.28 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook: > pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.28:cvnHP:ct10: > cvrChassisVersion: > dmi.product.name: HP Notebook > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1696477/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696477 Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Im not sure what to do! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID
[Kernel-packages] [Bug 1696477] [NEW] package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1696440 *** https://bugs.launchpad.net/bugs/1696440 Public bug reported: Im not sure what to do! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1763 F pulseaudio Date: Wed Jun 7 10:53:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=eb37730f-e499-4cfb-882f-d3d6754f541a InstallationDate: Installed on 2017-06-02 (4 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=76523522-9d82-411c-9552-a2c7931bfda7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.28:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696477 Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Im not sure what to do! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 1763 F pulseaudio Date: Wed Jun 7 10:53:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=eb37730f-e499-4cfb-882f-d3d6754f541a InstallationDate: Installed on 2017-06-02 (4 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=76523522-9d82-411c-9552-a2c7931bfda7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.28:cvnHP:ct
[Kernel-packages] [Bug 1578176] Re: Cannot place or recieve calls when using in-car bluetooth system
One interesting data point is that if you go into the bluetooth menu during the call and disconnect the device then the audio is correctly routed. I suspect the fundamental problem is the same for blue headset and speaker no be automatically routed when autoconnected. -- 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/1578176 Title: Cannot place or recieve calls when using in-car bluetooth system Status in bluez package in Ubuntu: Confirmed Bug description: After working around bug https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was able to pair the phone (BQ Aquaris E4.5) with the car hands-free system. However, thing don't quite work as expected. I can use the car's system to place a call using the phone, but The audio is not getting properly routed. After placing the call, I can't hear any sounds (not even the "ringing" noise), I don't get any feedback after the other person has answered the phone, and the other person can't hear me either. Furthermore, Long after the other person has hung up the call, the phone still looks like the call is ongoing (I have to manually disconnect it). I can also use the system to answer an incoming call, but the sympthoms are the same. No audio on either end. Would a debug log be helpful in this situation (https://wiki.ubuntu.com/DebuggingBluetooth)? Or is something else required? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1631719] Re: Intel GMA965 DRM hanging on yakkety
I think the non-existant firmware is not relevant for the older Intel Chips such as GMA965. This firmware is only for the latest chips. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1631719 Title: Intel GMA965 DRM hanging on yakkety Status in linux package in Ubuntu: Incomplete Bug description: Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic. System regularly hangs for 10 second intervals which is very noticeable in boot process. Cause seems to be the Intel GMA965 DRM support causing regular kernel warnings: WARNING: CPU: 0 PID: 1183 at /build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 drm_wait_one_vblank+0x1b6/0x1c0 [drm] The problem seems to start very early in the boot process, possible already in GRUB, definitely when the kernel image is first started. Workaround: Boot into Ubuntu recovery mode and then resume into graphical system. In this case the problem does not occur. Disabling GRUB graphics with GRUB_TERMINAL=console does not help ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-21-generic 4.8.0-21.23 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2377 F pulseaudio Date: Sun Oct 9 11:10:10 2016 HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab InstallationDate: Installed on 2012-08-21 (1509 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 8943DNG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-21-generic N/A linux-backports-modules-4.8.0-21-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago) dmi.bios.date: 10/22/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7QET27WW (1.09 ) dmi.board.name: 8943DNG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8943DNG dmi.product.version: ThinkPad R61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1631719] Re: Intel GMA965 DRM hanging on yakkety
As the problem report shows the system was upgraded, over many releases originally from Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 The lastest 16.04 kernel did not have the problem. I guess that gives us two bisection points. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1631719 Title: Intel GMA965 DRM hanging on yakkety Status in linux package in Ubuntu: Incomplete Bug description: Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic. System regularly hangs for 10 second intervals which is very noticeable in boot process. Cause seems to be the Intel GMA965 DRM support causing regular kernel warnings: WARNING: CPU: 0 PID: 1183 at /build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 drm_wait_one_vblank+0x1b6/0x1c0 [drm] The problem seems to start very early in the boot process, possible already in GRUB, definitely when the kernel image is first started. Workaround: Boot into Ubuntu recovery mode and then resume into graphical system. In this case the problem does not occur. Disabling GRUB graphics with GRUB_TERMINAL=console does not help ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-21-generic 4.8.0-21.23 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2377 F pulseaudio Date: Sun Oct 9 11:10:10 2016 HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab InstallationDate: Installed on 2012-08-21 (1509 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 8943DNG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-21-generic N/A linux-backports-modules-4.8.0-21-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago) dmi.bios.date: 10/22/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7QET27WW (1.09 ) dmi.board.name: 8943DNG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8943DNG dmi.product.version: ThinkPad R61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
