[Kernel-packages] [Bug 1809206] Re: Amd ACPI Error
Jeffrey, Please attach the acpidump to https://bugzilla.kernel.org/show_bug.cgi?id=201981, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809206 Title: Amd ACPI Error Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Hi Hp Laptop Amd A10 9600p Ubuntu 18.10 Kernel: all kernel acpi error mesg | grep Error [3.546921] RAS: Correctable Errors collector initialized. [9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979438] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979872] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.989318] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990274] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990646] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990682] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1809206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912773] 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 1912773
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/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
display not working, cpu/agpu performance dropped considerably
Status in amd:
New
Status in Linux Firmware:
New
Status in Mutter:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
After a recent update, I now have a system that can no longer play
audio (via HDMI), my second monitor (DVI) is no longer being picked
up, and CPU/AGPU usage has lost a lot of performance (OBS is basically
unusable at this point).
Whatever has happened with the recent updates has caused the AMD
drivers (presumably?) to not work correctly - because it is an AMD
Ryzen 5 3400g (with no dedicated graphics card).
1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu
```
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
```
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Not sure which package would be the cause, however these were the
version that were working prior to the update:
```
libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3
mutter-common=3.36.6-1ubuntu0.20.04.2
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70
mutter=3.36.6-1ubuntu0.20.04.2
```
This list was generated with the command:
`awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`
3) What you expected to happen
Sound and video working via HDMI on primary monitor, second monitor
displaying (extended) video via DVI. CPU and AGPU being able to render
via OBS.
4) What happened instead
No sound. No second display. Any CPU or AGPU tasks running slower than
normal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: hazrpg 3344 F pulseaudio
/dev/snd/controlC2: hazrpg 3344 F pulseaudio
/dev/snd/controlC0: hazrpg 3344 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 22 11:51:14 2021
InstallationDate: Installed on 2020-05-22 (244 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio
Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by
[Kernel-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mesa (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912773] Re: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
display not working, cpu/agpu performance dropped considerably
Status in amd:
New
Status in Linux Firmware:
New
Status in Mutter:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
After a recent update, I now have a system that can no longer play
audio (via HDMI), my second monitor (DVI) is no longer being picked
up, and CPU/AGPU usage has lost a lot of performance (OBS is basically
unusable at this point).
Whatever has happened with the recent updates has caused the AMD
drivers (presumably?) to not work correctly - because it is an AMD
Ryzen 5 3400g (with no dedicated graphics card).
1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu
```
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
```
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Not sure which package would be the cause, however these were the
version that were working prior to the update:
```
libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3
mutter-common=3.36.6-1ubuntu0.20.04.2
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70
mutter=3.36.6-1ubuntu0.20.04.2
```
This list was generated with the command:
`awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`
3) What you expected to happen
Sound and video working via HDMI on primary monitor, second monitor
displaying (extended) video via DVI. CPU and AGPU being able to render
via OBS.
4) What happened instead
No sound. No second display. Any CPU or AGPU tasks running slower than
normal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: hazrpg 3344 F pulseaudio
/dev/snd/controlC2: hazrpg 3344 F pulseaudio
/dev/snd/controlC0: hazrpg 3344 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 22 11:51:14 2021
InstallationDate: Installed on 2020-05-22 (244 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio
Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd09/18/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
[Kernel-packages] [Bug 1912773] [NEW] [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably
You have been subscribed to a public bug:
After a recent update, I now have a system that can no longer play audio
(via HDMI), my second monitor (DVI) is no longer being picked up, and
CPU/AGPU usage has lost a lot of performance (OBS is basically unusable
at this point).
Whatever has happened with the recent updates has caused the AMD drivers
(presumably?) to not work correctly - because it is an AMD Ryzen 5 3400g
(with no dedicated graphics card).
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
```
$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
```
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Not sure which package would be the cause, however these were the
version that were working prior to the update:
```
libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3
mutter-common=3.36.6-1ubuntu0.20.04.2
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70
mutter=3.36.6-1ubuntu0.20.04.2
```
This list was generated with the command:
`awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`
3) What you expected to happen
Sound and video working via HDMI on primary monitor, second monitor
displaying (extended) video via DVI. CPU and AGPU being able to render
via OBS.
4) What happened instead
No sound. No second display. Any CPU or AGPU tasks running slower than
normal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: hazrpg 3344 F pulseaudio
/dev/snd/controlC2: hazrpg 3344 F pulseaudio
/dev/snd/controlC0: hazrpg 3344 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 22 11:51:14 2021
InstallationDate: Installed on 2020-05-22 (244 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd09/18/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C52
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: amd
Importance: Undecided
Status: New
** Affects: linux-firmware
Importance: Undecided
Status: New
** Affects: mutter
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not
working, cpu/agpu performance dropped
[Kernel-packages] [Bug 1909790] Re: wireless mouse middle click missing on new 20.04
Can you please install libinput-tools, and run `sudo libinput debug- events`, then check if there's any event for the middle click. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909790 Title: wireless mouse middle click missing on new 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Long time Ubuntu user. Fresh install of 20.04 on an older NUC. Everything works fine except the Logitech wireless mouse - M185 came in keyboard/mouse package. Actually the mouse works fine except there is no middle click. Middle wheel scrolls fine. LSUSB recognizes the receiver: Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver xinput test only recognizes button 1 and 3 $ xinput test 12 button press 1 button release 1 button press 3 button release 3 I installed Solaar but that didn't help, although I did like the Solaar battery gauge. The Ubuntu Mouse & Touchpad Settings doesn't show a middle button either. I miss my middle click paste. :-( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcw 1410 F pulseaudio /dev/snd/controlC0: marcw 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 31 20:10:46 2020 InstallationDate: Installed on 2020-12-28 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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.4.0-58-generic root=UUID=569d8094-8fe3-4d4e-b814-99989559626a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0072.2019.1001.1636 dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-506 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0072.2019.1001.1636:bd10/01/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-506:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903790] Re: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc4/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903790 Title: SSD and Bluetooth conflict (Bluetooth AR3011 doesn't work) Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1951 F pulseaudio /dev/snd/controlC0: navycat1951 F pulseaudio /dev/snd/controlC1: navycat1951 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 05:26:13 2020 InstallationDate: Installed on 2020-11-01 (9 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909840] Re: SDXC card reader not working properly
Which driver provides the exFAT functionality? FUSE driver or in-kernel 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/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Confirmed Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bruno 1008 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-01 (33 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81KT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN22WW X64 dmi.board.asset.tag: No Asset Tag dmi.board.name:
[Kernel-packages] [Bug 1908847] Re: [Realtek ALC298] No sound from internal speakers
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc4/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908847 Title: [Realtek ALC298] No sound from internal speakers Status in linux package in Ubuntu: Incomplete Bug description: I've tried several ways to solve this problem but still have a problem. 1) alsa-info http://alsa-project.org/db/?f=7ba6e11f4fa1cfad5518a32bfcaaba5f5aff5aff 2) RtHDDumpo I attached output file. I found 'write I2C' sequence in it. ( to enable MAX98390 ) -- I tried the test below 1) options snd-intel-dspcfg dsp_driver=1 and 3 : same results, no sound 2) options snd-hda-intel dmic_detect=0 and options snd-hda-intel models : same results, no sound -- I think need a patch to support max98390. Could you give me some advice ? -- additional information 1) versions Ubuntu 5.8.0-31.33-generic 5.8.17 Description: Ubuntu 20.10 Release: 20.10 2) lspci 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsystem: LG Electronics, Inc. 11th Gen Core Processor Host Bridge/DRAM Registers [1854:0402] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. UHD Graphics [1854:0402] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Address: fee00018 Data: Masking: Pending: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV) IOVCap: Migration-, Interrupt Message Number: 000 IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy- IOVSta: Migration- Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00 VF offset: 1, stride: 1, Device ID: 9a49 Supported Page Size: 0553, System Page Size: 0001 Region 0: Memory at 00401000 (64-bit, non-prefetchable) Region 2: Memory at 00402000 (64-bit, prefetchable) VF Migration: offset: , BIR: 0 Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a03] (rev 01) Subsystem: LG Electronics, Inc. Device [1854:0402] Control: I/O- Mem+ BusMaster- SpecCycle-
[Kernel-packages] [Bug 1908919] Re: Touchpad is not present in input devices
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc4/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908919 Title: Touchpad is not present in input devices Status in linux package in Ubuntu: Incomplete Bug description: Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC) First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04. Tested with both available kernels : ii linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1 amd64Signed kernel image generic ii linux-image-5.4.0-58-generic 5.4.0-58.64 amd64Signed kernel image generic See attached file. Bug summited with the help of https://wiki.ubuntu.com/DebuggingTouchpadDetection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rgo1450 F pulseaudio /dev/snd/controlC1: rgo1450 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 17:21:08 2020 InstallationDate: Installed on 2020-12-21 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd07/22/2020:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1X2T6EA#ABF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909115] Re: ASUS Z9PE-D8 WS needs custom DSDT fix to properly shutdown (random)
A took a quick look and _PTS simply sets some variables for EC. So
please contact Asus, because we don't know what EC expects.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1909115
Title:
ASUS Z9PE-D8 WS needs custom DSDT fix to properly shutdown (random)
Status in linux package in Ubuntu:
Confirmed
Bug description:
Running Ubuntu server 20.04.1 LTS (CLI only), after switching from
other distro (Manjaro and Artix) which present the same issue;
basically I tried the debian based, arch based and systemd free
distro.
Issue description: issuing the command "shutdown -h now" or "poweroff -f"
doesn't shutdown the system properly, the system hangs is S5.
This doesn't happen all the time, but randomly, let's say in about 30% of
cases.
This happens not only with an installed system but also with the bootable usb
installer.
How to replicate: I really don't know, it seems very random, without a
pattern.
Motherboard: ASUS Z9PE-D8 WS with bios v. 5802 (dated 2015/10/15)
CPU: 2x intel Xeon E5-2687w (SR0KG)
After trying different proposed solutions for the "hanging at
shutdown" issue (mostly by enabling/disabling things in grub and
different kernels down to 4.9) I found out that only a DSDT fix solves
the issue, and in particular in the _PTS method.
Basically this is the original part of the extracted DSDT:
Method (_PTS, 1, NotSerialized) // _PTS: Prepare To Sleep
{
If (((Arg0 == 0x04) && (OSFL () == 0x02)))
{
Sleep (0x0BB8)
}
PTS (Arg0)
DBG8 = Arg0
WAKP [Zero] = Zero
WAKP [One] = Zero
WSSB = ASSB /* \ASSB */
WOTB = AOTB /* \AOTB */
WAXB = AAXB /* \AAXB */
ASSB = Arg0
AOTB = OSFL ()
AAXB = Zero
\_SB.SLPS = One
}
The fix (or better call it workaround) includes a "do nothing" if Arg0 is
0x05 (state S5):
Method (_PTS, 1, NotSerialized)
{
If (LEqual (Arg0, 0x05)) {}
Else
{
Store (Arg0, DBG8)
If (LAnd (LEqual (Arg0, 0x04), LEqual (OSFL (), 0x02)))
{
Sleep (0x0BB8)
}
PTS (Arg0)
Store (Zero, Index (WAKP, Zero))
Store (Zero, Index (WAKP, One))
Store (ASSB, WSSB)
Store (AOTB, WOTB)
Store (AAXB, WAXB)
Store (Arg0, ASSB)
Store (OSFL (), AOTB)
Store (Zero, AAXB)
Store (One, \_SB.SLPS)
}
}
I really don't know why without injecting the DSDT fix it hangs randomly at
shutdown.
I reported the issue to the kernel bugtracker too, but it seems there's not
much movement there :D
I hope this can be fixed kernel side:
For reference, this is the link to the kernel bugtracker:
https://bugzilla.kernel.org/show_bug.cgi?id=210689
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909115/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909117] Re: Repeated kernel OOPS in dentry_unlink_inode
Can you update the system and test kernel 5.4.0-65.73? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909117 Title: Repeated kernel OOPS in dentry_unlink_inode Status in linux package in Ubuntu: Confirmed Bug description: Happened twice last night, precisely one hour apart root@nas:/var/log# grep "Dec 23 0[23]:13:" /var/log/syslog* /var/log/syslog:Dec 23 02:13:01 nas CRON[156065]: (root) CMD (date >> /var/log/sensors.log; /usr/bin/sensors -f >> /var/log/sensors.log) /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404588] BUG: kernel NULL pointer dereference, address: 0408 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404607] #PF: supervisor write access in kernel mode /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404616] #PF: error_code(0x0002) - not-present page /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404626] PGD 0 P4D 0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404632] Oops: 0002 [#1] SMP NOPTI /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404640] CPU: 6 PID: 130 Comm: kswapd0 Not tainted 5.4.0-58-generic #64-Ubuntu /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404652] Hardware name: Gigabyte Technology Co., Ltd. Z390 GAMING X/Z390 GAMING X-CF, BIOS F6 12/04/2018 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404671] RIP: 0010:dentry_unlink_inode+0x56/0x110 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404680] Code: 00 08 00 74 08 65 48 ff 05 6f ee 32 6f 49 8b 84 24 b8 00 00 00 48 85 c0 74 2c 49 8b 94 24 b0 00 00 00 48 89 10 48 85 d2 74 04 <48> 89 42 08 49 c7 84 24 b0 00 00 00 00 00 00 00 49 c7 84 24 b8 00 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404708] RSP: 0018:b70540327b18 EFLAGS: 00010206 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404718] RAX: 9131de578680 RBX: 9134d3266c00 RCX: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404732] RDX: 0400 RSI: 91395d9c9fa8 RDI: 9134d32666c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404746] RBP: b70540327b28 R08: 02ad R09: b70540327cb0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404760] R10: R11: 0010 R12: 9134d32666c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404772] R13: 9131de578548 R14: 9134d32666c0 R15: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404786] FS: () GS:91395e38() knlGS: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404800] CS: 0010 DS: ES: CR0: 80050033 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404810] CR2: 0408 CR3: 000117e0a006 CR4: 003606e0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404822] DR0: DR1: DR2: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404837] DR3: DR6: fffe0ff0 DR7: 0400 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404851] Call Trace: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404858] __dentry_kill+0xdf/0x180 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404866] shrink_dentry_list+0x4e/0xc0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404874] prune_dcache_sb+0x5c/0x80 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404882] super_cache_scan+0xfe/0x1b0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404891] do_shrink_slab+0x150/0x2a0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404900] shrink_slab+0x20c/0x2a0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404908] shrink_node+0xd3/0x410 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404916] balance_pgdat+0x319/0x590 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404924] kswapd+0x1f8/0x3c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404932] ? wait_woken+0x80/0x80 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404940] kthread+0x104/0x140 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404946] ? balance_pgdat+0x590/0x590 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404954] ? kthread_park+0x90/0x90 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404963] ret_from_fork+0x35/0x40 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.405418] Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport xt_MASQUERADE xt_nat xt_dscp xt_DSCP xt_hashlimit xt_length xt_tcpudp xt_state xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter bpfilter binfmt_misc nls_iso8859_1 dm_multipath si2157 scsi_dh_rdac scsi_dh_emc scsi_dh_alua lgdt3306a cx231xx_dvb dvb_core cx231xx_alsa cx25840 cx231xx videobuf_vmalloc tveeprom cx2341x videobuf_core i2c_mux videodev mc
[Kernel-packages] [Bug 1902566] Re: touchpad
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902566 Title: touchpad Status in linux package in Ubuntu: Expired Bug description: touchpad not working cant hover the pointer ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: memet 2590 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 3 01:32:41 2020 InstallationDate: Installed on 2020-11-01 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X453SA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=id_ID.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=2859945f-1ea2-4e9e-9e0b-efb2e6194978 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X453SA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X453SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX453SA.205:bd10/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX453SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX453SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X453SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902421] Re: iwl3945: Low throughput on focal / Linux 5.4
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902421 Title: iwl3945: Low throughput on focal / Linux 5.4 Status in linux package in Ubuntu: Expired Bug description: Hello out their, I seem to be having some issues related WiFi on my Xubuntu 20.04 install. My main issue is that my WiFi connection on my Xubuntu install versus my Windows 7 Starter install is a lot slower. Currently the highest speed I have gotten on Xubuntu has been 10mbps, I was getting around 30-50mbps on Windows. I tried editing the default-wifi-powersave- on.conf and setting it to 2 because that seemed to be a commonly recommended answer, but doesn't seem to be helping. I have also tried using "Additional Drivers" to try and see if their was another driver available to no avail. A user on the Xubuntu IRC chat (tomreyn) suggested a few things and we collected this info about my wireless chipset, I hope it helps: https://paste.ubuntu.com/p/DbhNsN9JsD/ Thanks for any help in this matter! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mitch 980 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Nov 1 04:46:44 2020 InstallationDate: Installed on 2020-09-25 (36 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Gateway MT6821 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e9fce119-f720-47f8-a508-c4cb1b9e8bde ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 77.09 dmi.board.vendor: Gateway dmi.board.version: 77.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr77.09:bd11/27/2006:svnGateway:pnMT6821:pvr3408141R:rvnGateway:rn:rvr77.09:cvnGateway:ct8:cvrRev.1: dmi.product.name: MT6821 dmi.product.version: 3408141R dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903473] Re: Bluetooth does not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903473 Title: Bluetooth does not work Status in linux package in Ubuntu: Expired Bug description: [625347.017671] usb 1-1.4: Product: Bluetooth Radio [625347.039793] Bluetooth: Core ver 2.22 [625347.039819] Bluetooth: HCI device and connection manager initialized [625347.039822] Bluetooth: HCI socket layer initialized [625347.039824] Bluetooth: L2CAP socket layer initialized [625347.039829] Bluetooth: SCO socket layer initialized [625347.047141] Bluetooth: hci0: rtl: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [625347.047142] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_config.bin [625347.047360] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_config.bin failed with error -2 [625347.047362] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_fw.bin [625347.049134] Bluetooth: hci0: rom_version status=0 version=1 [625347.049140] Bluetooth: hci0: cfg_sz 0, total size 20204 [625347.147059] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [625347.147060] Bluetooth: BNEP filters: protocol multicast [625347.147062] Bluetooth: BNEP socket layer initialized [625349.156276] Bluetooth: hci0: command 0xfc20 tx timeout [625357.380082] Bluetooth: hci0: download fw command failed (-110) [625562.330711] Bluetooth: RFCOMM TTY layer initialized [625562.330717] Bluetooth: RFCOMM socket layer initialized [625562.330722] Bluetooth: RFCOMM ver 1.11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-122-generic 4.15.0-122.124 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 2276 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 18:56:36 2020 InstallationDate: Installed on 2018-12-08 (702 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Z220 SFF Workstation ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=7af66fb9-8488-4a45-a134-214f705e35d5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-122-generic N/A linux-backports-modules-4.15.0-122-generic N/A linux-firmware 1.173.19 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K51 v01.80 dmi.board.name: 1791 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK51v01.80:bd10/21/2014:svnHewlett-Packard:pnHPZ220SFFWorkstation:pvr:rvnHewlett-Packard:rn1791:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z220 SFF Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I have also had the boot problem disappear, return, and disappear again. On 1/22/21 11:12 AM, Wolf Pichler wrote: > I have these installed: > > dpkg -l | grep "linux\-[a-z]*\-" > > rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46 > ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 > ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1 > ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1 > > I tried as Charles Green said: Switching to tty2 and then back to tty1 causes > the boot to complete. > (Ctrl+Alt+F2, Ctrl+Alt+F1) > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909840] Re: SDXC card reader not working properly
Tested my 8GB Micro SDHC recently formatted with exFAT. All files transfered flawlessly, even with the Partition Type NTFS/exFAT/HPFS and exFAT content description in gnome-disks, and, most important (at least i think so), no "cannot verify signal voltage switch" in dmesg. By dmesg i got: [ 101.565119] mmc1: new high speed SDHC card at address e624 [ 101.570865] mmcblk1: mmc1:e624 SU08G 7.40 GiB [ 101.587376] mmcblk1: p1 but the problem persists with the SDXC card reader. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Confirmed Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bruno 1008 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-01 (33 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81KT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A
[Kernel-packages] [Bug 1872504] 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 1872504 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/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in linux package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
I added the linux source package to this bug because I've heard this commit addresses the issue: https://github.com/gregkh/linux/commit/099340d3e758cca06a82bf5dcff8b9a8acbdcb0a Thanks ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in linux package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
I upgraded my video card to a newer NVIDIA 1660 Ti. An expensive way to fix a bug :). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Incomplete Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912708] Re: CONFIG_RANDOMIZE_BASE on ppc64el
Steve, I am adding this to our workflow to address -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912708 Title: CONFIG_RANDOMIZE_BASE on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hello, it looks like CONFIG_RANDOMIZE_BASE is not set in our ppc64el kernel configurations, based on running this in an rsync clone of kernel.ubuntu.com::kernel-ppa-config/ : grep CONFIG_RANDOMIZE_BASE $(find . -iname '*ppc*' | grep /linux/) This returns no hits -- not even for a disabled feature -- which surprised me a bit. This webpage suggests power should have this kernel configuration available after 5.5: https://cateee.net/lkddb/web- lkddb/RANDOMIZE_BASE.html Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash
** Changed in: linux-azure (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1882623 Title: VM enter into hung status after triggering a crash Status in linux-azure package in Ubuntu: In Progress Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard DS2 v2 Install kexec-tools kdump-tools makedumpfile, configure boot kernel parameter crashkernel=512M Run sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools and sed -i 's/LOAD_KEXEC=true/LOAD_KEXEC=false/g' /etc/default/kexec Reboot VM, make sure crash kernel memory reserved successfully Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c > /proc/sysrq-trigger, VM will reboot automatically and after reboot, check crash dump is generated under /var/crash Install linux-azure kernel Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c > /proc/sysrq-trigger, VM entered into a hung status. Attach whole serial console [ 65.452007] INFO: rcu_sched detected stalls on CPUs/tasks: [ 65.456004] 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0 [ 65.456004] (detected by 0, t=15002 jiffies, g=707, c=706, q=8457) [ 65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 [ 360.020026] INFO: rcu_sched detected stalls on CPUs/tasks: [ 360.024015] 1-...!: (10 GPs behind) idle=b34/0/0 softirq=1/1 fqs=1 [ 360.024015] (detected by 0, t=15002 jiffies, g=717, c=716, q=6429) [ 360.024015] rcu_sched kthread starved for 15000 jiffies! g717 c716 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 [ 420.048010] INFO: rcu_sched detected stalls on CPUs/tasks: [ 420.052006] 1-...!: (0 ticks this GP) idle=f94/0/0 softirq=1/1 fqs=0 [ 420.052006] (detected by 0, t=15002 jiffies, g=718, c=717, q=6429) [ 420.052006] rcu_sched kthread starved for 15002 jiffies! g718 c717 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels
Thanks for the report and fix Stefan! Although the LP is a bit old, I
think worth to mention here the patches that fix boths issues (the
"Unknown type (Reserved) while parsing" message and the "ELF core
(kcore) parse failed" bug) - both present in kexec-tools as fixes due to
Linux kernel modifications:
ed15ba1b ("build_mem_phdrs(): check if p_paddr is invalid")
fab91841 ("Handle additional e820 memmap type strings")
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713940
Title:
kexec-tools 2.0.14 fails to load 4.12+ crash kernels
Status in kexec-tools package in Ubuntu:
Fix Released
Bug description:
Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
because ELF core parsing fails with errors like:
Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load /var/lib/kdump/vmlinuz
The issue is fixed upstream in kexec-tools 2.0.15 (Debian is still at
2.0.14)
The complete changes list between 2.0.14 and 2.0.15 shows mostly bug
fixes and in fact all additional patches in debian/patches which are
Ubuntu delta, have moved into upstream 2.0.15. So we could drop all
those while moving to the new version.
* ppc64: Reduce number of ELF LOAD segments
* kexec: Increase the upper limit for RAM segments
* alpha: add missing __NR_kexec_load definition
* kexec: implemented XEN KEXEC STATUS to determine if an image is loaded
* kexec: Remove redundant space from help message
* purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe
* kexec: Add option to get crash kernel region size
* crashdump/arm: Add get_crash_kernel_load_range() function
* crashdump/arm64: Add get_crash_kernel_load_range() function
* crashdump/cris: Add get_crash_kernel_load_range() function
* crashdump/ia64: Add get_crash_kernel_load_range() function
* crashdump/m68k: Add get_crash_kernel_load_range() function
* crashdump/mips: Add get_crash_kernel_load_range() function
* crashdump/ppc: Add get_crash_kernel_load_range() function
* crashdump/ppc64: Add get_crash_kernel_load_range() function
* crashdump/s390: Add get_crash_kernel_load_range() function
* crashdump/sh: Add get_crash_kernel_load_range() function
* gitignore: add two generated files in purgatory
* Only print debug message when failed to serach for kernel symbol from
/proc/kallsyms
* build_mem_phdrs(): check if p_paddr is invalid
* uImage: fix realloc() pointer confusion
* uImage: Fix uImage_load() for little-endian machines
* uImage: Add new IH_ARCH_xxx definitions
* uImage: use 'char *' instead of 'unsigned char *' for uImage_load()
* uImage: use 'char *' instead of 'unsigned char *' for uImage_probe()
* arm64: add uImage support
* vmcore-dmesg: Define _GNU_SOURCE
* Don't use %L width specifier with integer values
* x86/x86_64: Fix format warning with die()
* ppc: Fix format warning with die()
* crashdump: Remove stray get_crashkernel_region() declaration
* x86: Support large number of memory ranges
* Fix broken Xen support in configure.ac
* kexec: extend the semantics of kexec_iomem_for_each_line
* kexec: generalize and rename get_kernel_stext_sym()
* arm64: identify PHYS_OFFSET correctly
* arm64: change return values on error to negative
* arm64: kdump: identify memory regions
* arm64: kdump: add elf core header segment
* arm64: kdump: set up kernel image segment
* arm64: kdump: set up other segments
* arm64: kdump: add DT properties to crash dump kernel's dtb
* arm64: kdump: Add support for binary image files
* Handle additional e820 memmap type strings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713940/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909840] Re: SDXC card reader not working properly
it uses exFAT and in gnome-disks the Partition Type is NTFS/exFAT/HPFS and the contents are exFAT. i found weird that partition type shows NTFS/exFAT/HPFS and the contents exFAT. But who knows? (i am not very proficient in computing). obs: i did format it as exFAT in windows 10 in another machine with default setting in allocation unit size. I was able to use it normally with any windows machine i tested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Confirmed Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bruno 1008 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-01 (33 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81KT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname:
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Maybe it is possible to ask them directly : http://www.emc.com.tw/emc/en/Product/Solution/TouchpadSolutions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
@hydrogencl > I have reported this issue to ASUS support Thank you! I also requested tech support for the drivers for ExpertBook B9. Today I got the reply: > In regards to drivers for Ubuntu Linux 20.10, you will be required to contact Linux directly for drivers and tools for the fingerprint sensor and Numpad as we do not support Linux. So they are hoping that Linux developers will write drivers themselves :D I asked them to request the drivers or specs from Elantech, let's see what they say next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870837] Re: BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel
Also experiencing this issue. Took a long time to google this thread. Really hope for a fix in recent kernels. Please, let me know if any diagnostic/debug information or testing is required, I'm ready to assist. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870837 Title: BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907160] Re: intel-hid is not loaded on new Intel platform
** Description changed: [Impact] - intel-hid, used to handle BIOS events, is not loaded on new intel - rocket lake platforms because the existing hardware ids "INT33D5" and - "INTC1051" aren't used in BIOS. + intel-hid is not loaded on Intel Tiger Lake and Rocket Lake platforms because the existing + hardware ids "INT33D5" aren't used in BIOS. [Fix] - A new id "INTC1054" is added to intel-hid kernel driver. + New ids "INTC1051" and "INTC1054" are to be added to intel-hid kernel + driver. [Test Case] - This was tested on a rocket lake platform and intel-hid was loaded + This was tested on a Rocket Lake platform and intel-hid was loaded correctly as kernel log below: - [ 2.938964] input: Intel HID 5 button array as + [ 2.938964] input: Intel HID 5 button array as /devices/platform/INT1054:00/input/input11 [Where problems could occur] - None. + None. - An new ID was added for new platforms. Previous platforms will not be + New IDs were added for new platforms. Previous platforms will not be affected. ** Tags removed: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907160 Title: intel-hid is not loaded on new Intel platform Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Incomplete Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] intel-hid is not loaded on Intel Tiger Lake and Rocket Lake platforms because the existing hardware ids "INT33D5" aren't used in BIOS. [Fix] New ids "INTC1051" and "INTC1054" are to be added to intel-hid kernel driver. [Test Case] This was tested on a Rocket Lake platform and intel-hid was loaded correctly as kernel log below: [ 2.938964] input: Intel HID 5 button array as /devices/platform/INT1054:00/input/input11 [Where problems could occur] None. New IDs were added for new platforms. Previous platforms will not be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Any news on this driver?
--
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/1879633
Title:
Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification: oem-5.6]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
its prerequisite drivers.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
Tag ath11k-qca6390-bringup-202011301608 from ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
first stable milestone on the platform/device under development since
v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
in vanilla kernel v5.10-rc4 except those starting from commit
065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").
While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
in these components are also pulled.
Besides, tx encapsulation
https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
and a couple more inclusive of 6 GHz capability, BSS Color were also
pulled to satisfy API changes in mac80211/cfg80211.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
While this is going to bring massive changes to the kernel, as well as
shared wireless stack that is not only used by ath11k but also many
others, prebuilt kernel/firmware packages were deployed on platforms
with and without ath11k for regression tests, and so far the results are
positive.
[Where problems could occur]
ath11k and its relying parts have never been enabled in oem-5.6, so
changes to them should have little effect on most platforms. For
platforms equip QCA6390, this will be the first time they're probed and
enabled, and as the driver is still under polishing, there can be
regressions, performance lost, power consumption increase at this
moment.
Changes to wireless stack could also be an issue as this introduces
interface changes to the API, so maybe DKMS packages in the wild will be
affected.
== SRU for U/OEM-5.10 ==
[SRU Justification: U/OEM-5.10]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k
driver.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
25 additional fixes in ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
and firmware updates from mainline are required.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
[Where problems could occur]
There has been a lot patches landed in kernel since 5.7 devel cycle. The
last bits here has merge base with mainline at v5.10-rc4, and since then
only patches for ath11k itself has been committed.
== Original Bug Description ==
Qualcomm QCA6390 series not recognized due to the lack of ath11k
driver.
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1842 F pulseaudio
CasperMD5CheckResult: skip
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+X23
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-06-04 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
MP is open
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
Triaged
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the lack of hardware this test needs to be done by IBM.
[Regression Potential]
* There is a certain regression risk with this patch, since:
* The handling of 'scpdata' is changed, and with that the way how
kernel cmd-line parameters are extracted from the NVMe IPL
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
** Patch added: "debdiff (for LP1903984 LP1908371 LP1902179)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5455813/+files/debdiff_focal.diff
** Changed in: s390-tools (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
Triaged
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the lack of hardware this test needs to be
[Kernel-packages] [Bug 1902469] Re: drm/i915/dp_mst - System would hang during the boot up.
yeah...nevermind. I will look for support where I'm supposed to. :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902469 Title: drm/i915/dp_mst - System would hang during the boot up. Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] The machine connect with the external monitor on dock(Thunderbolt), Then system would hang during the boot-up. [Fix] The atomic check hooks must look up the encoder to be used with a connector from the connector's atomic state, and not assume that it's the connector's current attached encoder. The latter one can change under the atomic check func, or can be unset yet as in the case of MST connectors. [test] With the patch, The machine connect with the external monitor on dock(Thunderbolt), Then system boot up successfully. [Regression Potential] Low. This patch is also verified by others and is archived in the drmtip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub
test cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
We have this test since Focal.
This patch can be cherry-picked into all the affected kernels.
[Test]
Run this test with:
sudo ./udpgro.sh
And check its final return value with:
echo $?
If there is any failure, the return value should not be 0.
[Where problems could occur]
If this fix is incorrect it might affect the test execution, but it
should be fine as this is just affecting the test tool. Also, with
this patch, we are expecting to see this test case to fail until
bug 1908501 got fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1908499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909062 Title: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1909062 [Impact] For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will fail, due to these packets getting corrupted. Kubernetes uses IPIP tunnelled packets for internal DNS resolution, and this particular packet type is not supported for hardware tx checksum offload, and the packets end up corrupted when the qede driver attempts to checksum them. This only affects internal Kubernetes DNS, as regular DNS lookups to regular external domains will succeed, due to them not using IPIP packet types. [Fix] Marvell has developed a fix for the qede driver, which checks the packet type, and if it is IPPROTO_IPIP, then csum offloads are disabled for socket buffers of type IPIP. commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 Subject: qede: fix offload for IPIP tunnel packets Link: https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530 This commit landed in mainline in 5.11-rc3. The commit was accepted into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7. Note, this SRU isn't targeted for Bionic due to tx csum offload support only landing in 5.0 and onward, meaning the 4.15 kernel still works even without this patch. Because of this, Bionic can pick the patch up naturally from upstream stable. [Testcase] The system must have a QLogic QL41xxx series NIC fitted, and needs to be a part of a Kubernetes cluster. Firstly, get a list of all devices in the system: $ sudo ifconfig Next, set all devices down with: $ sudo ifconfig down Next, bring up the QLogic QL41xxx device: $ sudo ifconfig up Then, attempt to lookup an internal Kubernetes domain: $ nslookup Without the patch, the connection will time out: ;; connection timed out; no servers could be reached If we look at packet traces with tcpdump, we see it leaves the source, but never arrives at the destination. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test If you install it, then Kubernetes internal DNS lookups will succeed. [Where problems could occur] If a regression were to occur, then users of the qede driver would be affected. This is limited to those with QLogic QL41xxx series NICs. The patch explicitly checks for IPIP type packets, so only those particular packets would be affected. Since IPIP type packets are uncommon, it would not cause a total outage on regression, since most packets are not IPIP tunnelled. It could potentially cause problems for users who frequently handle VPN or Kubernetes internal DNS traffic. A workaround would be to use ethtool to disable tx csum offload for all packet types, or to revert to an older kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907421] Re: [UBUNTU 21.04] vfio: pass DMA availability information to userspace
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907421 Title: [UBUNTU 21.04] vfio: pass DMA availability information to userspace Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Description: vfio: pass DMA availability information to userspace Symptom: vfio-pci device on s390 enters error state Problem: Commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. However, lazy unmapping in s390 can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged, potentially the entire guest DMA space. This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device' Solution: The solution requires a change to both kernel and qemu - For the kernel, add the ability to provide the number of allowable DMA requests via the VFIO_IOMMU_GET_INFO ioctl. Reproduction: Put a vfio-pci device on s390 under I/O load Upstream-ID: a717072007e8aedd3f951726d8cf55454860b30d 7d6e1329652ed971d1b6e0e7bea66fba5044e271 Need also to be integrated into 20.10 and 20.04. OK, just to clarify we don't need to fix bionic for this one, but rather focal (20.04) and groovy (20.10). Furthermore, for 20.04, 20.10 and 21.04 ONLY commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a pre-req that is already present. __ SRU Justification: [Impact] * In case a vfio-pci device on s390x is under I/O load, vfio-pci device may end up in error state. * The commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. * However, lazy unmapping in s390x can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged - potentially the entire guest DMA space. * This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device'. * The solution requires a change to both kernel and qemu. * The kernel side of things is addressed by this SRU. * The fix adds the ability to provide the number of allowable DMA requests via VFIO_IOMMU_GET_INFO ioctl. * The actual fix comes with commit 7d6e1329652e, but another fix ccd59dce1a21 is needed to get it cleanly applied. [Fix] * ccd59dce1a21f473518bf273bdf5b182bab955b3 ccd59dce1a21 "vfio/type1: Refactor vfio_iommu_type1_ioctl()" * 7d6e1329652ed971d1b6e0e7bea66fba5044e271 7d6e1329652e "vfio iommu: Add dma available capability" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed. * PCIe adapters in place that provide vfio, like RoCE Express 2. * A KVM host needs to be setup and a KVM guest (use again 20.10) that uses vfio. * Generate I/O that flows through the vf and watch out for error like 'VFIO_MAP_DMA failed: No space left on device' in the log. [Regression Potential] * The first patch ccd59dce1a21 modifies the common code file drivers/vfio/vfio_iommu_type1.c quity significantly. * But the reason is not that it introduces a lot of new things, it's a refactoring patch. * Nevertheless if done in a bad way it can significantly harm the IO memory management of virtual function adapters. * In worst case it may break them entirely, instead of 'just' exeeding the entire DMA space. * Things could also go wrong while doing the mapping and unmapping of DMA, that may even have an impact beyond vf adapters - harming other DMA devices. * The handling of dirty pages is also touched and the ioctl itself - which is important to keep the control of the devices. * But as said before, it re-factoring work, it's upstream accepted since 5.9 and the provenance shows that many engineers had an eye on these changes. * The second patch 7d6e1329652e - that inclides the needed fix - comes with far less modifications. * It also tounches drivers/vfio/vfio_iommu_type1.c but in a way that it mainly add one new function (vfio_iommu_dma_avail_build_caps) and an add. if statement in vfio_iommu_type1_get_info. * That allows to provide the current allowable number of DMA mappings to the userspace via the IOMMU info chain, so that the userspace can take appropriate mitigation. * Potential problems here can be that the current allowable number of DMA mappings are wrong and in best case just mappings are wasted and in worst case there are more
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
** Merge proposal linked:
https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/396775
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the lack of hardware this test needs to be done by IBM.
[Regression Potential]
* There is a certain regression risk with this patch, since:
* The handling of
[Kernel-packages] [Bug 1902469] Re: drm/i915/dp_mst - System would hang during the boot up.
This is the closest match I could find to the problem I'm experiencing. Every Kernel update above 5.4.0-59-generic on Ubuntu 20.04.1 LTS on this Thinkpad T580 docked on the Thinkpad Ultra Docking Station causes the computer to freeze up either just before the login screen, on the login screen or shortly after successful login. If I take the machine off of the docking station, everything works fine. Docking and removing external monitor connections does not make it any better. Sorry if I'm not in compliance with this forum's practices. I'll go read-up on that and get in line ASAP. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902469 Title: drm/i915/dp_mst - System would hang during the boot up. Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] The machine connect with the external monitor on dock(Thunderbolt), Then system would hang during the boot-up. [Fix] The atomic check hooks must look up the encoder to be used with a connector from the connector's atomic state, and not assume that it's the connector's current attached encoder. The latter one can change under the atomic check func, or can be unset yet as in the case of MST connectors. [test] With the patch, The machine connect with the external monitor on dock(Thunderbolt), Then system boot up successfully. [Regression Potential] Low. This patch is also verified by others and is archived in the drmtip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
It seems that in at least 1 case, this condition arises with linux- modules-extra installed so my suggestion above may not help -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911848] Re: kvm: Windows 2k19 with Hyper-v role gets stuck on pending hypervisor requests on cascadelake based kvm hosts
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911848 Title: kvm: Windows 2k19 with Hyper-v role gets stuck on pending hypervisor requests on cascadelake based kvm hosts Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1911848 [Impact] On CascadeLake based KVM hosts, Windows Server 2k16 and 2k19 guests will fail to start once they have enabled the hyper-v role for nested virtualisation. The Windows Server guests will get stuck in the late stages of boot, before the graphical login screen appears, on Windows Server systems with the desktop environment installed. If you look at performance metrics for the guest, the CPU will appear to be stuck at 100%, and it never changes from 100%. The Windows Server guest is unresponsive. The KVM settings use Cascadelake-Server-noTSX virtual CPUs, with some very specific settings needed for nested virtualisation. See testcase section. If you use any other vcpu type, the problem does not reproduce. Known workarounds are to install the 5.8 HWE kernel, in which case the server will come up as expected. [Fix] The following commit fixes the issue, and landed in mainline 5.8-rc1: commit 8081ad06b68a728e676d3b08e9ab70ce4039747b Author: Sean Christopherson Date: Wed Apr 22 19:25:40 2020 -0700 Subject: KVM: x86: Set KVM_REQ_EVENT if run is canceled with req_immediate_exit set Link: https://github.com/torvalds/linux/commit/8081ad06b68a728e676d3b08e9ab70ce4039747b It appears that pending requests to the hypervisor can be lost or delayed if an immediate exit was requested in vcpu_enter_guest(). As the commit message mentions, only the !injected case is affected, so we add a check at the cancel_injection label to see if we got there as a result of an immediate exit, and then re-issue a KVM_REQ_EVENT request if we are. The Windows guest is waiting for an event to be processed, which never happens, and so gets stuck. Even though the above commit has a Fixes: tag to a commit in 3.15-rc1, in my testing the 4.15 kernel with a Bionic-ussuri userspace does not reproduce the issue, so SRU to Bionic will not be needed. [Testcase] A cascadelake based Xeon server is required. Anything else and the bug will not reproduce. I used a c5.metal server on AWS. It has the following processor: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz Install a KVM stack, and ubuntu-desktop. Set up xrdp and confirm you can reach the desktop. Copy a Windows Server 2k19 image to the destination server, as well as a recent ISO image of virtio drivers. Install virt-manager. Create a new virtual machine using the Windows 2k19 defaults. Use 8 vcpus, 16gb ram. Click customise button to change settings before install. Change the hard disk to be SATA, attach a new cd rom drive for the virtio drivers. Change networking to virtio. Change CPU to Cascadelake-Server-noTSX. Edit the virsh xml, and ensure you set the following features for CPU: Cascadelake-Server-noTSX Those settings are an absolute must. Boot the VM, and install Windows 2k19 with the desktop environment. Once it is installed, open up computer management > device manager and install drivers from the virtio ISO for missing hardware, likely the network and balloon devices. From there, go to server manager, and install the hyper-v role. Reboot the server. It will reboot a few times, and on the final time, it will lock up before it reaches the log in screen. In virt-manager, go to the performance tab. The CPU will be stuck at 100%. The windows guest will be non responsive. A patched kernel is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf296306-test If you install this kernel and boot the Windows 2k19 guest, it will come up normally when the hyper-v role is enabled, and you will be able to log in. [Where problems could occur] This is a change to a core part of the kvm subsystem, so there is potential for regression which could affect all users of KVM. If a regression were to occur, there are no workarounds. Users would need to downgrade their kernel while a fix is developed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911001] Re: Use DCPD to control HP DreamColor panel
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Groovy) 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/1911001 Title: Use DCPD to control HP DreamColor panel Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Cannot change brightness on HP ZBook Fury with certain panel. [Fix] Add the panel to DPCD quirk table to use DPCD to control the panel backlight. [Test] Changing backlight sysfs doesn't change the display brightness. With the patch applied, changing sysfs backlight can really change the display brightness. [Where problems could occur] This fix is specific to a single panel, so it's not likely to cause any regression to other devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1911001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I have these installed: dpkg -l | grep "linux\-[a-z]*\-" rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46 ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1 ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1 I tried as Charles Green said: Switching to tty2 and then back to tty1 causes the boot to complete. (Ctrl+Alt+F2, Ctrl+Alt+F1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
** Also affects: ubuntu-release-notes
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the lack of hardware this test needs to be done by IBM.
[Regression Potential]
* There is a certain regression risk with this patch, since:
* The handling of 'scpdata' is changed, and with that the way
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
If anyone affected by this bug can still reproduce it in their environments, I would like them to try installing linux-modules-extra and rebooting to see if the issue clears. You will need to do this with your 5.4 kernel. Thanks in advance, Terry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912828] Re: USB resets since upgrade to 20.04
** Summary changed: - USB resets sind upgrade to 20.04 + USB resets since upgrade to 20.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/1912828 Title: USB resets since upgrade to 20.04 Status in linux package in Ubuntu: Confirmed Bug description: since upgrading from 18.04 to 20.04 i experience interruptions of my usb keyboard every few minutes. during these events either keys are ignored or get repeated until i press the same key again. in dmesg it is shown like this: [206129.443725] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206131.063578] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206132.719719] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206134.143584] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206135.923480] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci i tried plugging it to different usb ports. it happens on any ports but i noticed it happens way more frequently on the ports on the backside of the PC than on the front side (they happen to be different usb busses). i also did upgrade the BIOS to the latest version, but that did not change the behavior at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twix 3831 F pulseaudio /dev/snd/pcmC0D0p: twix 3831 F...m pulseaudio /dev/snd/controlC2: twix 3831 F pulseaudio /dev/snd/controlC1: twix 3831 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 22 18:56:19 2021 HibernationDevice: RESUME=UUID=fd4b40d6-dd20-49d8-a82f-36efaec3481b InstallationDate: Installed on 2016-06-26 (1671 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Studio XPS 8100 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-05 (17 days ago) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912828] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912828 Title: USB resets sind upgrade to 20.04 Status in linux package in Ubuntu: Confirmed Bug description: since upgrading from 18.04 to 20.04 i experience interruptions of my usb keyboard every few minutes. during these events either keys are ignored or get repeated until i press the same key again. in dmesg it is shown like this: [206129.443725] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206131.063578] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206132.719719] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206134.143584] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206135.923480] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci i tried plugging it to different usb ports. it happens on any ports but i noticed it happens way more frequently on the ports on the backside of the PC than on the front side (they happen to be different usb busses). i also did upgrade the BIOS to the latest version, but that did not change the behavior at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twix 3831 F pulseaudio /dev/snd/pcmC0D0p: twix 3831 F...m pulseaudio /dev/snd/controlC2: twix 3831 F pulseaudio /dev/snd/controlC1: twix 3831 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 22 18:56:19 2021 HibernationDevice: RESUME=UUID=fd4b40d6-dd20-49d8-a82f-36efaec3481b InstallationDate: Installed on 2016-06-26 (1671 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Studio XPS 8100 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-05 (17 days ago) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885462] Re: snd_hda_intel 0000:00:0e.0: No response from codec, resetting bus:
Why was this set invalid? The change in /etc/modprobe.d/audio_powersave.conf seems more of a work-around than a fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885462 Title: snd_hda_intel :00:0e.0: No response from codec, resetting bus: Status in linux package in Ubuntu: Invalid Bug description: If I connect headphones after the system boot or if I boot the system with headphone connected and after boot disconnect the headphone without reproducing any sound before, the system starts flooding dmesg with messages like "snd_hda_intel :00:0e.0: No response from codec, resetting bus: last cmd=0x01470500" and becomes very slow. If I boot the system and reproduce any sound before disconnecting headphone, everything works normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1515 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 20:48:44 2020 InstallationDate: Installed on 2020-06-26 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Positivo Tecnologia SA N1240 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA dmi.bios.version: V1.09.X dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: N14DP6 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11139547 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: MASTER dmi.product.name: N1240 dmi.product.sku: 3052532 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Positivo Tecnologia SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912829] Re: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1912829 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: i install google chrome and after install i have this error message and my wi-fi icon disappear too. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-38-generic Date: Fri Jan 22 10:08:06 2021 Dependencies: nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1 nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-10-12 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 435.21-0ubuntu7 Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-455 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1912829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912828] [NEW] USB resets sind upgrade to 20.04
Public bug reported: since upgrading from 18.04 to 20.04 i experience interruptions of my usb keyboard every few minutes. during these events either keys are ignored or get repeated until i press the same key again. in dmesg it is shown like this: [206129.443725] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206131.063578] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206132.719719] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206134.143584] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206135.923480] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci i tried plugging it to different usb ports. it happens on any ports but i noticed it happens way more frequently on the ports on the backside of the PC than on the front side (they happen to be different usb busses). i also did upgrade the BIOS to the latest version, but that did not change the behavior at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twix 3831 F pulseaudio /dev/snd/pcmC0D0p: twix 3831 F...m pulseaudio /dev/snd/controlC2: twix 3831 F pulseaudio /dev/snd/controlC1: twix 3831 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 22 18:56:19 2021 HibernationDevice: RESUME=UUID=fd4b40d6-dd20-49d8-a82f-36efaec3481b InstallationDate: Installed on 2016-06-26 (1671 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Studio XPS 8100 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-05 (17 days ago) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912828 Title: USB resets sind upgrade to 20.04 Status in linux package in Ubuntu: New Bug description: since upgrading from 18.04 to 20.04 i experience interruptions of my usb keyboard every few minutes. during these events either keys are ignored or get repeated until i press the same key again. in dmesg it is shown like this: [206129.443725] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206131.063578] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206132.719719] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206134.143584] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206135.923480] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci i tried plugging it to different usb ports. it happens on any ports but i noticed it happens way more frequently on the ports on the backside of the PC than on the front side (they happen to be different usb busses). i also did upgrade the BIOS to the latest version, but that did not change the behavior at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twix 3831 F pulseaudio /dev/snd/pcmC0D0p: twix 3831 F...m pulseaudio /dev/snd/controlC2: twix 3831 F pulseaudio /dev/snd/controlC1: twix 3831 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 22 18:56:19 2021 HibernationDevice: RESUME=UUID=fd4b40d6-dd20-49d8-a82f-36efaec3481b InstallationDate: Installed on 2016-06-26 (1671 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Studio XPS 8100 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic
[Kernel-packages] [Bug 1912829] [NEW] nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build
Public bug reported: i install google chrome and after install i have this error message and my wi-fi icon disappear too. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-38-generic Date: Fri Jan 22 10:08:06 2021 Dependencies: nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1 nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-10-12 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 435.21-0ubuntu7 Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-455 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1912829 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: i install google chrome and after install i have this error message and my wi-fi icon disappear too. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-38-generic Date: Fri Jan 22 10:08:06 2021 Dependencies: nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1 nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-10-12 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 435.21-0ubuntu7 Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-455 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1912829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912825] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912825 Title: Bluetooth device not found Status in linux package in Ubuntu: Confirmed Bug description: I've tried a lot of recommendations from ask.ubuntu, but none work. However, in Windows 10, the Bluetooth device is recognized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jezer 1971 F pulseaudio /dev/snd/pcmC0D0p: jezer 1971 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 11:25:08 2021 InstallationDate: Installed on 2020-07-02 (204 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2609828f-4157-41ce-b7f8-b2ee1c99f19a ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell linux-image-5.8.0-40-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-28 (24 days ago) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG2351BNJ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr088811000330591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: C2M42UA#ABA dmi.product.version: 088811000330591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
Can you please install linux-modules-extra: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/comments/23 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux
[Kernel-packages] [Bug 1912825] [NEW] Bluetooth device not found
Public bug reported: I've tried a lot of recommendations from ask.ubuntu, but none work. However, in Windows 10, the Bluetooth device is recognized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jezer 1971 F pulseaudio /dev/snd/pcmC0D0p: jezer 1971 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 11:25:08 2021 InstallationDate: Installed on 2020-07-02 (204 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2609828f-4157-41ce-b7f8-b2ee1c99f19a ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell linux-image-5.8.0-40-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-28 (24 days ago) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG2351BNJ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr088811000330591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: C2M42UA#ABA dmi.product.version: 088811000330591620100 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912825 Title: Bluetooth device not found Status in linux package in Ubuntu: New Bug description: I've tried a lot of recommendations from ask.ubuntu, but none work. However, in Windows 10, the Bluetooth device is recognized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jezer 1971 F pulseaudio /dev/snd/pcmC0D0p: jezer 1971 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 11:25:08 2021 InstallationDate: Installed on 2020-07-02 (204 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2609828f-4157-41ce-b7f8-b2ee1c99f19a ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell linux-image-5.8.0-40-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-28 (24 days ago) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG2351BNJ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr088811000330591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: C2M42UA#ABA dmi.product.version: 088811000330591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912825/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 616538] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
i have use a New wifi/bt card and no issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/616538 Title: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in bcmwl package in Ubuntu: Invalid Status in dkms package in Ubuntu: Fix Released Bug description: bcmwl-kernel-source fails to install if you have a mainline kernel installed. Went to jockey or "hardware drivers" and selected to install Brodcom's Proprietary STA driver (for 43xx series wireless cards). A "SystemError: installArchives() failed" error came up and apport prompted me to report this bug. I was testing a mainline kernel when this happened. Booting into the current kernel and trying to install the driver again gives the same error. Trying to get back (test1): - sudo apt-get purge bcmwl-kernel-source - upon my return to jockey, seem sta is still there byt b43/fwcutter was removed - attempting to download sta gives same error - SystemError: installArchives() failed *WORKAROUND* Trying to get back (test2): - sudo apt-get purge bcmwl-kernel-source linux-image-2.6.35-020635rc6-generic linux-headers-2.6.35-020635rc6 linux-headers-2.6.35-020635rc6-generic - reboot - upon my return to jockey, both sta and b43/fwcutter are there. Installing sta now works. Expecting: If this is a problem where DKMS thinks it should recompile modules for all kernels, it should simply report that it cannot compile the module for a specific kernel and provide a reason. If there is a way to test mainline kernels and broadcom drivers together, that fix would be ideal. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 Uname: Linux 2.6.35-020635rc6-generic i686 Architecture: i386 Date: Wed Aug 11 18:04:22 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1) SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/616538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909840] Re: SDXC card reader not working properly
What filesystem does the card use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909840 Title: SDXC card reader not working properly Status in linux package in Ubuntu: Confirmed Bug description: I have tried to use a 8GB flash and it works without any flaw in ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM), but i need to use my 128GB SDXC card and it only works in my windows system in the same machine. I am "able" to copy files to it in ubuntu (to the 128GB SDXC card) but most of the copies appear as corrupted files, which does not happen in windows. The 8GB card had been tested by f3 in ubuntu and h2testw in windows, and the SDXC had been tested by h2testw in windows (testing the SDXC with f3 in ubuntu causes input/output error), so i assume there are no problems in the sd cards. I think that this problem is related to (or almost the same as) https://bugzilla.kernel.org/show_bug.cgi?id=202473 by lspci i get 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03) 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) 00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03) 00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3) 00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03) 00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03) 00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03) - 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth (rev 99) booting up and putting the SDXC card and removing it gives by dmesg [ 119.612298] mmc1: cannot verify signal voltage switch [ 119.737024] mmc1: new ultra high speed SDR104 SDXC card at address [ 119.737955] mmcblk1: mmc1: SB128 119 GiB [ 119.755488] mmcblk1: p1 [ 208.417246] mmc1: card removed The module used is rtsx_pci. by lspci -nnk|grep -A2 RTS5229 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci Sorry for the lack of information, i tried to use ubuntu-bug. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bruno 1008 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-01 (33 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81KT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN22WW X64 dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1910894] Re: Wireless worked in "linux-image-unsigned-5.0.0-37-generic 5.0.0-37.41+redmiv3" doesn't work in 5.4 kernel
Can you please attach dmesg under both 5.0 and 5.4? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910894 Title: Wireless worked in "linux-image-unsigned-5.0.0-37-generic 5.0.0-37.41+redmiv3" doesn't work in 5.4 kernel Status in linux package in Ubuntu: Incomplete Bug description: run apt update && apt upgrade. after that booted with kernerl 5.4 LTS Wireless connection keep on asking for password or encryption keys for wi-fi which are already linked properly with 5.0.0-37-generic. Laptop: Redmi Book 14 2019 lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 uname -r 5.0.0-37-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-01-22 11:01 EDT---
(In reply to comment #89)
> So for now I think we should pick up the patches as they are,
> since they already provide value and we will be at a similar level like on
> groovy,
> mention the current situation in the release notes and pointing to
> "nvme-core.multipath=0"
> and SRUing a chreipl fix as soon as it becomes available (probably for H, G
> and F then).
Sounds good, thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-01-22 10:39 EDT---
(In reply to comment #87)
> Ubuntu supports NVMe Multipath on all architectures in Focal. I know that
> some other distributions do not.
>
> Setting nvme-core.multipath=0 for s390x isos only, or changing kernel config
> to disable multipath to "n" on s390x only, would mean regression on s390x as
> compared with amd64/arm64/ppc64le.
>
> That would be suboptimal.
>
> Do you have no plans to support multipath NVMe and are customers who buy
> expensive multipath capable NVMe drives will not be able to use multipath
> capability with them? Or for example is multipath handled separately on Z
> with NVMe? (ie. HMC mediated)
>
> My preference would be to see a chreipl fix upstream in s390-tools to add
> support for multipath nvme drives, and SRU that too.
Oh, we absolutely want to support NVMe multipathing and I don't see
a general reason to disable it in the config as I don't know
about any other issues with it. This is only about working
around the current "chreipl node /dev/nvmeXYZ" bug which as far as I
understand breaks the final reboot from the installer to the
installed system. We're already working on a chreipl fix but as far
as I understand the installer ISOs are released only for .x releases
and running the installer with multipathing off should only impact
the installer's performance or am I missing something? So
this is definitely meant as a temporary workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
So for now I think we should pick up the patches as they are,
since they already provide value and we will be at a similar level like on
groovy,
mention the current situation in the release notes and pointing to
"nvme-core.multipath=0"
and SRUing a chreipl fix as soon as it becomes available (probably for H, G and
F then).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the
[Kernel-packages] [Bug 1912799] Re: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be co
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1912799 Title: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia- compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: Happened when updating OS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 20 16:01:42 2021 DuplicateSignature: package:libnvidia-compute-450:i386:450.102.04-0ubuntu0.20.04.1 Setting up mutter-common (3.36.7+git20201123-0.20.04.1) ... dpkg: error processing package libnvidia-compute-450:amd64 (--configure): package libnvidia-compute-450:amd64 450.102.04-0ubuntu0.20.04.1 cannot be configured because libnvidia-compute-450:i386 is at a different version (450.80.02-0ubuntu0.20.04.2) ErrorMessage: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) InstallationDate: Installed on 2020-10-06 (107 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1912799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912803] [NEW] switch to an autogenerated core via dkms-versions
Public bug reported: Switch the linux-restricted-modules payload to an autogenerated core based on the contents of the debian/dkms-versions. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1912803 Title: switch to an autogenerated core via dkms-versions Status in linux-restricted-modules package in Ubuntu: New Bug description: Switch the linux-restricted-modules payload to an autogenerated core based on the contents of the debian/dkms-versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1912803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912799] [NEW] package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be
Public bug reported: Happened when updating OS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 20 16:01:42 2021 DuplicateSignature: package:libnvidia-compute-450:i386:450.102.04-0ubuntu0.20.04.1 Setting up mutter-common (3.36.7+git20201123-0.20.04.1) ... dpkg: error processing package libnvidia-compute-450:amd64 (--configure): package libnvidia-compute-450:amd64 450.102.04-0ubuntu0.20.04.1 cannot be configured because libnvidia-compute-450:i386 is at a different version (450.80.02-0ubuntu0.20.04.2) ErrorMessage: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) InstallationDate: Installed on 2020-10-06 (107 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1912799 Title: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia- compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: Happened when updating OS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 20 16:01:42 2021 DuplicateSignature: package:libnvidia-compute-450:i386:450.102.04-0ubuntu0.20.04.1 Setting up mutter-common (3.36.7+git20201123-0.20.04.1) ... dpkg: error processing package libnvidia-compute-450:amd64 (--configure): package libnvidia-compute-450:amd64 450.102.04-0ubuntu0.20.04.1 cannot be configured because libnvidia-compute-450:i386 is at a different version (450.80.02-0ubuntu0.20.04.2) ErrorMessage: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) InstallationDate: Installed on 2020-10-06 (107 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: package libnvidia-compute-450:i386 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: package libnvidia-compute-450:i386 450.80.02-0ubuntu0.20.04.2 cannot be configured because libnvidia-compute-450:amd64 is at a different version (450.102.04-0ubuntu0.20.04.1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1912799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
Ubuntu supports NVMe Multipath on all architectures in Focal. I know
that some other distributions do not.
Setting nvme-core.multipath=0 for s390x isos only, or changing kernel
config to disable multipath to "n" on s390x only, would mean regression
on s390x as compared with amd64/arm64/ppc64le.
That would be suboptimal.
Do you have no plans to support multipath NVMe and are customers who buy
expensive multipath capable NVMe drives will not be able to use
multipath capability with them? Or for example is multipath handled
separately on Z with NVMe? (ie. HMC mediated)
My preference would be to see a chreipl fix upstream in s390-tools to
add support for multipath nvme drives, and SRU that too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-01-22 10:02 EDT---
Hi Frank,
we've now internally confirmed that setting the "nvme-core.multipath=0" Kernel
parameter as a workaround makes "chreipl node" succeed with NVMes that
otherwise break the current chreipl due to its lack of multipath support.
Do you think it would be possible to set this Kernel parameter for the
installer?
As far as I understand this option doesn't necessarily have to be set for the
installed system since the IPL information is stored in firmware as FID
and namespace so only a manual "chreipl node /dev/nvmeXYZ" from
the installed system would risk breaking the IPL information and there
the user should get a crash and can instead use "chreipl nvme -i -s
". Normal "zipl" as done by a kernel update should not be a problem, in
fact I've got an Ubuntu 20.04 installed on an NVMe (via KVM ;-) /dev/vda on an
NVMe) here and kernel updates worked fine.
Alternatively there is also the config option CONFIG_NVME_MULTIPATH if
we would set that to "n" for Z that should also work.
Either way we'll of course work on a proper fix for chreipl.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
Arch has patches for kernels through 5.10:
See
https://github.com/archlinux/svntogit-community/tree/packages/broadcom-wl-dkms/trunk
and also
https://github.com/archlinux/svntogit-community/blob/packages/broadcom-wl-dkms/trunk/PKGBUILD
Note the patch for 5.10:
https://github.com/archlinux/svntogit-community/blob/packages/broadcom-wl-dkms/trunk/011-linux59.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel or later
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Triaged
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of
[Kernel-packages] [Bug 1912793] [NEW] package libnvidia-common-450 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-document
Public bug reported: i was installing the drivest for my nvidia geforce 840 m. while i vas installing the drivers i encountered this error. i was folowing instructions how to install the nvidia trivers thru the terminal. i installed 3 driver for my graphics chip and the error encountered on the driver nvidia-driver-450. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 22 15:45:10 2021 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: package libnvidia-common-450 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1912793 Title: package libnvidia-common-450 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: i was installing the drivest for my nvidia geforce 840 m. while i vas installing the drivers i encountered this error. i was folowing instructions how to install the nvidia trivers thru the terminal. i installed 3 driver for my graphics chip and the error encountered on the driver nvidia-driver-450. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 22 15:45:10 2021 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: package libnvidia-common-450 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1912793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912789] [NEW] Add support for selective build of special drivers
Public bug reported: [SRU Justification] = Impact = We want to add some driver code which exists in the primary kernel source but will not get included unless specifically asked for. As long as there are no drivers using this, there is no user-visible change. = Impact = This will be done by adding a new config option which gets turned on via build setup rules. The default will be off. = Testcase = As long as there are no consumers changes can only be seen by inspecting the build logs (if even that). = Regression Potential = This prepares for future consumers. At this stage either the build will fail completely or pass and in that case the produced kernel binaries are the same as they were before. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912789 Title: Add support for selective build of special drivers Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [SRU Justification] = Impact = We want to add some driver code which exists in the primary kernel source but will not get included unless specifically asked for. As long as there are no drivers using this, there is no user-visible change. = Impact = This will be done by adding a new config option which gets turned on via build setup rules. The default will be off. = Testcase = As long as there are no consumers changes can only be seen by inspecting the build logs (if even that). = Regression Potential = This prepares for future consumers. At this stage either the build will fail completely or pass and in that case the produced kernel binaries are the same as they were before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
apport information ** Tags added: apport-collected ** Description changed: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + Dependencies: + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-20 (1 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 + Tags: focal + Uname: Linux 5.6.0-1042-oem x86_64 + UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
After some additional discussions the situation is as following:
With picking the current s390-tools fix (as it was used so far here) we would
be on the same level (regarding NVMe support) than groovy.
The NVMe testing on groovy was done on a device without multipath.
The issue that cropped up during the testing on focal now is because an NVMe
device with multipath was used.
But there is still value of getting the fixes picked up as they are (especially
for a certain team).
However, getting NVMe devices supported also the multipath way and by the
installer, the fix is of course still needed (chreipl).
But since this fix is not only needed for focal, but at least also for groovy
(and probably also for hirsute), I think it's fine to drive this missing bit a
later stage, based on a separate ticket and dedicated s390-tools package SRU.
(Please keep in mind that this is all s390x specific!)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Kernel-packages] [Bug 1912670] Re: Mouse buttons and keyboard unresponsive after idle time
Thanks. Here are the results of your suggestions, plus some other things I tried: 1. 'tlp' was not installed. 2. I installed 'powertop' and checked its 'Tunables' section. There were 6 entries for "Autosuspend for USB device xHCI Host Controller" all set to 'Good' - I changed these to 'Bad'. The problem still occurred. 3. Further diagnostics eventually led to my trying the following: * added "usbcore.autosuspend=-1" to the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub * ran: sudo update-grub * rebooted * cat /sys/module/usbcore/parameters/autosuspend [shows -1 as expected] * cat /sys/bus/usb/devices/usb[1-6]/power/autosuspend_delay_ms [now shows -1000 - (was previously 0) ] but the problem still occurs. 4. Repeated the above GRUB change with the parameter 'autosuspend_delay_ms' rather than 'autosuspend'. * ls /sys/module/usbcore/parameters [shows an 'autosuspend' parameter but not an 'autosuspend_delay_ms' parameter] * sudo modinfo usbcore [shows: parm: autosuspend:default autosuspend delay (int)] * cat /sys/bus/usb/devices/usb[1-6]/power/autosuspend_delay_ms [now shows 0] but the problem still occurs. In all cases I still get the same five 'device removed' messages in /var/log/Xorg.0.log as originally reported, and the mouse and keyboard are unresponsive after a few minutes idle time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912670 Title: Mouse buttons and keyboard unresponsive after idle time Status in linux package in Ubuntu: Confirmed Bug description: If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1, Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and most keyboard presses become unresponsive. My "system power saving" setting is disabled (set to "never") and "display power management" is set to blank after 15 minutes, but the problem seems to occur sooner than that. Unplugging and re-inserting the mouse after a few seconds has no effect. The only keystrokes that have any effect are Ctrl+Alt+F1 for a terminal session (where I can type normally). Returning to the desktop with Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before. This occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26 kernel and the problem happens with that too. When I reboot the machine everything works fine again, but after a few minutes of idle time, the same problem occurs again. I've only noticed the problem occurring in the last ~2-3 weeks. When I leave a terminal window open on the desktop running the command: tail -f /var/log/Xorg.0.log and allow lots of time for the problem to occur, no lines are appended in the terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 and log in at the terminal console, the following additional lines appear in /var/log/xorg.0.log : [ 3805.283] (II) event1 - Power Button: device removed [ 3805.296] (II) event0 - Power Button: device removed [ 3805.312] (II) event3 - Logitech USB Optical Mouse: device removed [ 3805.344] (II) event4 - Eee PC WMI hotkeys: device removed [ 3805.364] (II) event2 - AT Translated Set 2 keyboard: device removed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 16:37:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501] InstallationDate: Installed on 2020-05-17 (249 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1912772] Re: Panic on sysfs read
** Package changed: ubuntu => linux-raspi (Ubuntu) -- 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/1912772 Title: Panic on sysfs read Status in linux-raspi package in Ubuntu: New Bug description: 1) root@fry:~# lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) root@fry:~# apt-cache policy linux-image-raspi linux-image-raspi: Installed: 5.8.0.1011.14 [...] 3) Nothing 4) On a Raspberry Pi 4 Rev 1.4 8GB, the kernel panics if you read the /sys/kernel/debug/regmap/dummy-avs-monitor@7d5d2000/registers file. You find a screenshot attached. Unfortunately, I don't have a serial adaptor at hand, and I didn't get netconsole working right now. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-raspi 5.8.0.1011.14 ProcVersionSignature: Ubuntu 5.8.0-1011.14-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-1011-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Fri Jan 22 11:29:32 2021 ImageMediaBuild: 20201022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:E2:2A:BE vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-1011-raspi N/A linux-backports-modules-5.8.0-1011-raspi N/A linux-firmware1.190.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_v4l2 bcm2835_mmal_vchiq bcm2835_codec bcm2835_isp snd_bcm2835 vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1912772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912772] [NEW] Panic on sysfs read
You have been subscribed to a public bug: 1) root@fry:~# lsb_release -rd Description:Ubuntu 20.10 Release:20.10 2) root@fry:~# apt-cache policy linux-image-raspi linux-image-raspi: Installed: 5.8.0.1011.14 [...] 3) Nothing 4) On a Raspberry Pi 4 Rev 1.4 8GB, the kernel panics if you read the /sys/kernel/debug/regmap/dummy-avs-monitor@7d5d2000/registers file. You find a screenshot attached. Unfortunately, I don't have a serial adaptor at hand, and I didn't get netconsole working right now. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-raspi 5.8.0.1011.14 ProcVersionSignature: Ubuntu 5.8.0-1011.14-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-1011-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Fri Jan 22 11:29:32 2021 ImageMediaBuild: 20201022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:E2:2A:BE vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-1011-raspi N/A linux-backports-modules-5.8.0-1011-raspi N/A linux-firmware1.190.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_v4l2 bcm2835_mmal_vchiq bcm2835_codec bcm2835_isp snd_bcm2835 vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy staging -- Panic on sysfs read https://bugs.launchpad.net/bugs/1912772 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
Maybe it's a fix for bug 1866587 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
Another note is that although this does not fix the hang on KVM instance, but I can see this test passed on B-AWS bare metals (was failing on previous cycle) Instance c5.metal 4.15.0-1091.96 AWS Test failed with timeout https://pastebin.ubuntu.com/p/b77pbFdjf7/ 4.15.0-1093.99 AWS Test passed 6. 01/22 06:24:42 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.lGWO5mvwC6 -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.zlSuqJDX9u 7. 01/22 06:24:42 DEBUG| utils:0153| [stdout] enabling apic 8. 01/22 06:24:42 DEBUG| utils:0153| [stdout] paging enabled 9. 01/22 06:24:42 DEBUG| utils:0153| [stdout] cr0 = 80010011 10. 01/22 06:24:42 DEBUG| utils:0153| [stdout] cr3 = 477000 11. 01/22 06:24:42 DEBUG| utils:0153| [stdout] cr4 = 20 12. 01/22 06:24:42 DEBUG| utils:0153| [stdout] 13. 01/22 06:24:42 DEBUG| utils:0153| [stdout] Test suite: vmx_nm_test 14. 01/22 06:24:42 DEBUG| utils:0153| [stdout] PASS: fnop with CR0.TS set in L2 triggers #NM VM-exit to L1 15. 01/22 06:24:42 DEBUG| utils:0153| [stdout] PASS: fnop with CR0.EM set in L2 triggers #NM VM-exit to L1 16. 01/22 06:24:42 DEBUG| utils:0153| [stdout] SUMMARY: 9 tests 17. 01/22 06:24:42 DEBUG| utils:0153| [stdout] PASS vmx_nm_test (9 tests) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
Follow up for comment #15, the instance will be in a "paused" state in virsh after this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
Hello Thadeu, With the B-kvm proposed kernel (4.15.0-1084.86 linux-kvm), this vmx-nm-test still hangs This is syslog from console: [ 1003.399966] kvm: MWAIT instruction emulated as NOP! [ 1061.306351] *** Guest State *** [ 1061.306676] CR0: actual=0x80010031, shadow=0x80010031, gh_mask=fff7 [ 1061.307599] CR4: actual=0x2020, shadow=0x2020, gh_mask=e871 [ 1061.308426] CR3 = 0x00477000 [ 1061.308701] RSP = 0x0046e748 RIP = 0x00404850 [ 1061.309219] RFLAGS=0x0002 DR7 = 0x0400 [ 1061.309715] Sysenter RSP= CS:RIP=0008:004003d8 [ 1061.310334] CS: sel=0x0008, attr=0x0a09b, limit=0x, base=0x [ 1061.311254] DS: sel=0x0010, attr=0x0c093, limit=0x, base=0x [ 1061.312037] SS: sel=0x0010, attr=0x0c093, limit=0x, base=0x [ 1061.312812] ES: sel=0x0010, attr=0x0c093, limit=0x, base=0x [ 1061.313780] FS: sel=0x0010, attr=0x0c093, limit=0x, base=0x [ 1061.314636] GS: sel=0x0010, attr=0x0c093, limit=0x, base=0x [ 1061.315517] GDTR: limit=0x, base=0x0041d00a [ 1061.316671] LDTR: sel=0x, attr=0x00082, limit=0x, base=0x [ 1061.317590] IDTR: limit=0x, base=0x [ 1061.318534] TR: sel=0x0080, attr=0x0008b, limit=0x0067, base=0x8b41d48a [ 1061.319666] EFER = 0x0500 PAT = 0x0007040600070406 [ 1061.320394] DebugCtl = 0x DebugExceptions = 0x [ 1061.321303] BndCfgS = 0x [ 1061.321756] Interruptibility = ActivityState = [ 1061.322576] InterruptStatus = [ 1061.322948] *** Host State *** [ 1061.323317] RIP = 0xc058c0e6 RSP = 0xa5b8879c3ca0 [ 1061.323986] CS=0010 SS=0018 DS= ES= FS= GS= TR=0040 [ 1061.324698] FSBase=7fa9f3915700 GSBase=a2487fd0 TRBase=fe05b000 [ 1061.325589] GDTBase=fe059000 IDTBase=fe00 [ 1061.326382] CR0=80050033 CR3=000128b3e000 CR4=26a0 [ 1061.327374] Sysenter RSP=fe05b000 CS:RIP=0010:be801700 [ 1061.328157] EFER = 0x0d01 PAT = 0x0007040600070406 [ 1061.328838] *** Control State *** [ 1061.329236] PinBased=00bf CPUBased=b6a06dfe SecondaryExec=000223e3 [ 1061.330206] EntryControls=0001d3ff ExitControls=00afefff [ 1061.330828] ExceptionBitmap=00060042 PFECmask= PFECmatch= [ 1061.331815] VMEntry: intr_info= errcode= ilen= [ 1061.332592] VMExit: intr_info= errcode= ilen=0003 [ 1061.333421] reason=8021 qualification= [ 1061.334151] IDTVectoring: info= errcode= [ 1061.334920] TSC Offset = 0xfcf67b3d [ 1061.335511] TPR Threshold = 0x00 [ 1061.335879] PostedIntrVec = 0xf2 [ 1061.336254] EPT pointer = 0x5b4ef05e [ 1061.336755] Virtual processor ID = 0x0001 ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-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/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx
[Kernel-packages] [Bug 1887774] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-22 05:55 EDT---
IBM Bugzilla status->closed, Fix Released for all requested distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887774
Title:
[UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed
ERP
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Linux kernel panics due to kernel page fault in IRQ context when
running zfcp_erp_timeout_handler() calling zfcp_erp_notify().
[Fix]
* 936e6b85da0476dd2edac7c51c68072da9fb4ba2 936e6b85da04 "scsi: zfcp:
Fix panic on ERP timeout for previously dismissed ERP action"
[Test Case]
* Requires an IBM z13/z13s or LinuxONE Rockhopper/Emperor system (or
newer) connected to zfcp capcble storage sub-system.
* Initiate an (ERP) timeout (maybe by injection or by causing a slow
recovery otherwise).
* Monitor the system log for any kernel panics.
[Regression Potential]
* The regression can be considered as medium since the modification is
platform specific / limited to s390x and again limited to the zfcp
layer.
* Within zfcp it's further limited to the error recovery procedure
(ERP) of fcp and only touches zfcp_erp.c, means the code path is
mainly active under error conditions.
[Other]
* The above fix is upstream accepted with v5.8-rc3, hence will make
it's way to groovy with kernel 5.8.
* Therefore this SRU request was submitted for bionic and focal only
and not for groovy.
__
Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP
Symptom: Linux kernel panic due to kernel page fault in IRQ context
when running zfcp_erp_timeout_handler() calling
zfcp_erp_notify().
Problem: Suppose that, for unrelated reasons, FSF requests on behalf
of recovery are very slow and can run into the ERP timeout.
In the case at hand, we did adapter recovery to a large
degree. However due to the slowness a LUN open is pending so
the corresponding fc_rport remains blocked. After
fast_io_fail_tmo we trigger close physical port recovery for
the port under which the LUN should have been opened. The
new higher order port recovery dismisses the pending LUN
open ERP action and dismisses the pending LUN open FSF
request. Such dismissal decouples the ERP action from the
pending corresponding FSF request by setting
zfcp_fsf_req->erp_action to NULL (among other things)
[zfcp_erp_strategy_check_fsfreq()].
If now the ERP timeout for the pending open LUN request runs
out, we must not use zfcp_fsf_req->erp_action in the ERP
timeout handler. This is a problem since v4.15 commit
75492a51568b ("s390/scsi: Convert timers to use
timer_setup()"). Before that we intentionally only passed
zfcp_erp_action as context argument to
zfcp_erp_timeout_handler().
Note: The lifetime of the corresponding zfcp_fsf_req object
continues until a (late) response or an (unrelated) adapter
recovery.
Solution: Just like the regular response path ignores dismissed
requests [zfcp_fsf_req_complete() =>
zfcp_fsf_protstatus_eval() => return early] the ERP timeout
handler now needs to ignore dismissed requests. So simply
return early in the ERP timeout handler if the FSF request
is marked as dismissed in its status flags. To protect
against the race where zfcp_erp_strategy_check_fsfreq()
dismisses and sets zfcp_fsf_req->erp_action to NULL after
our previous status flag check, return early if
zfcp_fsf_req->erp_action is NULL. After all, the former ERP
action does not need to be woken up as that was already done
as part of the dismissal above [zfcp_erp_action_dismiss()].
Upstream-ID: 936e6b85da0476dd2edac7c51c68072da9fb4ba2 -> kernel 5.8
Will be integrated by kernel 5.8 by groovy.
Please check that this also be integrated into 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1912646] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455590/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455589/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455588/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455587/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455586/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455585/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455584/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455583/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455582/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455581/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455580/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455579/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455578/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455577/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455576/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455575/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455574/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Re: Ubuntu 20.10 freeze after update
apport information ** Tags added: apport-collected wayland-session ** Description changed: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. - I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from - the kernel team. All freeze. + I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: haug 2161 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2019-09-26 (483 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: LENOVO 20LS001AGE + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-40-generic N/A + linux-backports-modules-5.8.0-40-generic N/A + linux-firmware1.190.3 + Tags: groovy wayland-session + Uname: Linux 5.8.0-40-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) + UserGroups: sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 08/05/2020 + dmi.bios.release: 1.40 + dmi.bios.vendor: LENOVO + dmi.bios.version: R0QET63W (1.40 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20LS001AGE + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.40 + dmi.modalias: dmi:bvnLENOVO:bvrR0QET63W(1.40):bd08/05/2020:br1.40:efr1.40:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad L480 + dmi.product.name: 20LS001AGE + dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 + dmi.product.version: ThinkPad L480 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1912646/+attachment/5455573/+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/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Confirmed Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haug 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-26 (483 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS001AGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-40-generic root=UUID=39812da1-4b85-4eac-bf54-de26c89ea52f ro rootflags=subvol=@ psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 Tags: groovy wayland-session Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-01-09 (12 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET63W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version:
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
I have reported this issue to ASUS support. If they don't reply, we have to demand them solve it by the support website: https://www.asus.com/support/product/contactus/services/questionform/?lang =us-en This issue belongs to ASUS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912752] [NEW] linux-uc20-efi: megaraid_sas required in the initrd
Public bug reported: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: elgin oem-priority originate-from-1911361 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Tags added: elgin oem-priority originate-from-1911361 ** Description changed: == Impact == - System fails to boot with UC20 pc-kernel snap because of unable to find the storage device. + Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. ** Summary changed: - linux-uc20-efi: extra kernel modules required in the initrd + linux-uc20-efi: megaraid_sas required in the initrd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
Hi Tom,
that's awesome.
For F/G I am not sure about the release schedule. But this commit has already
landed on these two kernels. Should be ready soon.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906128
Title:
Touchpad not detected on ByteSpeed C15B laptop
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Touchpad on a ByteSpeed C15B laptop is not working.
User will need to add i8042.noloop=1 to boot options to make it work.
[Fix]
* a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")
This fix can be cherry-picked into all affected releases.
[Test Case]
Test kernel for Bionic / Focal can be found here:
https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/
And they have been tested with positive test results.
[Where problems could occur]
The fix is just a small and simple hardware quirk. I can't think of any
potential problem for now.
== Original Bug Report ==
Touchpad hardware is OK and works for Win10. Not working for live disc, not
for 18.04 and not for 20.04 after upgrading. I've attached a Logitech wireless
mouse with its USB adapter and that works. Bluetooth is also missing, but I
have not started trying to skull that out. I'm happy to help try debugging
things, and to help resolve the issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tom1395 F pulseaudio
/dev/snd/controlC0: tom1395 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 19:09:05 2020
InstallationDate: Installed on 2020-01-26 (307 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
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.4.0-54-generic
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.616
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: C15B
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ByteSpeed LLC
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: ByteSpeed Laptop C15B
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: ByteSpeed LLC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910561 Title: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 Mobile Workstation when muting corresponding audio devices. * The right channel of internal speaker has not sound. [Fix] Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling LEDs and initialing AMP. [Test] Built a test kernel with applying this patch, the mute/micmute LEDs are work as expected. The internal speaker could play the sounds from left and right channels. [Where problems could occur] This quirk is specific for these two platforms. It should not cause the regression to other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1910561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
** Tags added: sru-20210104 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: New Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769] mmiotrace: enabled CPU26. kernel: [ 2236.684537] smpboot: Booting Node 0 Processor 27 APIC 0x1b kernel: [ 2236.685751]
