[Kernel-packages] [Bug 2062502] Re: linux-firmware package breaks iwlwifi
That apport-collect is with the older linux-firmware package installed,
as my wifi does not work with the new one.
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771152/+files/WifiSyslog.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771153/+files/acpidump.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771151/+files/UdevDb.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771150/+files/RfKill.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771149/+files/ProcModules.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771147/+files/ProcCpuinfoMinimal.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771148/+files/ProcInterrupts.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771146/+files/ProcCpuinfo.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771145/+files/Lsusb-v.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771144/+files/Lsusb-t.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771143/+files/Lsusb.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771142/+files/Lspci-vt.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771141/+files/Lspci.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771140/+files/IwConfig.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771139/+files/CurrentDmesg.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: been 2559 F wireplumber
/dev/snd/controlC1: been 2559 F wireplumber
/dev/snd/seq:been 2554 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-11-17 (162 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-28-generic N/A
linux-backports-modules-6.5.0-28-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCTGL357.0040.2021.1126.1843
dmi.board.name: LAPKC71F
dmi.board.vendor: Intel Corporation
dmi.board.version: M2-402
dmi.chassis.type: 10
dmi.chassis.vendor: Intel(R) Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
dmi.product.family: XENIA
dmi.product.name: XENIA 15
dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
dmi.product.version: M37957-402
dmi.sys.vendor: ADATA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062502] Re: linux-firmware package breaks iwlwifi
apport information
** Tags added: apport-collected mantic
** Description changed:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in iwlwifi
driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to
...2.9 of the linux-firmware package, I saw many errors that begin like
this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
- Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no
- errors.
+ Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: been 2559 F wireplumber
+ /dev/snd/controlC1: been 2559 F wireplumber
+ /dev/snd/seq:been 2554 F pipewire
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-11-17 (162 days ago)
+ InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
+ RelatedPackageVersions:
+ linux-restricted-modules-6.5.0-28-generic N/A
+ linux-backports-modules-6.5.0-28-generic N/A
+ linux-firmware20230919.git3672ccab-0ubuntu2.1
+ Tags: mantic
+ Uname: Linux 6.5.0-28-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/26/2021
+ dmi.bios.release: 5.19
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: KCTGL357.0040.2021.1126.1843
+ dmi.board.name: LAPKC71F
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: M2-402
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Intel(R) Corporation
+ dmi.chassis.version: 2.0
+ dmi.ec.firmware.release: 1.11
+ dmi.modalias:
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
+ dmi.product.family: XENIA
+ dmi.product.name: XENIA 15
+ dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
+ dmi.product.version: M37957-402
+ dmi.sys.vendor: ADATA
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2062502/+attachment/5771138/+files/AlsaInfo.txt
--
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/2062502
Title:
linux-firmware package breaks iwlwifi
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
This package version works:
20230919.git3672ccab-0ubuntu2.1
This one causes firmware SW errors and resets - breaking wifi in
iwlwifi driver:
20230919.git3672ccab-0ubuntu2.9
I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
to ...2.9 of the linux-firmware package, I saw many errors that begin
like this in syslog:
2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode
Downgrading to ..2.1 version of linux-firmware
[Kernel-packages] [Bug 2062502] [NEW] linux-firmware package breaks iwlwifi
Public bug reported: This package version works: 20230919.git3672ccab-0ubuntu2.1 This one causes firmware SW errors and resets - breaking wifi in iwlwifi driver: 20230919.git3672ccab-0ubuntu2.9 I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to ...2.9 of the linux-firmware package, I saw many errors that begin like this in syslog: 2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi :00:14.3: Queue 1 is stuck 0 12 2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi :00:14.3: Start IWL Error Log Dump: 2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi :00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2062502 Title: linux-firmware package breaks iwlwifi Status in linux-firmware package in Ubuntu: New Bug description: This package version works: 20230919.git3672ccab-0ubuntu2.1 This one causes firmware SW errors and resets - breaking wifi in iwlwifi driver: 20230919.git3672ccab-0ubuntu2.9 I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to ...2.9 of the linux-firmware package, I saw many errors that begin like this in syslog: 2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi :00:14.3: Queue 1 is stuck 0 12 2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi :00:14.3: Start IWL Error Log Dump: 2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi :00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
> Just a note that 5.15.0-104-generic is a part of the 2024.04.01 SRU cycle, and will likely be released at the end of month, as per https://kernel.ubuntu.com/, and won't be coming out any sooner. Do I understand this correctly, do you keep kernel update 5.15.0-102.112 in place and let people update into a kernel that breaks SMB/CIFS for almost an entire month? Isn't that dangerous? I manage a bunch of Ubuntu servers and I had to instruct people to hold off on all Ubuntu updates immediately as not to break all the file shares, which would be very disruptive to our operations. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
I collected a bunch of info on it. Seems to be reported all over the place: - https://www.reddit.com/r/linux/comments/1bzvy5l/ubuntu_22044_latest_updates_492024_break_cifssmb/ - https://www.reddit.com/r/Ubuntu/comments/1bzshdt/ubuntu_2204_smb_shares_stopped_working_lastnight/ - https://askubuntu.com/questions/1509987/cifs-on-22-04-lts-has-something-changed-between-kernel-5-15-0-101-generic-and - https://forum.level1techs.com/t/cifs-broken-by-ubuntu-server-22-04-4-latest-updates/209639 - https://forums.linuxmint.com/viewtopic.php?t=417371 Oh and there's also a duplicate: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2060797 The most promising lead is this: > Looks like there's a fix that's yet to make it to Linux Mint and Ubuntu > kernels: > > [PATCH 5.15.y 0/1] smb: client: fix "df: Resource temporarily unavailable" on > 5.15 stable kernel > https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/ Many people are affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Confirmed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
https://salsa.debian.org/ubuntu-dev- team/plymouth/-/commit/bd9d0119fdbeb3b30c8d3caafdb8a31b23c188c4 does not reflect the removal of the complete drm section. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: plymouth (Ubuntu) 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Sponsored plymouth 24.004.60-1ubuntu6 after dropping the complete drm modules code and correcting the changelog entries. Unsubscribing ~ubuntu-sponsors. ** Patch added: "plymouth_24.004.60-1ubuntu6_sponsored.debdiff" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5757922/+files/plymouth_24.004.60-1ubuntu6_sponsored.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Daniel, please review and comment https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462691 (see the description for the two possible implementations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Looking at the remaining "add drm modules (only if MODULES=dep)" section: This logic should moved to hooks/framebuffer as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: initramfs-tools (Ubuntu) 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Do you still experience that error? Can you reproduce it? ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- 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/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 814489] Re: package bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 881028 package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full filesystem ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- 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/814489 Title: package bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bcmwl package in Ubuntu: Confirmed Bug description: Upgrading system from USB stick -ubuntu natty ProblemType: Package DistroRelease: Ubuntu 11.04 Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Fri Jul 22 11:01:10 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/814489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 825000] Re: package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug is no longer a duplicate of bug 881028
package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full
filesystem
** This bug has been marked a duplicate of bug 798414
update-initramfs should produce a more helpful error message when there
isn't enough free space--or provide an automatic tool for removal of old files
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/825000
Title:
package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 2
Status in linux package in Ubuntu:
Confirmed
Bug description:
Ubuntu version 10.04.3
Installed on Flash drive using software from pendrivelinux.com
After installation, performing an update from
System>Administration>Update Manager, led to this error message.
Problem can be reproduced when running "sudo apt-get upgrade" in
terminal. Please refer below for full error information in terminal:
ubuntu@ubuntu:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up linux-image-2.6.32-33-generic (2.6.32-33.72) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-33-generic
lzma: Encoder error: -2147467259
Failed to create initrd image.
dpkg: error processing linux-image-2.6.32-33-generic (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.32-33-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
ubuntu@ubuntu:~$
result of running "cat /proc/version_signature" :
Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
please find attached result of running "sudo lspci -vnvn"
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-33-generic 2.6.32-33.72
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3833 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfeaf8000 irq 22'
Mixer name : 'Intel G45 DEVCTG'
Components : 'HDA:10ec0888,10ec0888,0011
HDA:80862802,80860101,0010'
Controls : 20
Simple ctrls : 11
Date: Fri Aug 12 14:14:03 2011
ErrorMessage: subprocess installed post-installation script returned error
exit status 2
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
LiveMediaBuild: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz splash
-- BOOT_IMAGE=/casper/vmlinuz
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
SourcePackage: linux
Title: package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to
install/upgrade: subprocess installed post-installation script returned error
exit status 2
dmi.bios.date: 05/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/27/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825000/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 889552] Re: package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de err
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug is no longer a duplicate of bug 881028
package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full
filesystem
** This bug has been marked a duplicate of bug 798414
update-initramfs should produce a more helpful error message when there
isn't enough free space--or provide an automatic tool for removal of old files
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/889552
Title:
package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to
install/upgrade: el subproceso instalado el script post-installation
devolvió el código de salida de error 2
Status in linux package in Ubuntu:
Confirmed
Bug description:
none
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-12-generic 2.6.38-12.51
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No existe el fichero o el directorio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xde30 irq 46'
Mixer name : 'Realtek ALC861-VD'
Components : 'HDA:10ec0862,1179010c,0011
HDA:11c11040,11790001,00100200'
Controls : 16
Simple ctrls : 10
Date: Sat Nov 12 13:47:05 2011
ErrorMessage: el subproceso instalado el script post-installation devolvió el
código de salida de error 2
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: TOSHIBA Satellite A200
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed
boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
linux-backports-modules-2.6.38-8-generic N/A
linux-firmware1.52
SourcePackage: linux
Title: package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to
install/upgrade: el subproceso instalado el script post-installation devolvió
el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.80
dmi.board.name: ISKAE
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnTOSHIBA:bvrV1.80:bd08/21/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAECE-01100KSP:rvnTOSHIBA:rnISKAE:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite A200
dmi.product.version: PSAECE-01100KSP
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889552/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 896646] Re: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 881028 package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full filesystem ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/896646 Title: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in b43-fwcutter package in Ubuntu: New Bug description: Trying to intall 10.04 LTS on Apple Mac G5 that has OS X already on it. I wanted the OS X to be deleted and all the disk reserved for Ubuntu ProblemType: Package DistroRelease: Ubuntu 10.04 Package: b43-fwcutter (not installed) ProcVersionSignature: Ubuntu 2.6.32-21.32-powerpc64-smp 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-powerpc64-smp ppc64 AptOrdering: b43-fwcutter: Install b43-fwcutter: Configure Architecture: powerpc Date: Sat Nov 26 17:58:25 2011 ErrorMessage: subprocess new pre-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release powerpc (20100428) SourcePackage: b43-fwcutter Title: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/896646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
initramfs-tools 0.142ubuntu15.1 debdiff for mantic attached. ** Description changed: + [ Impact ] + With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. - - -- + [ Test Plan ] + + The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' + + After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' + usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst + usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst + + Test case on Microsoft Surface Laptop 4: Remove all previous + workarounds. Install the fixed initramfs-tools version. Then the + keyboard should work during boot to enter the passphrase. + + [ Where problems could occur ] + + This is making the initramfs slightly bigger. In my testing, both added + were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). + + [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: - adduser 3.118ubuntu5 - apt 2.4.8 - apt-utils 2.4.8 - busybox-initramfs 1:1.30.1-7ubuntu3 - ca-certificates 20211016ubuntu0.22.04.1 - coreutils 8.32-4.1ubuntu1 - cpio 2.13+dfsg-7 - debconf 1.5.79ubuntu1 - debconf-i18n 1.5.79ubuntu1 - dmsetup 2:1.02.175-2.1ubuntu4 - dpkg 1.21.1ubuntu2.1 - gcc-12-base 12.1.0-2ubuntu1~22.04 - gettext-base 0.21-4ubuntu4 - gpgv 2.2.27-3ubuntu2.1 - grub-common 2.06-2ubuntu7.1 - grub-gfxpayload-lists 0.7 - grub-pc 2.06-2ubuntu7.1 - grub-pc-bin 2.06-2ubuntu7.1 - grub2-common 2.06-2ubuntu7.1 - init-system-helpers 1.62 - initramfs-tools 0.140ubuntu13.1 - initramfs-tools-bin 0.140ubuntu13.1 - initramfs-tools-core 0.140ubuntu13.1 - klibc-utils 2.0.10-4 - kmod 29-1ubuntu1 - libacl1 2.3.1-1 - libapt-pkg6.0 2.4.8 - libattr1 1:2.5.1-1build1 - libaudit-common 1:3.0.7-1build1 - libaudit1 1:3.0.7-1build1 - libblkid1 2.37.2-4ubuntu3 - libbrotli1 1.0.9-2build6 - libbz2-1.0 1.0.8-5build1 - libc6 2.35-0ubuntu3.1 - libcap-ng0 0.7.9-2.2build3 - libcap2 1:2.44-1build3 - libcom-err2 1.46.5-2ubuntu1.1 - libcrypt1 1:4.4.27-1 - libdb5.3 5.3.28+dfsg1-0.8ubuntu3 - libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 - libefiboot1 37-6ubuntu2 - libefivar1 37-6ubuntu2 - libffi8 3.4.2-4 - libfreetype6 2.11.1+dfsg-1ubuntu0.1 - libfuse3-3 3.10.5-1build1 - libgcc-s1 12.1.0-2ubuntu1~22.04 - libgcrypt20 1.9.4-3ubuntu3 - libgmp10 2:6.2.1+dfsg-3ubuntu1 - libgnutls30 3.7.3-4ubuntu1.1 - libgpg-error0 1.43-3 - libgssapi-krb5-2 1.19.2-2ubuntu0.1 - libhogweed6 3.7.3-1build2 - libidn2-0 2.3.2-2build1 - libk5crypto3 1.19.2-2ubuntu0.1 - libkeyutils1 1.6.1-2ubuntu3 - libklibc 2.0.10-4 - libkmod2 29-1ubuntu1 - libkrb5-3 1.19.2-2ubuntu0.1 - libkrb5support0 1.19.2-2ubuntu0.1 - liblocale-gettext-perl 1.07-4build3 - liblz4-1 1.9.3-2build2 - liblzma5 5.2.5-2ubuntu1 - libmount1 2.37.2-4ubuntu3 - libnettle8 3.7.3-1build2 - libnsl2 1.3.0-2build2 - libp11-kit0 0.24.0-6build1 - libpam-modules 1.4.0-11ubuntu2.3 - libpam-modules-bin 1.4.0-11ubuntu2.3 - libpam0g 1.4.0-11ubuntu2.3 - libpcre2-8-0 10.39-3ubuntu0.1 - libpng16-16 1.6.37-3build5 - libseccomp2 2.5.3-2ubuntu2 - libselinux1 3.3-1build2 - libsemanage-common 3.3-1build2 - libsemanage2 3.3-1build2 - libsepol2 3.3-1build1 - libsmartcols1 2.37.2-4ubuntu3 - libssl3 3.0.2-0ubuntu1.8 - libstdc++6 12.1.0-2ubuntu1~22.04 - libsystemd0 249.11-0ubuntu3.6 - libtasn1-6 4.18.0-4build1 - libtext-charwidth-perl 0.04-10build3 - libtext-iconv-perl 1.7-7build3 - libtext-wrapi18n-perl 0.06-9 - libtinfo6 6.3-2 - libtirpc-common 1.3.2-2ubuntu0.1 - libtirpc3 1.3.2-2ubuntu0.1 - libudev1 249.11-0ubuntu3.6 - libunistring2 1.0-1 - libuuid1 2.37.2-4ubuntu3 - libxxhash0 0.8.1-1 - libzstd1 1.4.8+dfsg-3build1 - linux-base 4.5ubuntu9 - linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 - logsave 1.46.5-2ubuntu1.1 - lsb-base 11.1.0ubuntu4 - mount
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
** Also affects: initramfs-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: New Status in linux source package in Mantic: Invalid Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 7 vendor_id: GenuineIntel cpu family : 6 model: 140 model name : 11th
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
Forwarded adding surface_aggregator_registry to dracut: https://github.com/dracutdevs/dracut/pull/2558 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 7 vendor_id: GenuineIntel cpu family : 6 model: 140
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
I checked the included modules on Ubuntu 23.10 (linux 6.5.0-10-generic) and following modules are included: 8250_dw pinctrl_tigerlake (pinctrl-tigerlake.ko) surface_aggregator surface_hid surface_hid_core Following modules are not included, but will be included by the fix for bug #2042710: intel_lpss intel_lpss_pci Following module needs to be included (also dracut is affected): surface_aggregator_registry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days
[Kernel-packages] [Bug 2018128] Re: Apport does not collect all logs when the package is HWE kernel
I discussed this topic with Simon and we came up with a less fragile solution: Each kernel binary package can ship a symlink to /usr/share/apport/package-hooks/source_linux.py. Example: linux- image-5.19.0-50-generic should ship /usr/share/apport/package- hooks/linux-image-5.19.0-50-generic.py -> source_linux.py This will work without a regular expression that will break sooner or later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: Fix Released Status in maas-images: Fix Released Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Fix Released Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-unsigned package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in grub2 source package in Focal:
Invalid
Status in grub2-unsigned source package in Focal:
Invalid
Status in linux source package in Focal:
Invalid
Status in grub2 source package in Jammy:
Invalid
Status in grub2-unsigned source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in grub2 source package in Lunar:
Invalid
Status in grub2-unsigned source package in Lunar:
Invalid
Status in linux source package in Lunar:
Invalid
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
* check that grub and EFI based ARM64 machines boot
* check that MAAS deployment works
[Where problems could occur]
* Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using
piboot, u-boot, abootimg likely one still wants to build Image.gz and have
CONFIG_EFI_ZBOOT disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in strace source package in Kinetic: Won't Fix Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018128] Re: Apport does not collect all logs when the package is HWE kernel
The source_linux.py package hook could be moved to general-hooks (where it is always run) and do a regular expression check for the source package name. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018128] Re: Apport does not collect all logs when the package is HWE kernel
Can you test with including the version number in the link name? /usr/share/apport/package-hooks/source_linux-signed-hwe-5.19.py -> source_linux.py -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
** Description changed: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html + + See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- + the-generation-in-ubuntu-23-10/38972 for the performance evaluation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: Fix Released Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- the-generation-in-ubuntu-23-10/38972 for the performance evaluation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037400] [NEW] nvidia drivers not included in initramfs
Public bug reported:
/usr/share/initramfs-tools/hooks/framebuffer-nvidia looks only for *.ko
modules:
```
copy_modules_dir_filter()
{
[...]
for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko"
-print); do
manual_add_modules $(basename ${kmod} .ko)
done
}
```
But the kernel modules are zstd compressed on mantic:
```
# ls /lib/modules/6.5.0-5-generic/updates/dkms/ -1
nvidia-drm.ko.zst
nvidia-modeset.ko.zst
nvidia-peermem.ko.zst
nvidia-uvm.ko.zst
nvidia.ko.zst
```
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Critical
Status: New
** Affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
Importance: Critical
Status: New
** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
Importance: Critical
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2037400
Title:
nvidia drivers not included in initramfs
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 source package in Mantic:
New
Bug description:
/usr/share/initramfs-tools/hooks/framebuffer-nvidia looks only for
*.ko modules:
```
copy_modules_dir_filter()
{
[...]
for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name
"$pattern*.ko" -print); do
manual_add_modules $(basename ${kmod} .ko)
done
}
```
But the kernel modules are zstd compressed on mantic:
```
# ls /lib/modules/6.5.0-5-generic/updates/dkms/ -1
nvidia-drm.ko.zst
nvidia-modeset.ko.zst
nvidia-peermem.ko.zst
nvidia-uvm.ko.zst
nvidia.ko.zst
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037400/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037305] [NEW] installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1
Public bug reported: Installing nvidia-driver-535 in a minimal schroot environment fails: ``` $ schroot-wrapper -p linux-headers-generic,linux-image-generic,initramfs-tools,zstd,xserver-xorg-core -c mantic -u root (mantic)root@host:~# apt-get install --no-install-recommends nvidia-driver-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: cpp-12 dkms gcc-12 gcc-12-base libgcc-12-dev libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-decode-535 libnvidia-encode-535 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-gl-535 lsb-release nvidia-compute-utils-535 nvidia-dkms-535 nvidia-firmware-535-535.104.05 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 Suggested packages: gcc-12-locales cpp-12-doc menu gcc-12-multilib gcc-12-doc Recommended packages: sudo nvidia-settings nvidia-prime libnvidia-compute-535:i386 libnvidia-decode-535:i386 libnvidia-encode-535:i386 libnvidia-fbc1-535:i386 libnvidia-gl-535:i386 The following NEW packages will be installed: cpp-12 dkms gcc-12 gcc-12-base libgcc-12-dev libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-decode-535 libnvidia-encode-535 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-gl-535 lsb-release nvidia-compute-utils-535 nvidia-dkms-535 nvidia-driver-535 nvidia-firmware-535-535.104.05 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. Need to get 359 MB of archives. After this operation, 924 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 lsb-release all 12.0-2 [6564 B] Get:2 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12-base amd64 12.3.0-9ubuntu1 [43.5 kB] Get:3 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 cpp-12 amd64 12.3.0-9ubuntu1 [10.7 MB] Get:4 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 libgcc-12-dev amd64 12.3.0-9ubuntu1 [2574 kB] Get:5 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12 amd64 12.3.0-9ubuntu1 [21.6 MB] Get:6 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 dkms all 3.0.11-1ubuntu10 [51.3 kB] Get:7 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-cfg1-535 amd64 535.104.05-0ubuntu4 [108 kB] Get:8 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-common-535 all 535.104.05-0ubuntu4 [15.4 kB] Get:9 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-compute-535 amd64 535.104.05-0ubuntu4 [40.2 MB] Get:10 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-decode-535 amd64 535.104.05-0ubuntu4 [1886 kB] Get:11 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-encode-535 amd64 535.104.05-0ubuntu4 [97.4 kB] Get:12 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-extra-535 amd64 535.104.05-0ubuntu4 [72.0 kB] Get:13 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-fbc1-535 amd64 535.104.05-0ubuntu4 [55.6 kB] Get:14 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-gl-535 amd64 535.104.05-0ubuntu4 [194 MB] Get:15 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-compute-utils-535 amd64 535.104.05-0ubuntu4 [122 kB] Get:16 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-kernel-source-535 amd64 535.104.05-0ubuntu4 [45.0 MB] Get:17 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-firmware-535-535.104.05 amd64 535.104.05-0ubuntu4 [39.5 MB] Get:18 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-kernel-common-535 amd64 535.104.05-0ubuntu4 [209 kB] Get:19 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-dkms-535 amd64 535.104.05-0ubuntu4 [35.9 kB] Get:20 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-utils-535 amd64 535.104.05-0ubuntu4 [403 kB] Get:21 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 xserver-xorg-video-nvidia-535 amd64 535.104.05-0ubuntu4 [1587 kB] Get:22 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-driver-535 amd64 535.104.05-0ubuntu4 [484 kB] Fetched 359 MB in 1s (301 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package lsb-release. (Reading database ... 53239 files and directories currently installed.) Preparing to unpack .../lsb-release_12.0-2_all.deb ... Unpacking lsb-release (12.0-2) ... Selecting previously unselected package gcc-12-base:amd64. Preparing to unpack .../gcc-12-base_12.3.0-9ubuntu1_amd64.deb ... Unpacking gcc-12-base:amd64 (12.3.0-9ubuntu1) ... Selecting previously unselected package cpp-12. Preparing to unpack .../cpp-12_12.3.0-9ubuntu1_amd64.deb ... Unpacking
[Kernel-packages] [Bug 2012992] Re: kernel-5.19.0-38 battery charge fails
Thank you for taking the time to report this bug and helping to make Ubuntu better. I re-assigned your bug report against the linux package. ** Package changed: initramfs-tools (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/2012992 Title: kernel-5.19.0-38 battery charge fails Status in linux package in Ubuntu: Incomplete Bug description: I just installed linux-image-5.19.0-38 on my HP ProBook 640 G2 with Ubuntu-22.0.4LTS and my battery no longer charges. Battery reports 77% charge, but "pending charge." Leaving it connected to charger give no change in charge status. Booting to Windows-10 shows charge at 77%, status charging, and charge report increasing as expected. Reverting to kernel-5.15.0-69 shows 76% charge, status "charging." john@stolat:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Hewlett-Packard model:Primary serial: 36600 2017/12/20 power supply: yes updated: Mon 27 Mar 2023 08:18:01 PM CDT (114 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 31.1106 Wh energy-empty:0 Wh energy-full: 40.5954 Wh energy-full-design: 48.0168 Wh energy-rate: 0 W voltage: 12.15 V charge-cycles: 57 percentage: 76% capacity:84.5442% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
Then setting ZSTD_CLEVEL in debian/scripts/install-firmware should do
the trick (needs testing!):
ZSTD_CLEVEL=19 ./copy-firmware.sh --zstd "${staging_dir}"
--
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/1942260
Title:
compress firmware in /lib/firmware
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
Confirmed
Bug description:
-- initramfs-tools
[Impact]
* linux supports xz compressed linux-firmware which saves disk space.
In focal, initramfs-tools only knows how to included uncompressed
firmware files (even when kernel supports loading compressed ones).
Newer releases of linux-firmware may use compressed firmware files
only, in such cases it would be nice for focal's initramfs-tools to
support compressed firmware files in case of partial or incomplete
upgrades (i.e. linux-firmware force installed or upgraded, without
newer initramfs-tools). The proposed changes to initramfs-tools are
backwards and forwards compatible, they prefer to include uncompressed
firmware files; and if missing, include compressed firmware files in
their uncompressed form. Thus maintaining compatibility with any
kernels, irrespective of compressed/uncompressed firmware inputs.
[Test Plan]
* Compress all files shipped by linux-firmware with xz
* Rebuild initrd
* Check that all the same firmware files are still included in the
initramfs, in their uncompressed form as before
[Where problems could occur]
* This SRU is precautionary to prevent accidental installation of
compressed linux-firmware from generating incorrect initramfs. It
should be noted that whilst initramfs-tools would create a compatible
initramfs with any kernels, pre-v5.3 kernels do not support xz
compressed firmware files at runtime. Mixing this new initramfs with
compressed firmwares and pre 5.3 kernels may lead to expectations of
supporting compressed firmware files with them only working at initrd
stage and not at runtime.
[Other Info]
Original bug report
Some facts:
- The linux kernel has supported loading xz compressed firmware since 5.3
- The size of /lib/firmware in impish is ~650Mb (and growing)
- The compressed size of firmware could be ~230Mb
It would be nice to install compressed firmware to save space.
Here are the plans from the Fedora project:
https://fedoraproject.org/wiki/Changes/CompressKernelFirmware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028550] Re: Backport support to tolerate ZSTD compressed firmware files
** Description changed: [ Impact ] - * To ensure reliable dist-upgrades in case of partial upgrades or + * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. - * Specifically it is being discussed to switch linux-firmware to ZSTD + * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one - * To ensure that failed dist-upgrades can still boot after-partial + * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] - * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD + * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD - * Check that existing firmware files loaded on a given machine can be + * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel - * Check that depmod / initramfs-tools all support .zst compressed + * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] - * Once this is inroduced in jammy-GA kernel it may cripple into focal- + * Once this is inroduced in jammy-GA kernel it may cripple into focal- hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] - - * See https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042652.html + + * See https://lists.ubuntu.com/archives/ubuntu- + devel/2023-July/042652.html and + https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html ** Description changed: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD - compressed one + compressed one (see bug #1942260) * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal- hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028550 Title: Backport support to tolerate ZSTD compressed firmware files Status in linux package in Ubuntu: In Progress Bug description: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one (see bug #1942260) * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal-hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+subscriptions --
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
** Description changed: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- - devel/2023-July/042652.html + devel/2023-July/042652.html and + https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: In Progress Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
Both linux-firmware patches were accepted upstream. Upstream currently does not set a compression level and has no way to specify it. -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700213] Re: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1658352 *** https://bugs.launchpad.net/bugs/1658352 ** This bug is no longer a duplicate of bug 1700211 package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1658352 package initramfs-tools or linux-image-*-generic failed to install/upgrade: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. -- 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/1700213 Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: upgrade failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.11 ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39 Uname: Linux 3.13.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jun 24 09:21:25 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-19 (124 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1700213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658352] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1.
** Package changed: linux-firmware (Ubuntu) => initramfs-tools (Ubuntu) ** Description changed: whenever i try to upgrade my operating system from ubuntu 14.04 to 16.04 error show "could not install initramfs-tools", "could not install linux-firmware" and "could not install linux-image-4.4.0-59-generic" and te upgrade is failed show could not install upgrade + + From the dpkg terminal log, the error that's occurring is: + + Processing triggers for initramfs-tools (0.103ubuntu4.7) ... + update-initramfs: Generating /boot/initrd.img-3.13.0-108-generic + E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. + update-initramfs: failed for /boot/initrd.img-3.13.0-108-generic with 1. + dpkg: error processing package initramfs-tools (--configure): +subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Sat Jan 21 23:52:45 2017 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-trusty-amd64-20140620-0 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-14 (7 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: - dpkg 1.17.5ubuntu5.7 - apt 1.0.1ubuntu2.17 + dpkg 1.17.5ubuntu5.7 + apt 1.0.1ubuntu2.17 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-01-21 (0 days ago) -- 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/1658352 Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Status in initramfs-tools package in Ubuntu: Invalid Bug description: whenever i try to upgrade my operating system from ubuntu 14.04 to 16.04 error show "could not install initramfs-tools", "could not install linux-firmware" and "could not install linux- image-4.4.0-59-generic" and te upgrade is failed show could not install upgrade From the dpkg terminal log, the error that's occurring is: Processing triggers for initramfs-tools (0.103ubuntu4.7) ... update-initramfs: Generating /boot/initrd.img-3.13.0-108-generic E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-108-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Sat Jan 21 23:52:45 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-14 (7 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1658352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
All kernels need to support reading the compressed firmware files (even after partial upgrades). See bug #2028550 for the kernel side. linux-firmware needs two patches to correctly produce compressed firmware files: * https://lore.kernel.org/linux-firmware/1addfae3b9a376ebbf39c0d05642394ebcfb9ee9.ca...@canonical.com/T/#u * https://lore.kernel.org/linux-firmware/c151f7d4837d3a07143ee5191d3f5e57bc6ded2c.ca...@canonical.com/T/#u Attached a tested debdiff that could be uploaded once following points are addressed: * support for zstd compressed firmware files in initramfs-tools (should be in 0.142ubuntu8) * support for zstd compressed firmware in all relevant kernels (see bug #2028550) * a "Breaks: initramfs-tools (<< 0.142ubuntu8~)" for the final uploaded version should be added ** Patch added: "linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1942260/+attachment/5688141/+files/linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
We have a bunch of bugs to decrease initramfs size and to make it faster: * bug #2028567: initramfs-tools: Do not re-compress compressed kernel modules and firmware files * bug #2028568: Ship kernel modules compressed * bug #1942260: compress firmware in /lib/firmware * bug #2028571: klibc-utils contains identical binaries * bug #2028574: Duplicate firmware files in /lib/firmware This started on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028574] [NEW] Duplicate firmware files in /lib/firmware
Public bug reported: linux-firmware ships firmware files that are identical/duplicates: ``` $ fdupes -rm /lib/firmware/ 341 duplicate files (in 195 sets), occupying 37.1 megabytes ``` Please patch the source package and replace the duplicates by symlinks. Alternatively run jdupes during build, but then ensure that the resulting symlinks are stable. This will reduce the initramfs size especially after compressing firmware files (bug #1942260) and putting compressed files in an uncompressed cpio archive (bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html Some upstream discussion: https://lore.kernel.org/linux- firmware/20230331115739.bytw7s35aacgr...@notk.org/ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:18:24 2023 Dependencies: firmware-sof-signed 2.2.4-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=f9311d7a-cbb8-43f1-b2cd-38c98ae92b9e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux-firmware UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) dmi.bios.date: 07/20/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F16e dmi.board.asset.tag: Default string dmi.board.name: B550I AORUS PRO AX dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16e:bd07/20/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550IAORUSPROAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550IAORUSPROAX:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550I AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Duplicate firmware files + Duplicate firmware files in /lib/firmware -- 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/2028574 Title: Duplicate firmware files in /lib/firmware Status in linux-firmware package in Ubuntu: New Bug description: linux-firmware ships firmware files that are identical/duplicates: ``` $ fdupes -rm /lib/firmware/ 341 duplicate files (in 195 sets), occupying 37.1 megabytes ``` Please patch the source package and replace the duplicates by symlinks. Alternatively run jdupes during build, but then ensure that the resulting symlinks are stable. This will reduce the initramfs size especially after compressing firmware files (bug #1942260) and putting compressed files in an uncompressed cpio archive (bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html Some upstream discussion: https://lore.kernel.org/linux- firmware/20230331115739.bytw7s35aacgr...@notk.org/ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:18:24 2023 Dependencies: firmware-sof-signed 2.2.4-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=f9311d7a-cbb8-43f1-b2cd-38c98ae92b9e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules compressed
Attached a tested patch for zstd -19 compression. ** Patch added: "0001-UBUNTU-Compress-kernel-modules-with-zst-19.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+attachment/5688115/+files/0001-UBUNTU-Compress-kernel-modules-with-zst-19.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028568 Title: Ship kernel modules compressed Status in linux package in Ubuntu: New Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] [NEW] Ship kernel modules compressed
Public bug reported: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html ** 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/2028568 Title: Ship kernel modules compressed Status in linux package in Ubuntu: New Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522327] Re: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 1522501 package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522327 Title: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: cd/dvd player dont read the discs device its working properly ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-71-generic 3.13.0-71.114 ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26 Uname: Linux 3.13.0-64-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoe1670 F pulseaudio /dev/snd/seq:timidity 1284 F timidity Date: Thu Dec 3 10:44:45 2015 DuplicateSignature: package:linux-image-3.13.0-71-generic:3.13.0-71.114:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8685940b-7d7e-4e26-a120-317e39c21913 InstallationDate: Installed on 2015-08-08 (116 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP Compaq dx6120 MT(EP691ES) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.5 SourcePackage: linux Title: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786C2 v01.06 dmi.board.name: 09CCh dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC6120B30 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786C2v01.06:bd04/05/2005:svnHewlett-Packard:pnHPCompaqdx6120MT(EP691ES):pvr:rvnHewlett-Packard:rn09CCh:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dx6120 MT(EP691ES) dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553750] Re: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
*** This bug is a duplicate of bug 1532355 *** https://bugs.launchpad.net/bugs/1532355 ** This bug is no longer a duplicate of bug 1547505 package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth ** This bug has been marked a duplicate of bug 1532355 package linux-image-4.3.0-5-generic 4.3.0-5.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1553750 Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in linux-meta package in Ubuntu: New Bug description: upgrading from 15.10 with latest update software ( after do a apt-get update && sudo apt-get upgrade). I got 5 or more errors in sequence. I'll try to install manually other kernel. probably same bug as: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553744 and https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553749 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.10.11 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zhe1403 F pulseaudio /dev/snd/controlC0: zhe1403 F pulseaudio /dev/snd/controlC2: zhe1403 F pulseaudio Date: Sun Mar 6 12:37:12 2016 ErrorMessage: dependency problems - leaving unconfigured HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e InstallationDate: Installed on 2016-03-06 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7900 ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-meta Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 01/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G45 GAMING (MS-7900) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7900 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1553750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553750] Re: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
*** This bug is a duplicate of bug 1547505 *** https://bugs.launchpad.net/bugs/1547505 ** This bug is no longer a duplicate of bug 1553744 package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 ** This bug has been marked a duplicate of bug 1547505 package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1553750 Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in linux-meta package in Ubuntu: New Bug description: upgrading from 15.10 with latest update software ( after do a apt-get update && sudo apt-get upgrade). I got 5 or more errors in sequence. I'll try to install manually other kernel. probably same bug as: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553744 and https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553749 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.10.11 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zhe1403 F pulseaudio /dev/snd/controlC0: zhe1403 F pulseaudio /dev/snd/controlC2: zhe1403 F pulseaudio Date: Sun Mar 6 12:37:12 2016 ErrorMessage: dependency problems - leaving unconfigured HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e InstallationDate: Installed on 2016-03-06 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7900 ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-meta Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 01/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G45 GAMING (MS-7900) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7900 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1553750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
Thanks. I have uploaded thermald 2.4.9-1ubuntu0.3 jammy with a small change and unsubscribed ~ubuntu-sponsors. I added "Cherry-pick following fixes from thermald 2.5.1 and 2.5.2 (LP: #1995606)" to d/changelog since this bug was not referenced. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018128] Re: Apport does not collect all logs when the package is HWE kernel
The kernel package has an exception. The apport package ships the source_linux.py hooks and several symlinks: ``` $ ls -l /usr/share/apport/package-hooks/source_linux* lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-firmware.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-meta-oem.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-meta.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-meta-raspi.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-oem-osp1.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-oem.py -> source_linux.py -rw-r--r-- 1 root root 6523 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-signed-oem.py -> source_linux.py lrwxrwxrwx 1 root root 15 Apr 14 00:17 /usr/share/apport/package-hooks/source_linux-signed.py -> source_linux.py ``` How is the HWE kernel package named? Can you try to add a symlink for the source package name to see if that solves your issue? ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019247] Re: perf should be compiled with libtraceevent
** 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/2019247 Title: perf should be compiled with libtraceevent Status in linux package in Ubuntu: Confirmed Bug description: libtraceevent was removed from the kernel tree in https://lore.kernel.org/lkml/20221130062935.2219247-1-irog...@google.com/. The linux-tools-6.2.0-20-generic I have in Lunar doesn't not use compile perf against libtraceevent, making perf unable to record traceevents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019247] [NEW] perf should be compiled with libtraceevent
Public bug reported: libtraceevent was removed from the kernel tree in https://lore.kernel.org/lkml/20221130062935.2219247-1-irog...@google.com/. The linux-tools-6.2.0-20-generic I have in Lunar doesn't not use compile perf against libtraceevent, making perf unable to record traceevents. ** 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/2019247 Title: perf should be compiled with libtraceevent Status in linux package in Ubuntu: New Bug description: libtraceevent was removed from the kernel tree in https://lore.kernel.org/lkml/20221130062935.2219247-1-irog...@google.com/. The linux-tools-6.2.0-20-generic I have in Lunar doesn't not use compile perf against libtraceevent, making perf unable to record traceevents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641859] Re: perf compiled without auxtrace
Seems intel_pt works now on 23.04. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641859 Title: perf compiled without auxtrace Status in linux package in Ubuntu: Fix Released Bug description: perf in linux-tools-common_4.8.0-27.29 seems to be compiled without auxtrace support. This prevents perf from using Intel Processor Trace (PT) or Branch Trace Store (BTS). Unfortunately, rather than indicating that auxtrace is missing, perf just records no samples: # grep -c intel_pt /proc/cpuinfo 8 # perf list | grep intel_pt # grep intel_pt /proc/cpuinfo # perf record -e intel_pt// -- ls ... # perf script I am able to successfully to use PT on my machine if I compile perf myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files (on log-out)
Added package version to the description (apport-collect does not allow me to collect the data since I am not the original reporter). ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. + + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + DistroRelease: Ubuntu 23.04 + Package: linux-image-6.2.0-20-generic 6.2.0-20.20 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6278216c-6f7c-4a94-8eab-e9c43da65227 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 ** 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/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6278216c-6f7c-4a94-8eab-e9c43da65227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 To manage notifications about
[Kernel-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files (on log-out)
This behavior is only noticeable on log-out. Killing gnome-shell works. I am using the 0001-apport-Write-coredump-at-beginning-and-quit.patch with a delay of 0.005s: ``` $ killall -11 gnome-shell $ tail /var/log/apport.log ERROR: apport (pid 15107) 2023-04-19 13:53:03,089: called for pid 14206, signal 11, core limit 0, dump mode 1 WARNING: apport (pid 15107) 2023-04-19 13:53:57,167: Wrote 639,475,712 bytes of core to /var/lib/apport/coredump/core._usr_bin_gnome-shell.1000.af6fdb2c-b9ba-4eeb-8727-683ac2247576.14206.5881189 $ gdb /usr/bin/gnome-shell /var/lib/apport/coredump/core._usr_bin_gnome-shell.1000.* ``` The 639 MB were successful written and that took 54 seconds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files
Note: Apport triggers this behavior, because it compresses the core dump and base64 encodes the compressed result. That increases the time to read the coredump file. In addition apport also takes some time to collect the crash information. ** Summary changed: - Repeatedly unusable truncated crash files + Repeatedly unusable truncated crash files (on log-out) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files
One day of debugging gave more insight. Apport is not directly the culprit. If reading from stdin takes too long, the input will be truncated. Attached a patch for apport to write the coredump at the beginning and quit. It can be slowed down by sleeping between the 1 MB blocks. The longer the sleep, the smaller the files get. For my VM: sleeping for 0.001s truncates the file slightly to ~400 MB; sleeping 0.005s truncates it to 42 MB. I verified that /proc/ is still there afterwards. So I would say that the kernel team should have a look next. ** Patch added: "0001-apport-Write-coredump-at-beginning-and-quit.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5665206/+files/0001-apport-Write-coredump-at-beginning-and-quit.patch ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" + + Steps to reproduce + == + + 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell + + 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) + + 3. Remove all crashes: `sudo rm -f /var/crash/*` + + 4. Interact with the desktop, icon grid and calendar for 30 seconds. + + 5. Log out. + + 6. Crash files written. + + To test the core file, either use `apport-unpack` on the + /var/crash/*.crash file to extract the CoreDump file or use `apport- + retrace -g` on the .crash file. It will fail to print the backtrace: + + ``` + $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash + [...] + Warnung: Error reading shared library list entry at 0x646c7472 + Failed to read a valid object file image from memory. + Core was generated by `/usr/bin/gnome-shell'. + Program terminated with signal SIGSEGV, Segmentation fault. + Warnung: Section `.reg-xstate/10527' in core file too small. + (gdb) bt + #0 0x7fe1c8090ffb in ?? () + Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 + ``` ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` + + You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch + on apport to only write the coredump and adjust the slowdown to 100% + reproduce the behavior on log-out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
With some help (https://gitlab.freedesktop.org/drm/intel/-/issues/4813), I finally found a better workaround than the "nomodeset" kernel parameter : replace it by "i915.enable_psr=0". See https://gitlab.freedesktop.org/drm/intel/-/issues/4813 for details. For me, all seem works well now (including suspend on RAM/disk and with/without my DisplayLink USB-C dock). ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4813 https://gitlab.freedesktop.org/drm/intel/-/issues/4813 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
With some help (https://gitlab.freedesktop.org/drm/intel/-/issues/4813), I finally found a better workaround than the "nomodeset" kernel parameter : replace it by "i915.enable_psr=0". See https://gitlab.freedesktop.org/drm/intel/-/issues/4813 for details. For me, all seem works well now (including suspend on RAM/disk and with/without my DisplayLink USB-C dock). ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4813 https://gitlab.freedesktop.org/drm/intel/-/issues/4813 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
I have exactly the same problem on my Dell Latitude 7390. I also try it with Debian Bullseye and I reproduce this problem. No problem on the original Microsoft Windows installation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832
[Kernel-packages] [Bug 2003075] [NEW] Emulex lpfc driver produces link down
Public bug reported: Hello, with kernel linux-image-5.15.0-52-generic the driver works without problems and with the command "multipath -ll" all san-storages are correctly displayed. With the newer kernels linux- image-5.15.0-57-generic and linux-image-5.15.0-58-generic the command "multipath -ll" does not show the devices anymore. Booting back into the old kernel everything is fine again. In the syslog there are "link up" and "link down" messages for the lpfc driver. The lpfc driver version is "0:14.0.0.4" with every kernel version. Greetings, Benjamin Klusz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 17 11:50 seq crw-rw 1 root audio 116, 33 Jan 17 11:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Tue Jan 17 11:58:56 2023 InstallationDate: Installed on 2022-10-24 (85 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. USB3.0-CRW Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0424:2660 Microchip Technology, Inc. (formerly SMSC) Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M |__ Port 4: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: HPE ProLiant DL380 Gen10 PciMultimedia: ProcEnviron: SHELL=/bin/bash LANG=de_DE.UTF-8 TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 netcfg/do_not_use_netplan=true RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2022 dmi.bios.release: 2.68 dmi.bios.vendor: HPE dmi.bios.version: U30 dmi.board.name: ProLiant DL380 Gen10 dmi.board.vendor: HPE dmi.chassis.type: 23 dmi.chassis.vendor: HPE dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHPE:bvrU30:bd07/14/2022:br2.68:efr2.78:svnHPE:pnProLiantDL380Gen10:pvr:rvnHPE:rnProLiantDL380Gen10:rvr:cvnHPE:ct23:cvr:sku868703-B21: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 Gen10 dmi.product.sku: 868703-B21 dmi.sys.vendor: HPE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003075 Title: Emulex lpfc driver produces link down Status in linux package in Ubuntu: New Bug description: Hello, with kernel linux-image-5.15.0-52-generic the driver works without problems and with the command "multipath -ll" all san-storages are correctly displayed. With the newer kernels linux- image-5.15.0-57-generic and linux-image-5.15.0-58-generic the command "multipath -ll" does not show the devices anymore. Booting back into the old kernel everything is fine again. In the syslog there are "link up" and "link down" messages for the lpfc driver. The lpfc driver version is "0:14.0.0.4" with every kernel version. Greetings, Benjamin Klusz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 17 11:50 seq crw-rw 1 root audio 116, 33 Jan 17 11:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
I have the same issue on a Dell Latitude 5490 running Ubuntu 22.04.1 LTS. The Dell is connected via USB-C to DisplayPort (DisplayPort alt mode) to an external monitor (Dell Alienware aw3821dw). After the screen locks and display went to sleep mode and I return to my desk, the screen always has a resolution of 1024x768 and I can see the following in my syslog: Nov 25 13:05:03 latitude-5490 kernel: [17418.633249] i915 :00:02.0: [drm] *ERROR* failed to enable link training Nov 25 13:04:59 latitude-5490 rtkit-daemon[1842]: message repeated 29 times: [ Supervising 11 threads of 6 processes of 1 users.] Nov 25 13:05:03 latitude-5490 /usr/libexec/gdm-x-session[3009]: (EE) modeset(0): failed to set mode: Invalid argument Nov 25 13:05:03 latitude-5490 /usr/libexec/gdm-x-session[3009]: (EE) modeset(0): failed to set mode: Invalid argument Nov 25 13:05:03 latitude-5490 dbus-daemon[1165]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.100' (uid=1000 pid=3348 comm="/usr/bin/gnome-shell " label="unconfined") Nov 25 13:05:03 latitude-5490 systemd[1]: Starting Fingerprint Authentication Daemon... Nov 25 13:05:03 latitude-5490 dbus-daemon[1165]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 25 13:05:03 latitude-5490 systemd[1]: Started Fingerprint Authentication Daemon. Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (EE) modeset(0): failed to set mode: Invalid argument Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (WW) modeset(0): hotplug event: connector 112's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): EDID vendor "DEL", prod id 41343 Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Using hsync ranges from config file Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Using vrefresh ranges from config file Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Printing DDC gathered Modelines: Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Modeline "3840x1600"x0.0 397.40 3840 3888 3920 4000 1600 1603 1608 1656 +hsync -vsync (99.3 kHz eP) Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Modeline "3840x1600"x0.0 566.25 3840 3888 3920 4000 1600 1603 1608 1666 +hsync -vsync (141.6 kHz e) Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Nov 25 13:05:04 latitude-5490 /usr/libexec/gdm-x-session[3009]: (EE) modeset(0): failed to set mode: Invalid argument Nov 25 13:05:04 latitude-5490 gnome-shell[3348]: Failed to use stored monitor configuration: Invalid mode 3840x1600 (59,993961) for monitor 'DEL Dell AW3821DW' Linux latitude-5490 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left
[Kernel-packages] [Bug 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package
libnvme 1.2-2 is now in Ubuntu 23.04 (lunar). ** Package changed: linux (Ubuntu) => libnvme (Ubuntu) ** Changed in: libnvme (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package Status in libnvme package in Ubuntu: Fix Released Status in libnvme source package in Jammy: Confirmed Bug description: Upstream (Keith Busch) has started to revive libnvme with the hope of having nvme-cli use libnvme in future. New features like CDC client will be developed on libnvme. Upstream plans are to make libnvme a standalone package that other projects would depend on. We request that Ubuntu 22.04 carry the new libnvme package. https://github.com/linux-nvme/libnvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnvme/+bug/1948636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Is there any expectation of X1 Gen 10 being supported ? It's currently giving the same error as slp110264 above with cheese: $ cheese ../src/intel/isl/isl.c:2220: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available. (cheese:50217): GLib-GObject-CRITICAL **: 17:17:03.292: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed (cheese:50217): GLib-GObject-CRITICAL **: 17:17:03.419: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed (cheese:50217): cheese-WARNING **: 17:17:03.433: Device '/dev/video0' does not support 2:0:0:0 colorimetry: ../sys/v4l2/gstv4l2object.c(4105): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Device wants 2:0:0:0 colorimetry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
initramfs-tools 0.142 added support for specifying the compression
level. Ubuntu will probably merge this version for Ubuntu 23.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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
[Kernel-packages] [Bug 1931790] Re: Unable to mount btrfs RAID 1 filesystem after reboot - Error - device total_bytes should be at most X but found Y
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931790 Title: Unable to mount btrfs RAID 1 filesystem after reboot - Error - device total_bytes should be at most X but found Y Status in btrfs package in Ubuntu: Confirmed Status in btrfs-progs package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm unable to mount my newly created btrfs RAID 1 filesystem after reboot..I performed the below steps with my 2 X 1 TB drives: * created a new btrfs filesystem mkfs.btrfs /dev/sdd1 * mounted it to /mnt/datanew mount -t btrfs /dev/sdd1 /mnt/datanew * copied over data from my previous NTFS volume on /dev/sde1 (which I intended to add later as a mirror) - took 3.5 hrs * added a new volume mkfs.btrfs device add /dev/sde1 * started balance and convert to raid 1 - took 8 to 10 hours..overnight btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/datanew * rebooted next morning I seeing below errors: [ 792.045980] BTRFS info (device sdd1): allowing degraded mounts [ 792.045988] BTRFS info (device sdd1): disk space caching is enabled [ 792.045990] BTRFS info (device sdd1): has skinny extents [ 792.047498] BTRFS error (device sdd1): device total_bytes should be at most 1000201841152 but found 1000203804672 [ 792.049207] BTRFS error (device sdd1): failed to read chunk tree: -22 [ 792.051525] BTRFS error (device sdd1): open_ctree failed * Manual mount has below error additonally mount: /mnt/datanew: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. * Verified the data seems intact (apparently no errors), superblock seems fine.. tried btrfs rescue commands.. no issues found to fix * Found several hits on search but not many solutions..except "btrfs filesystem resize max /" which doesnt work as I'm unable to mount in the first place.. btrfs filesystem resize max /mnt/datanew/ ERROR: not a btrfs filesystem: /mnt/datanew/ Any suggestions? Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.13 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Sun Jun 13 11:17:02 2021 InstallationDate: Installed on 2021-05-16 (27 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/1931790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977680] Re: Cam Link 4K disconnects, kernel warning, OBS video input frozen
** Description changed: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] + This is the third time happening. + ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: tontechnik 2101 F pulseaudio - /dev/snd/controlC0: tontechnik 2101 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: tontechnik 2101 F pulseaudio + /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun 5 11:39:21 2022 InstallationDate: Installed on 2020-08-14 (659 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: - lono wireless extensions. - - enp4s0no wireless extensions. + lono wireless extensions. + + enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS PRO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=182c25dd-5701-40ff-8ac5-e0a623a2204f ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.13.0-39-generic N/A - linux-backports-modules-5.13.0-39-generic N/A - linux-firmware 1.201.5 + linux-restricted-modules-5.13.0-39-generic N/A + linux-backports-modules-5.13.0-39-generic N/A + linux-firmware 1.201.5 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-14 (202 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13g dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550M AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977680 Title: Cam Link 4K disconnects, kernel warning, OBS video input frozen Status in linux package in Ubuntu: New Bug description: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] This is the third time happening. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tontechnik 2101 F pulseaudio /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun
[Kernel-packages] [Bug 1977680] [NEW] Cam Link 4K disconnects, kernel warning, OBS video input frozen
Public bug reported: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] This is the third time happening. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tontechnik 2101 F pulseaudio /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun 5 11:39:21 2022 InstallationDate: Installed on 2020-08-14 (659 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS PRO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=182c25dd-5701-40ff-8ac5-e0a623a2204f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-14 (202 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13g dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550M AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977680 Title: Cam Link 4K disconnects, kernel warning, OBS video input frozen Status in linux package in Ubuntu: New Bug description: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] This is the third time happening. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tontechnik 2101 F pulseaudio /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun 5 11:39:21 2022 InstallationDate: Installed on 2020-08-14 (659 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS PRO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic
[Kernel-packages] [Bug 1722513] Re: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration
Hi!, I was able to fix this by adding the ability to create the netplan yaml files from the hyperv-input. In my case everything works fine. I tested it with 18.04 LTS and 20.04 LTS. It adds .bak the default 01-netcfg.yaml and any previous files for the same interface you want to edit. It creates a seperate yaml-File for each interface when you edit it via the hyperv-host or via scvmm. ** Attachment added: "hv_set_ifconfig" https://bugs.launchpad.net/ubuntu/bionic/+source/linux/+bug/1722513/+attachment/5591510/+files/hv_set_ifconfig -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722513 Title: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Issue description: hv_set_ifconfig does not work due to new netplan configuration Platform: host independent Distribution name and release: Ubuntu 18.04 Kernel version: 4.15+ The hv_set_ifconfig script does not take in consideration netplan config files. Consequently, the changes made by hv_set_ifconfig in /etc/network/interfaces are not affecting the final network configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722513] Re: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration
Is there any update on this? I am on Kernel 5.13.0-1022-azure and linux- cloud-tools-common 5.4.0-109.123 and the script hv_set_ifconfig is only able to manipulate /etc/network/interfaces. Kind Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722513 Title: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Issue description: hv_set_ifconfig does not work due to new netplan configuration Platform: host independent Distribution name and release: Ubuntu 18.04 Kernel version: 4.15+ The hv_set_ifconfig script does not take in consideration netplan config files. Consequently, the changes made by hv_set_ifconfig in /etc/network/interfaces are not affecting the final network configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
And one more tool that might help you get a more reliable repro: https://github.com/HexHive/USBFuzz - likely would need modification to target this specific problem, however. More details here: https://www.usenix.org/conference/usenixsecurity20/presentation/peng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Confirmed Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ? __switch_to_asm+0x34/0x70 [ 943.298616] ? __switch_to_asm+0x40/0x70 [ 943.298617] ksys_ioctl+0x67/0x90 [
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
Ah, I suppose I could try booting off of a Live USB. It'd be a fair amount of effort, but if you're looking for a more reliable test jig, you might try using a Teensy 2.0++ or similar. They've been used in the past for similar purposes (e.g. https://fail0verflow.com/blog/2014/hubcap-chromecast-root-pt1/), as they allow very low-level access to their USB interface. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Confirmed Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ?
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
Unfortunately at the moment I no longer have access to a box that's running Ubuntu (or any linux) on bare metal. I suppose I can give it a try with USB passthrough in a VM over the weekend, perhaps? Also it's been ages since I've built and booted a custom kernel. Does Ubuntu have an easy method for building a patched kernel w/ official config, or is it just like it always was - clone source tree, etc? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Confirmed Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
I wasn't aware that I could change the status of this bug. It's clear to me from the comments above that others have observed it, so I've gone ahead and switched it from "Expired" to "Confirmed." ** Changed in: linux (Ubuntu) Status: Expired => 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/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Confirmed Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ? __switch_to_asm+0x34/0x70 [ 943.298616] ? __switch_to_asm+0x40/0x70 [ 943.298617] ksys_ioctl+0x67/0x90 [
[Kernel-packages] [Bug 1948696] [NEW] Keyboard and trackpad not working
Public bug reported: Unfortunately, neither the keyboard nor the trackpad work after the update to 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benny 1934 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 19:24:35 2021 InstallationDate: Installed on 2021-06-27 (120 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=e33900cf-14d7-4227-b0ea-ca0e9d9a8988 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-20 (5 days ago) dmi.bios.date: 03/10/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd03/10/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601736746:skuSK00:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7410 dmi.product.sku: SK00 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1948696/+attachment/5535951/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948696 Title: Keyboard and trackpad not working Status in linux package in Ubuntu: New Bug description: Unfortunately, neither the keyboard nor the trackpad work after the update to 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benny 1934 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 19:24:35 2021 InstallationDate: Installed on 2021-06-27 (120 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=e33900cf-14d7-4227-b0ea-ca0e9d9a8988 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-20 (5 days ago) dmi.bios.date: 03/10/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd03/10/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601736746:skuSK00:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7410 dmi.product.sku: SK00 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
For me it's the same situation, does not mather if touchpad and or trackpad enabled or disabled in bios, i just get the kernel panic. I've installed debian stable for now to ensure everything works as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900438] Re: Bcache bypass writeback on caching device with fragmentation
** Summary changed:
- Bcache bypasse writeback on caching device with fragmentation
+ Bcache bypass writeback on caching device with fragmentation
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1900438
Title:
Bcache bypass writeback on caching device with fragmentation
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
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
[Impact]
This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10
ms when hitting this issue and would easily be stuck there for hours
or even days, especially bad for ceph on bcache architecture. This
would make ceph extremely slow and make the entire cloud almost
unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the
writeback percent not reached, so it takes ages for bcache to really
reclaim enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and
production data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
threshold, so we only want to give it a little bit push by setting the
term to 1, it means the initial rate will be 170 if the fragment is 6,
it is calculated by bucket_size/fragment, this rate is very small,
but still much more reasonable than the minimum 8.
For a production bcache with non-heavy workload, if the cache device
is bigger than 1 TB, it may take hours to consume 1% buckets,
so it is very possible to reclaim enough dirty buckets in this stage,
thus to avoid entering the next stage.
B. If the dirty buckets ratio didn’t turn around during the first stage,
it comes to the mid stage, then it is necessary for mid stage
to be more aggressive than low stage, so the initial rate is chosen
to be 10 times more than the low stage, which means 1700 as the initial
rate if the fragment is 6. This is a normal rate
we usually see for a normal workload when writeback happens
because of writeback_percent.
C. If the dirty buckets ratio didn't turn around during the low and mid
stages, it comes to the third stage, and it is the last chance that
we can turn around to avoid the horrible cutoff writeback sync issue,
then we choose 100 times more aggressive than the mid stage, that
means 17 as the initial rate if the fragment is 6. This is also
inferred from a production bcache, I've got one week's writeback rate
data from a
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
After installation same situation for me, i've attached a photo of the output. It's really weird: On some boots i am stuck also just at the Lenovo Logo without any more possibillities, on other try of boot, i've got the kernel panic. Even if i disable trackpad and touchpad, but if disabled sometimes the notebooks is booting normal. What seems to work is turn on Notebook, go to BIOS, don't change anything but save with F10 and then reboot. Notebook boots normal without error. But if i turn it off and on again -> kernel panic. ** Attachment added: "PXL_20211008_212338338.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5531687/+files/PXL_20211008_212338338.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I just want to confirm this problem also with impish-proposed kernel, same hardware here and exactly same situation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944998] [NEW] package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package post-installation script sub
Public bug reported: Bug found on system instillation and bootup. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 24 09:00:11 2021 DuplicateSignature: package:linux-image-5.11.0-36-generic:5.11.0-36.40~20.04.1 Setting up linux-image-5.11.0-36-generic (5.11.0-36.40~20.04.1) ... Segmentation fault (core dumped) dpkg: error processing package linux-image-5.11.0-36-generic (--configure): installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 ErrorMessage: installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1944998 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package post- installation script subprocess returned error exit status 139 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Bug found on system instillation and bootup. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 24 09:00:11 2021 DuplicateSignature: package:linux-image-5.11.0-36-generic:5.11.0-36.40~20.04.1 Setting up linux-image-5.11.0-36-generic (5.11.0-36.40~20.04.1) ... Segmentation fault (core dumped) dpkg: error processing package linux-image-5.11.0-36-generic (--configure): installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 ErrorMessage: installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-36-generic package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1944998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
Installed linux 5.4.0-81.91 and verified that it is working. ** Tags removed: verification-needed-focal ** Tags added: 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged 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: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
Installed linux 5.11.0.26.28 and verified that it is working. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged 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: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
focal-proposed has linux 5.4.0-79.88, but this version does not include the patch yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged 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: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
** Description changed: + [Impact] + The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT - Type: Video Capture + Type: Video Capture - [0]: 'NV12' (Y/CbCr 4:2:0) - Size: Discrete 3840x2160 - Interval: Discrete 0.033s (29.970 fps) - [1]: 'NV12' (Y/CbCr 4:2:0) - Size: Discrete 3840x2160 - Interval: Discrete 0.033s (29.970 fps) - [2]: 'YU12' (Planar YUV 4:2:0) - Size: Discrete 3840x2160 - Interval: Discrete 0.033s (29.970 fps) + [0]: 'NV12' (Y/CbCr 4:2:0) + Size: Discrete 3840x2160 + Interval: Discrete 0.033s (29.970 fps) + [1]: 'NV12' (Y/CbCr 4:2:0) + Size: Discrete 3840x2160 + Interval: Discrete 0.033s (29.970 fps) + [2]: 'YU12' (Planar YUV 4:2:0) + Size: Discrete 3840x2160 + Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: - Width/Height : 3840/2160 - Pixel Format : 'NV12' (Y/CbCr 4:2:0) - Field : None - Bytes per Line: 3840 - Size Image: 12441600 - Colorspace: sRGB - Transfer Function : Rec. 709 - YCbCr/HSV Encoding: Rec. 709 - Quantization : Default (maps to Limited Range) - Flags : + Width/Height : 3840/2160 + Pixel Format : 'NV12' (Y/CbCr 4:2:0) + Field : None + Bytes per Line: 3840 + Size Image: 12441600 + Colorspace: sRGB + Transfer Function : Rec. 709 + YCbCr/HSV Encoding: Rec. 709 + Quantization : Default (maps to Limited Range) + Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. + + [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). + [Test Case] + + Connect an input device to the Cam Link 4K and try all three pixel + formats with VLC: + + vlc v4l2:///dev/video0 --v4l2-chroma=NV12 + vlc v4l2:///dev/video0 --v4l2-chroma=YU12 + + [Other Info] + The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work:
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
Thanks for the pointer. I will follow the process documented there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Bug description: The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
** Patch removed: "0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+attachment/5505364/+files/0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch ** Patch added: "v5-0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+attachment/5506449/+files/v5-0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Bug description: The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] [NEW] Pixel format change broken for Elgato Cam Link 4K
Public bug reported: The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Patch added: "0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch" https://bugs.launchpad.net/bugs/1932367/+attachment/5505364/+files/0001-media-uvcvideo-Fix-pixel-format-change-for-Elgato-Ca.patch ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Bug description: The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
The proposed package version is linux-kvm 5.4.0-1040.41 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
