[Kernel-packages] [Bug 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working
Hi, I can add that the Airplane mode switch is not working for unblocking (both on installed and live system). $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked PRESS THE AIRPLANE BUTTON $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan blocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 blocked unblocked PRESS THE AIRPLANE BUTTON $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan blocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 blocked unblocked $ rfkill unblock all $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working
Last addition: also wifi is not working with the rtl8821ce-dkms package from the repository. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working
Hi, same issue when purging the rtl8821ce-dkms and enabling the in-tree driver. Same issue also booting 21.04 from a live USB, in this case also wifi is not working because the additional drivers tool cannot find any wifi 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/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922171] Re: Handle Intel Wifi firmware disconnection
** Tags added: oem-priority originate-from-1921340 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922171 Title: Handle Intel Wifi firmware disconnection Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Won't Fix Bug description: [Impact] Intel Wifi firmware may crash when it's connected to B/G wireless. [Fix] There's a new "feature" that when firmware thinks there are too much noise in the current frequency, it will automatically disconnect wifi and expect software/OS to change channel/frequency and reconnect. Otherwise, firmware crashes. [Test] [ 2651.943142] wlp0s20f3: associate with 00:24:a5:b5:f8:93 (try 1/3) [ 2651.951043] wlp0s20f3: RX AssocResp from 00:24:a5:b5:f8:93 (capab=0x421 status=0 aid=1) [ 2651.962960] wlp0s20f3: associated [ 2651.966183] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 2651.972582] wlp0s20f3: Driver requested disconnection from AP 00:24:a5:b5:f8:93 [ 2654.641627] wlp0s20f3: authenticate with 00:24:a5:b5:f8:93 Now it's "Driver requested disconnection" instead of firmware crash. [Where problems could occur] The first two patches on 80211 only provide new hook and don't bring any functional change. The third patch achieves the "feature" by removing cap IEEE80211_HE_PHY_CAP0_CHANNEL_WIDTH_SET_40MHZ_IN_2G. I am no expert on 80211, but if there's any AP that doesn't support 20MHZ for 2.4G, the reconnecting may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1922171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922171] [NEW] Handle Intel Wifi firmware disconnection
Public bug reported: [Impact] Intel Wifi firmware may crash when it's connected to B/G wireless. [Fix] There's a new "feature" that when firmware thinks there are too much noise in the current frequency, it will automatically disconnect wifi and expect software/OS to change channel/frequency and reconnect. Otherwise, firmware crashes. [Test] [ 2651.943142] wlp0s20f3: associate with 00:24:a5:b5:f8:93 (try 1/3) [ 2651.951043] wlp0s20f3: RX AssocResp from 00:24:a5:b5:f8:93 (capab=0x421 status=0 aid=1) [ 2651.962960] wlp0s20f3: associated [ 2651.966183] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 2651.972582] wlp0s20f3: Driver requested disconnection from AP 00:24:a5:b5:f8:93 [ 2654.641627] wlp0s20f3: authenticate with 00:24:a5:b5:f8:93 Now it's "Driver requested disconnection" instead of firmware crash. [Where problems could occur] The first two patches on 80211 only provide new hook and don't bring any functional change. The third patch achieves the "feature" by removing cap IEEE80211_HE_PHY_CAP0_CHANNEL_WIDTH_SET_40MHZ_IN_2G. I am no expert on 80211, but if there's any AP that doesn't support 20MHZ for 2.4G, the reconnecting may fail. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Won't Fix ** Tags: oem-priority originate-from-1921340 stella ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922171 Title: Handle Intel Wifi firmware disconnection Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Won't Fix Bug description: [Impact] Intel Wifi firmware may crash when it's connected to B/G wireless. [Fix] There's a new "feature" that when firmware thinks there are too much noise in the current frequency, it will automatically disconnect wifi and expect software/OS to change channel/frequency and reconnect. Otherwise, firmware crashes. [Test] [ 2651.943142] wlp0s20f3: associate with 00:24:a5:b5:f8:93 (try 1/3) [ 2651.951043] wlp0s20f3: RX AssocResp from 00:24:a5:b5:f8:93 (capab=0x421 status=0 aid=1) [ 2651.962960] wlp0s20f3: associated [ 2651.966183] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 2651.972582] wlp0s20f3: Driver requested disconnection from AP 00:24:a5:b5:f8:93 [ 2654.641627] wlp0s20f3: authenticate with 00:24:a5:b5:f8:93 Now it's "Driver requested disconnection" instead of firmware crash. [Where problems could occur] The first two patches on 80211 only provide new hook and don't bring any functional change. The third patch achieves the "feature" by removing cap IEEE80211_HE_PHY_CAP0_CHANNEL_WIDTH_SET_40MHZ_IN_2G. I am no expert on 80211, but if there's any AP that doesn't support 20MHZ for 2.4G, the reconnecting may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1922171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
This thread has gone from stupid to completely pointless.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
[Kernel-packages] [Bug 1918940] Re: Screen goes black randomly after upgrade from Xubuntu 18.04.5 LTS to Xubuntu 20.04.2 LTS
There's a few possibilities: 1. Check if you have both light-locker and xfce4-screensaver installed. If you do, you should be able to safely uninstall light-locker. 2. It could be related to graphics. Please run `inxi -G` and provide the output so we can identify your graphics card and 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/1918940 Title: Screen goes black randomly after upgrade from Xubuntu 18.04.5 LTS to Xubuntu 20.04.2 LTS Status in linux package in Ubuntu: Confirmed Bug description: Since I upgraded to 20.04.2 LTS I've had a problem (about once a day) with my screen going black. The computer is not unresponsive, but the only way to wake the screen up is to close and open the laptop lid. External screen is not affected. I'm on a HP Elitebook 820 notebook. Searched journalctl and dmesg logs but I can't find anything relevant there, so suspecting this has to do with a change of display driver and/or settings in the new version. Please contact me if more info would be helpful. Wish you a great day! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 1350 F pulseaudio /dev/snd/controlC1: a 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Mar 12 15:26:46 2021 HibernationDevice: RESUME=UUID=add5c1ba-194d-4f4d-af77-7049d2c84b9a InstallationDate: Installed on 2017-09-23 (1266 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 820 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=be312993-03d0-453d-97c0-f598bedc47ae ro text RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-13 (58 days ago) dmi.bios.date: 10/04/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.03 dmi.board.name: 1991 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.48 dmi.chassis.asset.tag: CNU3459W62 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.03:bd10/04/2013:svnHewlett-Packard:pnHPEliteBook820G1:pvrA3009DD10203:rvnHewlett-Packard:rn1991:rvrKBCVersion15.48:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G1 dmi.product.sku: D7V73AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working
Could you try uninstall rtl8821ce-dkms and reboot to use in-tree driver? $ sudo apt purge rtl8821ce-dkms You'll need a reboot to load in-tree driver. You can always install that back if necessary: $ sudo apt install rtl8821ce-dkms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: [rtl8821ce] [10ec:c821] Bluetooth not working
>From comment #5, you're running rtl8821ce-dkms dkms driver, not in- kernel modules. And this is rooted in driver init failure: mar 30 10:23:56 IdeaPad-L340 kernel: [ cut here ] mar 30 10:23:56 IdeaPad-L340 kernel: proc_dir_entry 'net/rtl8821ce' already registered mar 30 10:23:56 IdeaPad-L340 kernel: WARNING: CPU: 4 PID: 444 at fs/proc/generic.c:381 proc_register+0x86/0x100 mar 30 10:23:56 IdeaPad-L340 kernel: Modules linked in: kvm_intel(+) rtl8821ce(OE+) snd_pcm kvm snd_seq_midi snd_seq_midi_event i915 crct10dif_pclmul snd_rawmidi ghash_clmulni_intel aesni_intel uvcvideo btusb crypto_simd cryptd glue_helper snd_seq btrtl snd_seq_device rapl videobuf2_vmalloc btbcm 8821ce(OE) intel_cstate intel_wmi_thunderbolt serio_raw wmi_bmof efi_pstore snd_timer videobuf2_memops drm_kms_helper btintel videobuf2_v4l2 processor_thermal_device videobuf2_common processor_thermal_rfim cec bluetooth snd videodev processor_thermal_mbox i2c_algo_bit rc_core input_leds joydev processor_thermal_rapl fb_sys_fops mei_me ecdh_generic cfg80211 syscopyarea 8250_dw intel_rapl_common mc soundcore ecc sysfillrect intel_soc_dts_iosf mei intel_pch_thermal elan_i2c sysimgblt mac_hid ideapad_laptop sparse_keymap int3403_thermal int340x_thermal_zone int3400_thermal acpi_tad acpi_pad acpi_thermal_rel sch_fq_codel msr parport_pc ppdev lp parport drm sunrpc ip_tables x_tables autofs4 hid_generic usbhid crc32_pclmul mar 30 10:23:56 IdeaPad-L340 kernel: r8169 realtek ahci nvme intel_lpss_pci intel_lpss libahci i2c_hid i2c_i801 xhci_pci idma64 i2c_smbus nvme_core virt_dma xhci_pci_renesas hid wmi video pinctrl_cannonlake mar 30 10:23:56 IdeaPad-L340 kernel: CPU: 4 PID: 444 Comm: systemd-udevd Tainted: P OE 5.11.0-11-generic #12-Ubuntu mar 30 10:23:56 IdeaPad-L340 kernel: Hardware name: LENOVO 81LK/LNVNB161216, BIOS BGCN33WW 11/24/2020 mar 30 10:23:56 IdeaPad-L340 kernel: RIP: 0010:proc_register+0x86/0x100 mar 30 10:23:56 IdeaPad-L340 kernel: Code: c6 05 65 87 09 02 00 4c 89 e0 5b 41 5c 5d c3 49 8b 94 24 a0 00 00 00 48 8b b3 a0 00 00 00 48 c7 c7 30 78 5e 93 e8 43 60 80 00 <0f> 0b c6 05 39 87 09 02 00 41 8b 44 24 5c 48 c7 c7 10 df e0 93 8d mar 30 10:23:56 IdeaPad-L340 kernel: RSP: 0018:b174414dfcf0 EFLAGS: 00010286 mar 30 10:23:56 IdeaPad-L340 kernel: RAX: RBX: 919b41239a80 RCX: 919ca6318ac8 mar 30 10:23:56 IdeaPad-L340 kernel: RDX: ffd8 RSI: 0027 RDI: 919ca6318ac0 mar 30 10:23:56 IdeaPad-L340 kernel: RBP: b174414dfd00 R08: R09: b174414dfad0 mar 30 10:23:56 IdeaPad-L340 kernel: R10: b174414dfac8 R11: 93d53508 R12: 919b44bd8c00 mar 30 10:23:56 IdeaPad-L340 kernel: R13: 919b463f22e0 R14: R15: c183fe40 mar 30 10:23:56 IdeaPad-L340 kernel: FS: 7fb0bf69c8c0() GS:919ca630() knlGS: mar 30 10:23:56 IdeaPad-L340 kernel: CS: 0010 DS: ES: CR0: 80050033 mar 30 10:23:56 IdeaPad-L340 kernel: CR2: 555a7bc0 CR3: 00010cc90004 CR4: 003706e0 mar 30 10:23:56 IdeaPad-L340 kernel: Call Trace: mar 30 10:23:56 IdeaPad-L340 kernel: ? 0xc1885000 mar 30 10:23:56 IdeaPad-L340 kernel: proc_mkdir_data+0x6d/0x90 mar 30 10:23:56 IdeaPad-L340 kernel: rtw_drv_proc_init+0x3b/0xc8 [rtl8821ce] mar 30 10:23:56 IdeaPad-L340 kernel: ? 0xc1885000 mar 30 10:23:56 IdeaPad-L340 kernel: rtw_drv_entry+0x28/0x1000 [rtl8821ce] mar 30 10:23:56 IdeaPad-L340 kernel: do_one_initcall+0x48/0x1d0 mar 30 10:23:56 IdeaPad-L340 kernel: ? kmem_cache_alloc_trace+0xf6/0x200 mar 30 10:23:56 IdeaPad-L340 kernel: ? do_init_module+0x28/0x290 mar 30 10:23:56 IdeaPad-L340 kernel: do_init_module+0x62/0x290 mar 30 10:23:56 IdeaPad-L340 kernel: load_module+0x6f3/0x770 mar 30 10:23:56 IdeaPad-L340 kernel: __do_sys_finit_module+0xc2/0x120 mar 30 10:23:56 IdeaPad-L340 kernel: __x64_sys_finit_module+0x1a/0x20 mar 30 10:23:56 IdeaPad-L340 kernel: do_syscall_64+0x38/0x90 mar 30 10:23:56 IdeaPad-L340 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 mar 30 10:23:56 IdeaPad-L340 kernel: RIP: 0033:0x7fb0bfb52edd mar 30 10:23:56 IdeaPad-L340 kernel: Code: 29 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5b df 0c 00 f7 d8 64 89 01 48 mar 30 10:23:56 IdeaPad-L340 kernel: RSP: 002b:7ffeed5aa538 EFLAGS: 0246 ORIG_RAX: 0139 mar 30 10:23:56 IdeaPad-L340 kernel: RAX: ffda RBX: 5565f93cea70 RCX: 7fb0bfb52edd mar 30 10:23:56 IdeaPad-L340 kernel: RDX: RSI: 7fb0bfcf9e2d RDI: 0010 mar 30 10:23:56 IdeaPad-L340 kernel: RBP: 0002 R08: R09: 5565f815089d mar 30 10:23:56 IdeaPad-L340 kernel: R10: 0010 R11: 0246 R12: 7fb0bfcf9e2d mar 30 10:23:56 IdeaPad-L340 kernel: R13: R14:
[Kernel-packages] [Bug 1921829] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1921829 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: [rtl8821ce] [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: [rtl8821ce] [10ec:c821] Bluetooth not working
** Summary changed: - [rtl8821ce] Bluetooth not working + [rtl8821ce] [10ec:c821] Bluetooth not working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: [rtl8821ce] [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: [rtl8821ce] Bluetooth not working
Possibly related to bug 1853665. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: [rtl8821ce] [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: [rtl8821ce] Bluetooth not working
I can't seem to reproduce the problem in Ubuntu 21.04 here so it seems to be machine-specific. And indeed the log in comment #5 is showing some kernel crashes in rtl8821ce that might be relevant. ** Summary changed: - Bluetooth not working + [rtl8821ce] Bluetooth not working ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1921829 Title: [rtl8821ce] [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922152] [NEW] F atal error: classmap.h: No such file or directory
Public bug reported: When building kernel module on ubuntu 20.04 server for raspberry (aarch64), I get the following error: make -C /lib/modules/5.4.0-1032-raspi/build SUBDIRS=/home/ubuntu/andor/src/driver modules make[1]: Entering directory '/usr/src/linux-headers-5.4.0-1032-raspi' HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:18:10: fatal error: classmap.h: No such file or directory 18 | #include "classmap.h" | ^~~~ compilation terminated. make[4]: *** [scripts/Makefile.host:107: scripts/selinux/genheaders/genheaders] Error 1 make[3]: *** [scripts/Makefile.build:522: scripts/selinux/genheaders] Error 2 make[2]: *** [scripts/Makefile.build:522: scripts/selinux] Error 2 make[1]: *** [Makefile:1127: scripts] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-1032-raspi' make: *** [Makefile:12: default] Error 2 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1922152 Title: F atal error: classmap.h: No such file or directory Status in linux-raspi package in Ubuntu: New Bug description: When building kernel module on ubuntu 20.04 server for raspberry (aarch64), I get the following error: make -C /lib/modules/5.4.0-1032-raspi/build SUBDIRS=/home/ubuntu/andor/src/driver modules make[1]: Entering directory '/usr/src/linux-headers-5.4.0-1032-raspi' HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:18:10: fatal error: classmap.h: No such file or directory 18 | #include "classmap.h" | ^~~~ compilation terminated. make[4]: *** [scripts/Makefile.host:107: scripts/selinux/genheaders/genheaders] Error 1 make[3]: *** [scripts/Makefile.build:522: scripts/selinux/genheaders] Error 2 make[2]: *** [scripts/Makefile.build:522: scripts/selinux] Error 2 make[1]: *** [Makefile:1127: scripts] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-1032-raspi' make: *** [Makefile:12: default] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1922152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** Tags added: ipu6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u
[Kernel-packages] [Bug 1922111] Re: acpitz-acpi-0 wrong temperature
Data from acpitz (acpi thermalzone) are from BIOS. The peak values you are seeing can be the results of BIOS/EC sampling mechanism, i.e. instantaneous values instead of average values. The must be fixed in BIOS/EC firmware not in OS; however, you can disable acpitz by kernel parameter "thermal.off=1" (see how @ https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot- parameter) if your system has another reliable temperature sensor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1918970 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482858/+files/acpidump.txt ** Description changed: I realized that acpitz-acpi-0 is not well calibrated and it will spike - at random times to 70+ for a second or two and it will come back down to - 45C which is the same as Package id 0 from coretemp-isa-. + at random times to 70C+ for a second or two and it will come back down + to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: juno 1510 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: - linux-restricted-modules-5.8.0-49-generic N/A - linux-backports-modules-5.8.0-49-generic N/A - linux-firmware1.187.10 + linux-restricted-modules-5.8.0-49-generic N/A + linux-backports-modules-5.8.0-49-generic N/A + linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic
[Kernel-packages] [Bug 1922111] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482848/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482847/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482849/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482857/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482850/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482846/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482843/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482841/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482855/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482854/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482856/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482853/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482851/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482845/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482844/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482852/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482842/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Re: acpitz-acpi-0 wrong temperature
apport information ** Tags added: apport-collected focal ** Description changed: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: juno 1510 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-12-09 (111 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) + MachineType: Notebook NV4XMB,ME,MZ + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-49-generic N/A + linux-backports-modules-5.8.0-49-generic N/A + linux-firmware1.187.10 + Tags: focal + Uname: Linux 5.8.0-49-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 11/03/2020 + dmi.bios.release: 7.6 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.06 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: NV4XMB,ME,MZ + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.ec.firmware.release: 7.2 + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: NV4XMB,ME,MZ + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1922111/+attachment/5482840/+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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1922124] [NEW] Bionic update: upstream stable patchset 2021-03-31
Public bug reported: 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: upstream stable patchset 2021-03-31 Ported from the following upstream stable releases: v4.14.224, v4.19.179 v4.14.225, v4.19.180 from git://git.kernel.org/ net: usb: qmi_wwan: support ZTE P685M modem scripts: use pkg-config to locate libcrypto scripts: set proper OpenSSL include dir also for sign-file hugetlb: fix update_and_free_page contig page struct assumption drm/virtio: use kvmalloc for large allocations virtio/s390: implement virtio-ccw revision 2 correctly arm64 module: set plt* section addresses to 0x0 arm64: Avoid redundant type conversions in xchg() and cmpxchg() arm64: cmpxchg: Use "K" instead of "L" for ll/sc immediate constraint arm64: Use correct ll/sc atomic constraints JFS: more checks for invalid superblock media: mceusb: sanity check for prescaler value xfs: Fix assert failure in xfs_setattr_size() smackfs: restrict bytes count in smackfs write functions net: fix up truesize of cloned skb in skb_prepare_for_shift() mm/hugetlb.c: fix unnecessary address expansion of pmd sharing net: bridge: use switchdev for port flags set through sysfs too dt-bindings: net: btusb: DT fix s/interrupt-name/interrupt-names/ staging: fwserial: Fix error handling in fwserial_create x86/reboot: Add Zotac ZBOX CI327 nano PCI reboot quirk vt/consolemap: do font sum unsigned wlcore: Fix command execute failure 19 for wl12xx pktgen: fix misuse of BUG_ON() in pktgen_thread_worker() ath10k: fix wmi mgmt tx queue full due to race condition x86/build: Treat R_386_PLT32 relocation as R_386_PC32 Bluetooth: Fix null pointer dereference in amp_read_loc_assoc_final_data staging: most: sound: add sanity check for function argument media: uvcvideo: Allow entities with no pads f2fs: handle unallocated section and zone on pinned/atgc parisc: Bump 64-bit IRQ stack size to 64 KB Xen/gnttab: handle p2m update errors on a per-slot basis xen-netback: respect gnttab_map_refs()'s return value zsmalloc: account the number of compacted pages correctly swap: fix swapfile read/write offset media: v4l: ioctl: Fix memory leak in video_usercopy PCI: Add a REBAR size quirk for Sapphire RX 5600 XT Pulse drm/amd/display: Guard against NULL pointer deref when get_i2c_info fails f2fs: fix to set/clear I_LINKABLE under i_lock btrfs: fix error handling in commit_fs_roots ALSA: hda/realtek: Add quirk for Clevo NH55RZQ ALSA: hda/realtek: Apply dual codec quirks for MSI Godlike X570 board UBUNTU: upstream stable to v4.14.224, v4.19.179 btrfs: raid56: simplify tracking of Q stripe presence btrfs: fix raid6 qstripe kmap usbip: tools: fix build error for multiple definition ALSA: ctxfi: cthw20k2: fix mask on conf to allow 4 bits rsxx: Return -EFAULT if copy_to_user() fails dm table: fix iterate_devices based device capability checks dm table: fix DAX iterate_devices based device capability checks dm table: fix zoned iterate_devices based device capability checks iommu/amd: Fix sleeping in atomic in increase_address_space() mwifiex: pcie: skip cancel_work_sync() on reset failure path platform/x86: acer-wmi: Cleanup ACER_CAP_FOO defines platform/x86: acer-wmi: Cleanup accelerometer device handling platform/x86: acer-wmi: Add new force_caps module parameter platform/x86: acer-wmi: Add ACER_CAP_SET_FUNCTION_MODE capability flag platform/x86: acer-wmi: Add support for SW_TABLET_MODE on Switch devices platform/x86: acer-wmi: Add ACER_CAP_KBD_DOCK quirk for the Aspire Switch 10E SW3-016 PCI: Add function 1 DMA alias quirk for Marvell 9215 SATA controller misc: eeprom_93xx46: Add quirk to support Microchip 93LC46B eeprom drm/msm/a5xx: Remove overwriting A5XX_PC_DBG_ECO_CNTL register Revert "zram: close udev startup race condition as default groups" HID: mf: add support for 0079:1846 Mayflash/Dragonrise USB Gamecube Adapter UBUNTU: upstream stable to v4.14.225, v4.19.180 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal
[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay
I think one reason might have been that a dependency between this package and systemd wanted to be avoided. And was the service part of kvm_stats from the very beginning (I don't remember) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921870 Title: [UBUNTU 21.04] tools/kvm_stat: Add restart delay Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, Systemd's initial attempt to start the kvm unit file may fail in case the kvm module is not loaded. However, once the kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, Systemd restarts with a minimum delay a number of times before giving up and disabling the service. Which means a subsequent kvm module load will have kvm running without monitoring. Solution: Add an appropriate delay in the unit file. Reproduction: (1) Enable the kvm service via systemctl (2) Reboot (3) Verify that the kvm module is not loaded & kvm service not running (4) Load the kvm module via 'modprobe kvm' (5) Verify that the kvm service came up within the next minute. Preventive:yes Just use the attached patch and you're good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
in response to comment #2) That would be indeed a valid approach (and I think we already had that once in the z13s prototype), since we run in such a situation always on a system in DPM mode, were one usually have only selected devices configured (compared to a system in PR/SM classic mode, where one often heavily shares devices). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1918970 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841304] Re: sky2 ethernet card don't work after returning from suspension
sky2.disable_msi=1 solves my issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841304 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Linux 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux error similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 however, all kernel patches do not fix this error !! maybe it is related to specific hardware / BIOS version? in my case the Samsung R780 laptop terminal fix helps: sudo modprobe -r sky2; sudo modprobe -i sky2 or an entry in GRUB GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash pci = nomsi, noaer" I think the problem is rather related to the option: pci = nomsi, noaer regards! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kris 1748 F pulseaudio /dev/snd/controlC0: kris 1748 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: SAMSUNG ELECTRONICS CO., LTD. R780/R778 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=89a089ca-faca-4b1e-be43-8cdd057ae525 ro quiet splash pci=nomsi,noaer ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04JA.M017.20100114.LDG dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: R780/R778 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04JA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04JA.M017.20100114.LDG:bd01/14/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR780/R778:pvr04JA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR780/R778:rvr04JA:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: R780/R778 dmi.product.version: 04JA dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841304] Re: sky2 ethernet card don't work after returning from suspension
System: Kernel: 5.8.0-48-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.2 LTS (Focal Fossa) Machine: Type: Desktop System: Acer product: Aspire E380 v: R01-B4 serial: Mobo: Acer model: EM61SM/EM61PM serial: BIOS: Phoenix v: R01-B4 date: 12/29/2006 Network: Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet vendor: Elite Systems driver: sky2 v: 1.30 port: ac00 bus ID: 03:00.0 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: mpqemubr0 state: down mac: IF-ID-2: mpqemubr0-dummy state: down mac: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841304 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Linux 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux error similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 however, all kernel patches do not fix this error !! maybe it is related to specific hardware / BIOS version? in my case the Samsung R780 laptop terminal fix helps: sudo modprobe -r sky2; sudo modprobe -i sky2 or an entry in GRUB GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash pci = nomsi, noaer" I think the problem is rather related to the option: pci = nomsi, noaer regards! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kris 1748 F pulseaudio /dev/snd/controlC0: kris 1748 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: SAMSUNG ELECTRONICS CO., LTD. R780/R778 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=89a089ca-faca-4b1e-be43-8cdd057ae525 ro quiet splash pci=nomsi,noaer ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04JA.M017.20100114.LDG dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: R780/R778 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04JA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04JA.M017.20100114.LDG:bd01/14/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR780/R778:pvr04JA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR780/R778:rvr04JA:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: R780/R778 dmi.product.version: 04JA dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
Alternative to all of the above, you could choose to "enable all the devices" hack on 18.04. Aka if the MAAS initrd includes a script to do `chzdev -e --all` by default on 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918970] Re: Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition
In https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu3 in eoan+ manual chzdev -e got added to activate qeth devices, if they have been specified in the ip= command, i.e. if enc300 is the device in the ip= command. This has not been backported to bionic. To boot without specifying the device name, i.e. with just mac address one will need automatic chzdev device configuration via /sys/firmware/sclp_sd/config/data that was added in s390-tools v2.5.0 fist available in cosmic+ but that also needs kernel support for sclp_sd driver to exist, i.e first added in v4.16. Thus if one wants this support one will need to backport 1) initramfs-tools changes 2) s390-tools changes 3) linux sclp_sd driver from linux-hwe to GA ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition + Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841304] Re: sky2 ethernet card don't work after returning from suspension
I am experiencing the same issue with an old Acer T180. My kernel version is 5.8.0-48-generic. My Ethernet card is a Marvell 88E8056. Let me know if you need further information, I would be willing to help 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/1841304 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Linux 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux error similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 however, all kernel patches do not fix this error !! maybe it is related to specific hardware / BIOS version? in my case the Samsung R780 laptop terminal fix helps: sudo modprobe -r sky2; sudo modprobe -i sky2 or an entry in GRUB GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash pci = nomsi, noaer" I think the problem is rather related to the option: pci = nomsi, noaer regards! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kris 1748 F pulseaudio /dev/snd/controlC0: kris 1748 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: SAMSUNG ELECTRONICS CO., LTD. R780/R778 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=89a089ca-faca-4b1e-be43-8cdd057ae525 ro quiet splash pci=nomsi,noaer ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04JA.M017.20100114.LDG dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: R780/R778 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04JA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04JA.M017.20100114.LDG:bd01/14/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR780/R778:pvr04JA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR780/R778:rvr04JA:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: R780/R778 dmi.product.version: 04JA dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I have not had any problem with Nouveau and Wayland so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=4e0782c5-5436-4e47-9813-0946aea670c3 ro quiet splash
[Kernel-packages] [Bug 1922111] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1922111 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] Re: acpitz-acpi-0 wrong temperature
** Description changed: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 - Kernel 5.10.0-1020-oem + Kernel 5.8.0-49-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Incomplete Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922111] [NEW] acpitz-acpi-0 wrong temperature
Public bug reported: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.10.0-1020-oem ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: New Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.10.0-1020-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55
Still seems to fail: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/n/nvidia-graphics- drivers-390/20210331_152743_2b7cd@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: Bluetooth not working
The issue is not due to the settings if the command line is failing, reassigning but it could be a kernel or driver problem, it could be worth trying to boot an older or newer kernel to try ** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1921829 Title: Bluetooth not working Status in bluez package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] [NEW] Bluetooth not working
You have been subscribed to a public bug: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) ** Affects: bluez (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug hirsute -- Bluetooth not working https://bugs.launchpad.net/bugs/1921829 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71
upstream commit a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback:
don't leak persistent grants from xen_blkbk_map()")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921902
Title:
Security-Fix Xen XSA 371 for Kernel 5.4.0-71
Status in linux package in Ubuntu:
Confirmed
Bug description:
Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published
which contain a security patch for a commit which is included in proposed
5.4.0-71.
The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line
maybe you can add this security fix to 5.4.0-71 release.
Thank you in advance.
Original Commit:
XSA-365: xen-blkback: fix error handling in xen_blkbk_map()
New commit with security fix:
XSA-371: xen-blkback: don't leak persistent grants from xen_blkbk_map()
See
- http://xenbits.xen.org/xsa/advisory-371.html
- http://xenbits.xen.org/xsa/xsa371-linux.patch
- http://xenbits.xen.org/xsa/advisory-365.html
- http://xenbits.xen.org/xsa/xsa365-linux.patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55
Re-triggered ADT run with proposed version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1922099 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55
Please try again with 390.141-0ubuntu0.20.10.2 in groovy-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] [NEW] nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55
Public bug reported: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903288] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2021-03-31 10:31 EDT--- Hi, > If the key is self-signed, shouldn't having the key in .builtin_trusted_keys > allow for loading it into the IMA keyring? Or is that insufficient for some > reason? Yes, you could do that (I tried recently, in fact!), but then you'd need a userspace blob to perform that loading. As I understand it xnox isn't keen on more userspace blobs. Kind regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921995] Re: hirsute kernels 5.11 do not boot on AMD STONEY hardware
According to upstream bug this is fixed in v5.11.9. Hirsute update: v5.11.9 is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921712 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Fix Committed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919319] Re: hirsute/linux-raspi: Upstream raspberrypi patchset 2021-03-16
This bug was fixed in the package linux-raspi - 5.11.0-1004.4
---
linux-raspi (5.11.0-1004.4) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1004.4 -proposed tracker (LP: #1920139)
* Enable CONFIG_GPIO_CDEV_V1 (LP: #1919973)
- [Config] raspi: Set GPIO_CDEV_V1=y
* hirsute/linux-raspi: Upstream raspberrypi patchset 2021-03-16 (LP: #1919319)
- media: i2c: imx477: Remove auto frame length adjusting
- media: i2c: imx477: Add very long exposure control to the driver
- media: i2c: imx290: Fix up exposure calcuations and ranges
- media: i2c: imx290: Handle exposure correctly when vblank changes
- DAC overlays (#4154)
- configs: Change CONFIG_BLK_DEV_NVME=y for 2711
- media: i2c: imx477: Fix crop height for 2028x1080 mode
- media: i2c: imx477: Replace existing 1012x760 mode
- media: i2c: imx477: Remove internal v4l2_mbus_framefmt from the state
- media: i2c: imx477: Remove unused function parameter
- overlays: i2c-rtc: Add the Dallas DS1340
- overlays: Update the upstream overlay
- Revert "Bluetooth: Always request for user confirmation for Just Works (LE
SC)"
- Revert "Bluetooth: Always request for user confirmation for Just Works"
- media: bcm2835-unicam: Fix bug in buffer swapping logic
- Assign crypto aliases to different AES implementation modules
- overlays: Improve the i2c-rtc,i2c_csi_dsi option
- configs: Add CONFIG_RTS_HCTOSYS=y
- overlays: Add pcie-32bit-dma overlay
- [Config] raspi: updateconfigs after update to rpi-5.11.y (2021-03-16)
* Miscellaneous Ubuntu changes
- [Config] raspi: updateconfigs after rebase to Ubuntu-5.11.0-13.14
- [Packaging] raspi: remove dh-systemd build dependency
- [Packaging] raspi: Drop removed modules from the ABI
- [Packaging] raspi: Remove debian.raspi/d-i
- [Packaging] raspi: Remove the temporary build hook
- [Packaging] raspi: Remove disable_d_i from the build rules
- [Packaging] raspi: Fix vertical alignment of build rules
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
- bpf: Fix off-by-one for area size in creating mask to left
[ Ubuntu: 5.11.0-12.13 ]
* hirsute/linux: 5.11.0-12.13 -proposed tracker (LP: #1918148)
* Hirsute update: v5.11.7 upstream stable release (LP: #1919492)
- uapi: nfnetlink_cthelper.h: fix userspace compilation error
- powerpc/603: Fix protection of user pages mapped with PROT_NONE
- powerpc/perf: Fix handling of privilege level checks in perf interrupt
context
- powerpc/pseries: Don't enforce MSI affinity with kdump
- crypto: mips/poly1305 - enable for all MIPS processors
- mptcp: fix length of ADD_ADDR with port sub-option
- ath9k: fix transmitting to stations in dynamic SMPS mode
- net: Fix gro aggregation for udp encaps with zero csum
- net: check if protocol extracted by virtio_net_hdr_set_proto is correct
- net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0
- ath11k: fix AP mode for QCA6390
- net: l2tp: reduce log level of messages in receive path, add counter
instead
- gpiolib: acpi: Add ACPI_GPIO_QUIRK_ABSOLUTE_NUMBER quirk
- gpiolib: acpi: Allow to find GpioInt() resource by name and index
- can: skb: can_skb_set_owner(): fix ref counting if socket was closed
before
setting skb ownership
- gpio: pca953x: Set IRQ type when handle Intel Galileo Gen 2
- can: flexcan: assert FRZ bit in flexcan_chip_freeze()
- can: flexcan: enable RX FIFO after FRZ/HALT valid
- can: flexcan: invoke flexcan_chip_freeze() to enter freeze mode
- can: tcan4x5x: tcan4x5x_init(): fix initialization - clear MRAM before
entering Normal Mode
- tcp: Fix sign comparison bug in getsockopt(TCP_ZEROCOPY_RECEIVE)
- tcp: add sanity tests to TCP_QUEUE_SEQ
- netfilter: nf_nat: undo erroneous tcp edemux lookup
- netfilter: x_tables: gpf inside xt_find_revision()
- net: always use icmp{,v6}_ndo_send from ndo_start_xmit
- net: phy: fix save wrong speed and duplex problem if autoneg is on
- selftests/bpf: Use the last page in test_snprintf_btf on s390
- selftests/bpf: No need to drop the packet when there is no geneve opt
- selftests/bpf: Mask bpf_csum_diff() return value to 16 bits in
test_verifier
- samples, bpf: Add missing munmap in xdpsock
- libbpf: Clear map_info before each bpf_obj_get_info_by_fd
- ibmvnic: Fix possibly uninitialized old_num_tx_queues variable warning.
- ibmvnic: always store valid MAC address
- ibmvnic: remove excessive irqsave
- mt76: dma: do not report truncated frames to mac80211
- gpio: fix gpio-device list corruption
- mount: fix mounting of detached mounts onto targets that reside on shared
mounts
- cifs: fix credit accounting for extra channel
[Kernel-packages] [Bug 1919973] Re: Enable CONFIG_GPIO_CDEV_V1
This bug was fixed in the package linux-raspi - 5.11.0-1004.4
---
linux-raspi (5.11.0-1004.4) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1004.4 -proposed tracker (LP: #1920139)
* Enable CONFIG_GPIO_CDEV_V1 (LP: #1919973)
- [Config] raspi: Set GPIO_CDEV_V1=y
* hirsute/linux-raspi: Upstream raspberrypi patchset 2021-03-16 (LP: #1919319)
- media: i2c: imx477: Remove auto frame length adjusting
- media: i2c: imx477: Add very long exposure control to the driver
- media: i2c: imx290: Fix up exposure calcuations and ranges
- media: i2c: imx290: Handle exposure correctly when vblank changes
- DAC overlays (#4154)
- configs: Change CONFIG_BLK_DEV_NVME=y for 2711
- media: i2c: imx477: Fix crop height for 2028x1080 mode
- media: i2c: imx477: Replace existing 1012x760 mode
- media: i2c: imx477: Remove internal v4l2_mbus_framefmt from the state
- media: i2c: imx477: Remove unused function parameter
- overlays: i2c-rtc: Add the Dallas DS1340
- overlays: Update the upstream overlay
- Revert "Bluetooth: Always request for user confirmation for Just Works (LE
SC)"
- Revert "Bluetooth: Always request for user confirmation for Just Works"
- media: bcm2835-unicam: Fix bug in buffer swapping logic
- Assign crypto aliases to different AES implementation modules
- overlays: Improve the i2c-rtc,i2c_csi_dsi option
- configs: Add CONFIG_RTS_HCTOSYS=y
- overlays: Add pcie-32bit-dma overlay
- [Config] raspi: updateconfigs after update to rpi-5.11.y (2021-03-16)
* Miscellaneous Ubuntu changes
- [Config] raspi: updateconfigs after rebase to Ubuntu-5.11.0-13.14
- [Packaging] raspi: remove dh-systemd build dependency
- [Packaging] raspi: Drop removed modules from the ABI
- [Packaging] raspi: Remove debian.raspi/d-i
- [Packaging] raspi: Remove the temporary build hook
- [Packaging] raspi: Remove disable_d_i from the build rules
- [Packaging] raspi: Fix vertical alignment of build rules
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
- bpf: Fix off-by-one for area size in creating mask to left
[ Ubuntu: 5.11.0-12.13 ]
* hirsute/linux: 5.11.0-12.13 -proposed tracker (LP: #1918148)
* Hirsute update: v5.11.7 upstream stable release (LP: #1919492)
- uapi: nfnetlink_cthelper.h: fix userspace compilation error
- powerpc/603: Fix protection of user pages mapped with PROT_NONE
- powerpc/perf: Fix handling of privilege level checks in perf interrupt
context
- powerpc/pseries: Don't enforce MSI affinity with kdump
- crypto: mips/poly1305 - enable for all MIPS processors
- mptcp: fix length of ADD_ADDR with port sub-option
- ath9k: fix transmitting to stations in dynamic SMPS mode
- net: Fix gro aggregation for udp encaps with zero csum
- net: check if protocol extracted by virtio_net_hdr_set_proto is correct
- net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0
- ath11k: fix AP mode for QCA6390
- net: l2tp: reduce log level of messages in receive path, add counter
instead
- gpiolib: acpi: Add ACPI_GPIO_QUIRK_ABSOLUTE_NUMBER quirk
- gpiolib: acpi: Allow to find GpioInt() resource by name and index
- can: skb: can_skb_set_owner(): fix ref counting if socket was closed
before
setting skb ownership
- gpio: pca953x: Set IRQ type when handle Intel Galileo Gen 2
- can: flexcan: assert FRZ bit in flexcan_chip_freeze()
- can: flexcan: enable RX FIFO after FRZ/HALT valid
- can: flexcan: invoke flexcan_chip_freeze() to enter freeze mode
- can: tcan4x5x: tcan4x5x_init(): fix initialization - clear MRAM before
entering Normal Mode
- tcp: Fix sign comparison bug in getsockopt(TCP_ZEROCOPY_RECEIVE)
- tcp: add sanity tests to TCP_QUEUE_SEQ
- netfilter: nf_nat: undo erroneous tcp edemux lookup
- netfilter: x_tables: gpf inside xt_find_revision()
- net: always use icmp{,v6}_ndo_send from ndo_start_xmit
- net: phy: fix save wrong speed and duplex problem if autoneg is on
- selftests/bpf: Use the last page in test_snprintf_btf on s390
- selftests/bpf: No need to drop the packet when there is no geneve opt
- selftests/bpf: Mask bpf_csum_diff() return value to 16 bits in
test_verifier
- samples, bpf: Add missing munmap in xdpsock
- libbpf: Clear map_info before each bpf_obj_get_info_by_fd
- ibmvnic: Fix possibly uninitialized old_num_tx_queues variable warning.
- ibmvnic: always store valid MAC address
- ibmvnic: remove excessive irqsave
- mt76: dma: do not report truncated frames to mac80211
- gpio: fix gpio-device list corruption
- mount: fix mounting of detached mounts onto targets that reside on shared
mounts
- cifs: fix credit accounting for extra channel
[Kernel-packages] [Bug 1921995] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482736/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482733/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482731/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482735/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1921995] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482741/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482738/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1921995] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482739/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1921995] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482734/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1921995] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482737/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482732/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1921995] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482740/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482730/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482729/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1921995] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482728/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482727/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1921995] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482726/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482725/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482724/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1921995] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1921995/+attachment/5482723/+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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1921995] Re: hirsute kernels 5.11 do not boot on AMD STONEY hardware
yes it boots with iommu=soft ** Description changed: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu61 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: eugene 1877 F pulseaudio + /dev/snd/controlC0: eugene 1877 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2020-11-20 (130 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: ASUSTeK COMPUTER INC. X505BA + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft + ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-13-generic N/A + linux-backports-modules-5.11.0-13-generic N/A + linux-firmware 1.195 + Tags: hirsute wayland-session + Uname: Linux 5.11.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/02/2020 + dmi.bios.release: 5.12 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X505BA.317 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X505BA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: VivoBook + dmi.product.name: X505BA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Confirmed Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1922042] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482714/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482713/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482712/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] Re: Sync ath11k driver with Hirsute/mainline
WIP: https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1922042/sync-ath11k-driver/oem-5.10 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1922042 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482718/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482719/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482720/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482721/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482715/+files/ProcInterrupts.txt ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482717/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482716/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482711/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482710/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922042] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1922042/+attachment/5482709/+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/1922042 Title: Sync ath11k driver with Hirsute/mainline Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Bug description: In bug 1879633, patchset that just works on oem-5.10 were merged with around 20 Ubuntu sauced patches. While ath11k is still under active development, many of those have been revised and accepted in upstream kernel. There should be a tracker bug for this. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 3293 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1039-oem root=UUID=1879dff8-eec0-43aa-bc90-1a07312ff1c1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1039.43-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1039-oem N/A linux-backports-modules-5.6.0-1039-oem N/A linux-firmware 1.187.7 Tags: focal Uname: Linux 5.6.0-1039-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd12/10/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
