[Kernel-packages] [Bug 1295210] Re: [Apple Inc. MacBookAir5, 2] suspend/resume failure [non-free: wl]
kernel 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux from 13.10 has the same issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295210 Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: crash after closing lid/sleep resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daan 2283 F pulseaudio Date: Thu Mar 20 17:04:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=bb9f9c1a-c3d3-4d2d-8bbe-c76c1010e3e2 InstallationDate: Installed on 2014-03-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=3259c5c0-bdff-4223-a16a-4fa4c775658a 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-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to trusty on 2014-03-17 (3 days ago) UserGroups: dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1295210] [NEW] [Apple Inc. MacBookAir5, 2] suspend/resume failure [non-free: wl]
Public bug reported: crash after closing lid/sleep resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daan 2283 F pulseaudio Date: Thu Mar 20 17:04:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=bb9f9c1a-c3d3-4d2d-8bbe-c76c1010e3e2 InstallationDate: Installed on 2014-03-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=3259c5c0-bdff-4223-a16a-4fa4c775658a 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-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to trusty on 2014-03-17 (3 days ago) UserGroups: dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295210 Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: crash after closing lid/sleep resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daan 2283 F pulseaudio Date: Thu Mar 20 17:04:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=bb9f9c1a-c3d3-4d2d-8bbe-c76c1010e3e2 InstallationDate: Installed on 2014-03-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=3259c5c0-bdff-4223-a16a-4fa4c775658a 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-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to trusty on 2014-03-17 (3 days ago) UserGroups: dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2
[Kernel-packages] [Bug 1295210] Re: [Apple Inc. MacBookAir5, 2] suspend/resume failure [non-free: wl]
kernel-unable-to-test-upstream 3.14.0 rc7 wont boot ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295210 Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: crash after closing lid/sleep resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daan 2283 F pulseaudio Date: Thu Mar 20 17:04:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=bb9f9c1a-c3d3-4d2d-8bbe-c76c1010e3e2 InstallationDate: Installed on 2014-03-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=3259c5c0-bdff-4223-a16a-4fa4c775658a 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-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir5,2] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to trusty on 2014-03-17 (3 days ago) UserGroups: dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 573378] Re: ALC892 not supported in 10.04 default kernel
Hi Christopher, please see my comment from 2010-05-04. Ever since, I
found no more problems related to this issue, up until my current 13.04
install. Best regards, Daan Willems
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/573378
Title:
ALC892 not supported in 10.04 default kernel
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Binary package hint: linux-image-2.6.32-21-generic
The default kernel installed with Ubuntu 10.04 has no full support for
ALC892 Audio chip, available on for example the ASUS P7H55-M Pro
motherboard. Instead, it reverts to a generic intel HD Audio chip,
offering only stereo playback. In alsamixer, only a master, pcm and
iec slider appear. Support for the ALC892 Intel G45 DEVIBX was added
in 2.3.33. A mainline kernel from the kernel ppa (i.e. -
linux-2.6.33-02063303-generic) successfully recognizes the chip and
offers the full range of sliders in alsamixer, offering the intended
5.1/7.1 support. My suggestion is to backport the 2.6.33.x kernel
module for ALC892 to the current 2.6.32 ubuntu kernel to add the
correct support of this chip.
#cat /proc/asound/card0/codec#* | grep Codec
Codec: Realtek ID 892
Codec: Intel G45 DEVIBX
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: d3vlin 1677 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfbdf4000 irq 22'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:10ec0892,10438436,00100302
HDA:80862804,80860101,0010'
Controls : 8
Simple ctrls : 4
Date: Sun May 2 01:41:44 2010
HibernationDevice: RESUME=UUID=1f43f3bb-945c-4686-b783-ee23bcc89d02
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic
root=UUID=f4add25a-22c0-436d-b60d-847acc2dc160 ro quiet splash
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
SourcePackage: linux
dmi.bios.date: 12/30/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7H55-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/573378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828304] Re: QCA6174 slow transfer speeds
I have the same card and experience similar problems. For me downloading is normal, but uploading is significantly slower. I inspected with iperf3 to a ubuntu server on my network. It is interesting to note that increasing the parallel streams increased and eventually saturated the network throughput. The command 'iperf3 -c myserver' yielded: [ 4] 0.00-10.00 sec 15.3 MBytes 12.8 Mbits/sec0 sender [ 4] 0.00-10.00 sec 15.3 MBytes 12.8 Mbits/sec receiver And the command 'iperf3 -P 40 -c daanserver' yielded: [SUM] 0.00-10.00 sec 277 MBytes 232 Mbits/sec 91 sender [SUM] 0.00-10.00 sec 275 MBytes 231 Mbits/sec receiver lshw -class network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 32 serial: 9c:b6:d0:8a:6d:87 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=4.15.0-58-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.0.151 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:132 memory:dc00-dc1f *-network description: Ethernet interface physical id: 2 logical name: enx4865ee185d66 serial: 48:65:ee:18:5d:66 size: 10Mbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.09.9 duplex=half link=no multicast=yes port=MII speed=10Mbit/s -- 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/1828304 Title: QCA6174 slow transfer speeds Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic-updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828304] Re: QCA6174 slow transfer speeds
It seems that this bug was fixed in Ubuntu 20, which is nice :) -- 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/1828304 Title: QCA6174 slow transfer speeds Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic-updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062977] [NEW] Please backport d02c357e5bfa7dfd618b7b3015624beb71f58f1f
Public bug reported: We've been starting to run the systemd integration tests on Github Actions, and noticed a soft lockup in of our VMs: """ [ 245.130625] INFO: task khugepaged:38 blocked for more than 122 seconds. [ 245.131669] Not tainted 6.8.7-arch1-1 #1 [ 245.132371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.134651] INFO: task test-journal-ve:4563 blocked for more than 122 seconds. [ 245.136035] Not tainted 6.8.7-arch1-1 #1 [ 245.136921] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 253.516332] systemd[1]: Unmounting efi.mount... [ 253.535696] systemd[1]: efi.mount: Deactivated successfully. [ 253.537261] systemd[1]: Unmounted efi.mount. [ 345.502294] systemd[1006]: Created slice background.slice. [ 345.504159] systemd[1006]: Starting systemd-tmpfiles-clean.service... [ 345.537927] systemd[1006]: Finished systemd-tmpfiles-clean.service. [ 368.017373] INFO: task khugepaged:38 blocked for more than 245 seconds. [ 368.019120] Not tainted 6.8.7-arch1-1 #1 [ 368.020219] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 368.021719] INFO: task test-journal-ve:4563 blocked for more than 245 seconds. [ 368.023485] Not tainted 6.8.7-arch1-1 #1 [ 368.024593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.891682] INFO: task khugepaged:38 blocked for more than 368 seconds. [ 490.893456] Not tainted 6.8.7-arch1-1 #1 [ 490.894594] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.896750] INFO: task test-journal-ve:4563 blocked for more than 368 seconds. [ 490.897930] Not tainted 6.8.7-arch1-1 #1 [ 490.898880] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. """ This is the same lockup as was already investigated in https://github.com/systemd/systemd-centos-ci/issues/720 and was traced to a missing backported commit in the *host* kernel, specifically d02c357e5bfa7dfd618b7b3015624beb71f58f1f (KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing). See the linked issue for all the details. Can this commit please be backported to linux-azure to fix these soft lockups in VMs running on Github Actions? ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2062977 Title: Please backport d02c357e5bfa7dfd618b7b3015624beb71f58f1f Status in linux-azure package in Ubuntu: New Bug description: We've been starting to run the systemd integration tests on Github Actions, and noticed a soft lockup in of our VMs: """ [ 245.130625] INFO: task khugepaged:38 blocked for more than 122 seconds. [ 245.131669] Not tainted 6.8.7-arch1-1 #1 [ 245.132371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.134651] INFO: task test-journal-ve:4563 blocked for more than 122 seconds. [ 245.136035] Not tainted 6.8.7-arch1-1 #1 [ 245.136921] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 253.516332] systemd[1]: Unmounting efi.mount... [ 253.535696] systemd[1]: efi.mount: Deactivated successfully. [ 253.537261] systemd[1]: Unmounted efi.mount. [ 345.502294] systemd[1006]: Created slice background.slice. [ 345.504159] systemd[1006]: Starting systemd-tmpfiles-clean.service... [ 345.537927] systemd[1006]: Finished systemd-tmpfiles-clean.service. [ 368.017373] INFO: task khugepaged:38 blocked for more than 245 seconds. [ 368.019120] Not tainted 6.8.7-arch1-1 #1 [ 368.020219] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 368.021719] INFO: task test-journal-ve:4563 blocked for more than 245 seconds. [ 368.023485] Not tainted 6.8.7-arch1-1 #1 [ 368.024593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.891682] INFO: task khugepaged:38 blocked for more than 368 seconds. [ 490.893456] Not tainted 6.8.7-arch1-1 #1 [ 490.894594] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.896750] INFO: task test-journal-ve:4563 blocked for more than 368 seconds. [ 490.897930] Not tainted 6.8.7-arch1-1 #1 [ 490.898880] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. """ This is the same lockup as was already investigated in https://github.com/systemd/systemd-centos-ci/issues/720 and was traced to a missing backported commit in the *host* kernel, specifically d02c357e5bfa7dfd618b7b3015624beb71f58f1f (KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing). See the linked issue for all the details. Can this commit please be backported to linux-azure to fix these soft lockups
[Kernel-packages] [Bug 2063233] [NEW] Please move scsi_debug.ko and nvmet-tcp.ko from linux-modules-extra to linux-modules
Public bug reported: SRU Justification [Impact] The scsi_debug.ko and nvmet-tcp.ko modules are currently shipped in linux-modules-extra. This makes it hard to pull them in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using these modules. These modules are required to run the systemd integration tests which we are trying to run in VMs on Github Actions (https://github.com/systemd/systemd/pull/32439). [Fix] Please consider moving these modules to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora these are core modules that are built by default. e.g. in Fedora both modules are part of the kernel- modules-core package. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if the kernel module files exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name scsi_debug.ko\* $ find . -name nvmet-tcp.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. ** 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/2063233 Title: Please move scsi_debug.ko and nvmet-tcp.ko from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Bug description: SRU Justification [Impact] The scsi_debug.ko and nvmet-tcp.ko modules are currently shipped in linux-modules-extra. This makes it hard to pull them in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using these modules. These modules are required to run the systemd integration tests which we are trying to run in VMs on Github Actions (https://github.com/systemd/systemd/pull/32439). [Fix] Please consider moving these modules to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora these are core modules that are built by default. e.g. in Fedora both modules are part of the kernel- modules-core package. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if the kernel module files exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name scsi_debug.ko\* $ find . -name nvmet-tcp.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Ping, would love to see this resolved. dmi-sysfs has no firmware dependency and as such should be a good fit for linux-modules instead of linux-modules-extra. The same goes for qemu-fw-cfg as well actually which also isn't a part of linux-modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] [NEW] linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
Public bug reported: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. ** 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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : ht
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038777
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp ** Tags removed: verification-needed-focal-linux-oracle-5.15 verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-mantic-linux-raspi ** Tags added: verification-done-focal-linux-oracle-5.15 verification-done-jammy-linux-bluefield verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-tegra-igx verification-done-mantic-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
