[Kernel-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Hello Alkis, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825940] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876862] [NEW] Missing v3d driver disables 3D support on RPi4
Public bug reported: Our raspberry pi kernel builds don't include the v3d drm driver (The relevant diff between the raspbian kernel config and ours) -CONFIG_DRM_V3D=m +# CONFIG_DRM_V3D is not set This means 3D acceleration is unavailable on our Pi 4 images. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1876862 Title: Missing v3d driver disables 3D support on RPi4 Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: Our raspberry pi kernel builds don't include the v3d drm driver (The relevant diff between the raspbian kernel config and ours) -CONFIG_DRM_V3D=m +# CONFIG_DRM_V3D is not set This means 3D acceleration is unavailable on our Pi 4 images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876066] Re: Support Intel TGL CPU on Focal
Hello Alex, or anyone else affected, Accepted thermald into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: thermald (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1876066 Title: Support Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu It can be checked by following command, and the patch works if it return "passed". $ systemctl is-active --quiet thermald && echo passed [regression potential] because TGL is not supported by current thermald, so thermald always inactive on TGL platform. This patch is to activate it. So, there's not potential regression. [scope] needed for F/G [original description] need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1876066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
I've added the testcase to the bug description. That seems like a sensible enough reproducer. ** Description changed: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == - As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x - -org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake- - performance-hit-hard-by-a-linux-kernel-regression?view=stream + Open two terminals: + -In the first terminal run the following command: +"sudo turbostat --show PkgWatt" + -In the second terminal run some all CPU busy workload, like stress-ng or mprime + + After few seconds turbostat will show that power is capped around 9W. + + Install the updated thermald, and repeat. + + Now with this fix the power should be capped around 15W. == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- ** Changed in: thermald (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == Open two terminals: -In the first terminal run the following command: "sudo turbostat --show PkgWatt" -In
[Kernel-packages] [Bug 1874933] Please test proposed package
Hello Srinivas, or anyone else affected, Accepted thermald into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == Open two terminals: -In the first terminal run the following command: "sudo turbostat --show PkgWatt" -In the second terminal run some all CPU busy workload, like stress-ng or mprime After few seconds turbostat will show that power is capped around 9W. Install the updated thermald, and repeat. Now with this fix the power should be capped around 15W. == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Proposed package upload rejected
An upload of apport to focal-proposed has been rejected from the upload queue for the following reason: "Groovy already has an apport verson 2.20.11-0ubuntu28 uploaded, withThis will need a new upload with a new version.". -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: In Progress Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881107] Re: zfs: backport AES-GCM performance accelleration
Do we have the tests run on hardware that does not support the relevant instructions, in addition to running them on CPUs with the AES instructions? ** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881107] Please test proposed package
Hello Colin, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857616] Update Released
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616
Title:
Cannot collect dump due to "Can't get a valid pmd_pte" error
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
Opinion
Status in makedumpfile source package in Bionic:
Fix Committed
Status in makedumpfile source package in Disco:
Invalid
Status in makedumpfile source package in Eoan:
Fix Released
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently makedumpfile has 2 flaws due to: (a) out of
synchronization with kernel code and, (b) kaslr handling. The first is
related to a definition of a memory flag bit, whereas the second is
about kaslr offset calculation - both cause similar failures when
collecting the vmcore in kdump environment:
Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't
get a valid pmd_pte.
readmem: Can't convert a virtual address(e05cb400) to physical
address.
readmem: type_addr: 0, addr:e05cb400, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
* The report is mainly related to the first issue, which started to
happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
this commit, a memory flag was changed and induced the error in dump
collection. The fix is available in makedumpfile, as commit 7bdb468c2c
("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
(due to HWE kernel 5.3), Eoan and Focal.
* The other issue is fixed in both Eoan and Focal, on makedumpfile
1.6.6-based version. It is related with the kaslr offset: if the
offset is small enough, we may return 0 wrongly in
get_kaslr_offset_x86_64(), causing the vmcore collection to fail or
even worse, to erase unintended data from the memory dump. This is
fixed by makedumpfile commit 3222d4ad04 ("x86_64: fix
get_kaslr_offset_x86_64() to return kaslr_offset correctly"), which
isn't present in versions before 1.6.6. We hereby SRU this fix for
Bionic.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy an Eoan VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure and collect a dump (with sysrq to panic the system) - the error
aforementioned is observed given Eoan kernel is 5.3-based.
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained
to makedumpfile in x86_64; both are merged in makedumpfile upstream,
one of them being already released in E/F. An unlikely regression
would potentially fails vmcore collection in kdump environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1857616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Fix Committed Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Released Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856323] Update Released
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1856323
Title:
kdump-tools is unable to resolve DNS when systemd-resolved is used
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Bionic:
Fix Committed
Status in makedumpfile source package in Disco:
Won't Fix
Status in makedumpfile source package in Eoan:
Fix Released
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently kdump is unable to handle domain name resolution due to
the lack of "resolved" service in the kdump environment; this happens
given the nature of reduced service load required in the kdump
scenario.
* Kdump currently relies on a systemd service approach - there are 2
services, one being a configuration/load entity (kdump-tools.service)
whereas the other is the crash dump service itself (kdump-tools-
dump.service). Due to the complexity and risk in booting a machine
after a kernel crash to collect kernel dump, it's expected kdump-
tools-dump to load the minimal possible amount of services. In order
to achieve that, kdump-tools-dump relies only in the sysinit and
network-online targets.
* The systemd DNS tool ("resolved") is not ready in the moment kdump-
tools-dump service is up to collect the kernel dump; also, "resolved"
depends on dbus.socket to work, so to have a fully functional DNS
resolution we are hereby adding both services as dependencies for
kdump-tools-dump, so the network dump functionality works with
hostnames (not requiring anymore that users set IP raw addresses).
* The attached SVG files (kdump.svg and regular_boot.svg) contains
"systemd-analyze plot" outputs from a kdump-tools-dump and regular
boot perspective. To collect the kdump data we manage to change the
kdump-tools-dump service to load SSHd and also that required disabling
the OneShot property of such service. With that data, one can check
the services started/completed in each environment - it's possible to
notice the absence of systemd-resolved when in kdump environment.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure a network dump (SSH or NFS) using hostnames for the target
machine;
5) Perform the test dump (with 'echo c> /proc/sysrq-trigger') and watch the
failure in name resolution,
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained to
kdump-tools package; it'll only affect the services loaded before
kdump-tools-dump collecting service.
A regression would then potentially fails kdump completion if one of the new
services added to the kdump environment load (resolved and dbus.socket) fails
to load and stalls/prevents the kdump service complete load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1856323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800566] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Released Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Bionic VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856084] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856084 Title: Livelock between ZFS evict and writeback threads Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Disco: Fix Released Status in zfs-linux source package in Eoan: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux package in Debian: Fix Released Bug description: Livelock between ZFS evict and writeback threads [Impact] ZIO pipeline stalls, causing ZFS workloads to hang indefinitely [Description] For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows: [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [72742.070429] mysqld D0 5713 2881 0x0320 [72742.073220] Call Trace: [72742.075305] __schedule+0x24e/0x880 [72742.090436] schedule+0x2c/0x80 [72742.090438] schedule_preempt_disabled+0xe/0x10 [72742.090441] __mutex_lock.isra.5+0x276/0x4e0 [72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs] [72742.090555] __mutex_lock_slowpath+0x13/0x20 [72742.115374] ? __mutex_lock_slowpath+0x13/0x20 [72742.132266] mutex_lock+0x2f/0x40 [72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs] [72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl] [72742.152622] ? mutex_lock+0x12/0x40 [72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs] [72742.171450] zil_commit+0xde/0x150 [zfs] [72742.173687] zfs_fsync+0x77/0xe0 [zfs] [72742.175044] zpl_fsync+0x80/0x110 [zfs] [72742.191690] vfs_fsync_range+0x51/0xb0 [72742.193876] do_fsync+0x3d/0x70 [72742.195126] SyS_fsync+0x10/0x20 [72742.211059] do_syscall_64+0x73/0x130 [72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 It's possible to hit this issue due to a race between the ZFS evict and writeback threads. If the z_iput task is trying to evict a znode that's currently sitting in the writeback thread, both will "livelock" each other and stall the ZIO pipeline, causing other ZFS operations (such as zil_commit) to hang indefinitely. This has been documented and fixed upstream in PR#9583 [0]. We need to pull two fixes from upstream: the first one fixes the zfs_zget() issue in the writeback thread, while the second fixes a regression on O_TMPFILE descriptors caused by the first one. Upstream patches: - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8) - Check for unlinked znodes after igrab() (0c46813805f4) [Test Case] Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads. [Regression Potential] These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low. Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly. [0] https://github.com/zfsonlinux/zfs/pull/9583 [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8 [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: p
[Kernel-packages] [Bug 1763823] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1763823 Title: Update firmware for 18.04 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Released Bug description: SRU Justification Impact: A 4.15-based hwe-edge kernel has been introduced into xenial. However some of the firmware files it requires are missing from xenial's linux-firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in xenial. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1763823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753439] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1753439 Title: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Invalid Bug description: SRU Justification Impact: BLE scanning for nearby beacons per second is too low and result high loss rate. Fix: Updated firmware. Test Case: Test on affected hardware using instructions below. Regression Potential: Limited to specific hardware. --- Steps to replicate the issue: 1. Power on the BT device, then change the terminal by "Ctil+F1" or open another putty to ssh SUT. 2.Use command below to discover BLE device. $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan --duplicates --passive | perl -nle 'print scalar(localtime), " ",$_' 3. log as attachment. This bug is for tracking purposes only, do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752044] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1752044 Title: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification Impact: New ath10k firmware is needed for compliance with CE-RED. Fix: Updated firmware files. Regression Potential: This update has been in upstream linux-firmware for a while now. While regressions are possible, the firmware should have seen a lot of use by now. --- To comply with CE-RED (Radio Emissions Directive), ath10k/QCA6174/hw3.0/board-2.bin and ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated. The commits are: commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2 Author: Kalle Valo AuthorDate: Thu Feb 15 15:10:51 2018 +0200 Commit: Kalle Valo CommitDate: Thu Feb 15 15:10:51 2018 +0200 ath10k: QCA6174 hw3.0: update board-2.bin Signed-off-by: Kalle Valo commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc Author: Kalle Valo AuthorDate: Thu Feb 15 15:10:51 2018 +0200 Commit: Kalle Valo CommitDate: Thu Feb 15 15:10:51 2018 +0200 ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00079-QCARMSWPZ-1 Signed-off-by: Kalle Valo To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1752044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757443] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1757443 Title: Redpine: BLE radio lost issue Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in linux source package in Xenial: Triaged Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Bionic: Incomplete Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: Radio stops capturing advertisements after several hours. Fix: Updated firmware. Test Case: See below. Regression Potential: Limited to specific hardware. --- Below are the steps to replicate the issue We are doing continuous BLE scanning and monitoring the advertisements from reference device. After long periods of capture (several hours), the radio stops capturing advertisements and won't start again until we power cycle the box or manually unload/load the module via modprobe This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788314] Re: Conflict between zfs-linux and s390-tools
Hello Stéphane, or anyone else affected, Accepted lxd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/3.0.2-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788314 Title: Conflict between zfs-linux and s390-tools Status in s390-tools package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Invalid Bug description: Not sure which of the two needs fixing, but there's a path conflict between zfs-linux and s390-tools which effectively prevents installing ZFS on s390x in cosmic. (Reading database ... 83042 files and directories currently installed.) Preparing to unpack .../zfsutils-linux_0.7.9-3ubuntu5_s390x.deb ... Unpacking zfsutils-linux (0.7.9-3ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb (--unpack): trying to overwrite '/usr/share/initramfs-tools/hooks/zdev', which is also in package s390-tools 2.6.0-0ubuntu2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Exit request sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1788314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
I have made some changes to my configuration, so it's not an entirely clean test, but I *did* notice that I no longer needed to mess with gfxpayload. I guess that it's fixed? ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773637] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1773637 Title: Distribution upgrade to 18.04: used nvidia display driver is commented out Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Cosmic: Won't Fix Status in ubuntu-release-upgrader source package in Cosmic: Fix Released Bug description: Impact -- Users who have manually configured an xorg.conf file with nvidia enabled as a driver will be surprised to have disabled on upgrade to a new release of Ubuntu and won't have a graphical display. Test Case - If you don't have a system with nvidia hardware to upgrade this is a bit convoluted but still works. 1) Run do-release-upgrade (use -d if upgrading to disco) 2) Cancel the upgrade 3) Create an /etc/X11/xorg.conf file with a Device section listed in the original description using the nvidia driver. 4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME 5) run ./$target-release-name --frontend DistUpgradeViewText 6) Observe the Driver line is commented out of xorg.conf When testing the release-upgrader from -proposed you'll need to use the -p switch to get the right tarball. Additionally, you'll want to add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to True instead of False (line 106) this'll simulate the nvidia driver being loaded. Regression Potential This just changes how xorg_fix_proprietary check for nvidia being in use and it only affects people who have an /etc/X11/xorg.conf so the impact of a regression is rather small. Additionally, the logic used to determine if nvidia in use is the same logic used in the apport package hook for all xorg packages so is well tested. Original Description I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade. After the installation had finished, Xorg wouldn't start. I later found out that this was because the installation routine had commented out the nvidia display driver I used in the xorg.conf: Section "Device" Identifier "nvidia" #Driver "nvidia" BusID "PCI:10@0:0:0" Option "ConstrainCursor" "off" EndSection As the installtion routine backuped my xorg.conf I could verify that the line hadn't been commented out before upgrading. Removing the "#" solved the problem. ProblemType: BugDistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 27 11:43:16 2018 DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d] Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d] InstallationDate: Installed on 2017-11-02 (205 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro
[Kernel-packages] [Bug 1675443] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1675443 Title: Update linux-firmware in xenial for 4.10 hwe-edge kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Released Bug description: SRU Justification Impact: The linux-hwe-edge kernel will soon be based on the 4.10 zesty kernel, which requires new/updated firmware files. Fix: Backport relevant commits from upstream linux-firmware. Regression Potential: In most cases these are new files which will not be used by older kernels, so no regression is possible there. In a few cases there are updates to existing firmware files, and while regressions are not expected they are possible. --- linux-hwe-edge in xenial is in the process of being updated to be based on the 4.10 zesty kernel. Add/update firmware files for this kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1675443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682871] Update Released
The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in linux source package in Xenial: In Progress Status in cloud-init source package in Yakkety: Fix Committed Status in linux source package in Yakkety: Fix Released Status in cloud-init source package in Zesty: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. * cloud-init test case wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg; chmod 755 get-proposed-cloudimg; for release in xenial yakkety zesty; do ./get-proposed-cloudimg $release; MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img ; # ubuntu/passw0rd python3 -c 'from cloudinit.net import get_interfaces_by_mac; print(get_interfaces_by_mac())'; # results in no runtime error and doesn't report vlan interface name done [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Hello Martin, or anyone else affected, Accepted gdm3 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.36.3-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gdm3 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Committed Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic
[Kernel-packages] [Bug 1893004] Re: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1893004 Title: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: [Impact] On the Dell WD15/19 Dock station, there is a USB audio card, and a headset audio jack routes to this audio card. We found if we plug some specific headset (non-iphone type headset), we could not record any sound from headset-mic even we set the input volume to max. [Fix] Improve the ucm for the audio card in this Dock, let the driver mixer value be adjustable, then we could adjust the input volume from driver side. [Test Case] plug various types of headset to the WD19 and WD15 dock stations, and adjust the input volume from gnome, check the input volume in the driver by running amixer, found the input volume is changed in the driver; record the sound from headset-mic, it could record the sound from all headsets we tested. [Regression Risk] It could make the PA fail to load the ucm on the machines with Dell WD15/WD19 dock station, then users only see analogue output/input from gnome-control-center instead of usb-speaks usb-lineout and usb-mic. But this possibility is very low since we have tested the patch on WD15 and WD19 dock, all worked very well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0%
[Kernel-packages] [Bug 1897934] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: Invalid Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724863] Update Released
The verification of the Stable Release Update for bcmwl has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1724863 Title: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe- edge 4.13.0-16.19~16.04.3 Status in bcmwl package in Ubuntu: In Progress Status in bcmwl source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package bcmwl-kernel-source fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original Description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1724863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
This package has been waiting for testing in Artful for 90 days and is blocking the release of other makedumpfile fixes for Xenial and Artful. Please test this SRU! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: Fix Committed Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741081] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Artful: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request, Artful == Enable ZFS module to be loaded without the broken ubuntu-load-zfs- unconditionally.patch. == Fix == Add a new zfs-load-module.service script that modprobes the ZFS module and remove any hard coded module loading from zfs-import-cache.service & zfs-import-scan.service and make these latter scripts require the new zfs-load-module.service script. Also remove the now defunct ubuntu-load-zfs-unconditionally.patch as this will no longer be required. == Testcase == On a clean VM, install with the fixed package, zfs should load automatically. == Regression potential == ZFS module may not load if the changes are broken. However, testing proves this not to be the case. I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719945] [NEW] Silently fails in Wayland session
Public bug reported: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: New Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] [NEW] Every second(?) boot fails to display anything [MSHYBRID mode]
Public bug reported: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Confirmed Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pa
Re: [Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
Yes. In all cases, GRUB itself draws fine. On further experimentation, it seems that it might be the case that the boot after a *failed* boot works. If nothing is visible and I blindly enter my cryptroot password it can boot all the way; rebooting with ctrl-alt-delete after that seems to result in another faliure to display anything on the subsequent boot. Restarting with ctrl-alt-delete from the (unseen) initramfs prompt seems to reliably result in the subsequent boot getting displayed. This does not seem to be related to $VT_HANDOFF in GRUB; whether or not it is enabled in grub.cfg does not appear to make a difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
You are absolutely correct; forceing “gfxmode text” appears to make booting reliably visible. That's a nice workaround. I guess this is a buggy VBIOS issue, then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1719945] Re: Silently fails in Wayland session
It's certainly possible to log out, log in to an Xorg session, and then log out again/reboot to switch to NVIDIA. *If* you know that's what you need to do. Since nvidia-settings silently fails *and* we default to Wayland if possible users who don't know this is what you need to do will find it very difficult to switch back from Intel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721902] [NEW] Bluetooth hangs ~1m after connecting to Bose headset
Public bug reported: I have a set of Bose bluetooth headphones here (annoyingly they don't have any model identification on them - they're the big over-ear ones, maybe called Quiet Comfort?). After pairing them, they work (mostly) fine, including switching between HSP/A2DP mode, for about a minute. After about a minute they stop working, and anything which was using them (bluez, the gnome-control- centre “Sound” tab) hangs. This appears to be a firmware bug - at the time that they stop working, a firmware debugging message is dumped into dmesg: [ 613.938660] iwlwifi :6e:00.0: Queue 10 is active on fifo 1 and stuck for 1 ms. SW [97, 174] HW [97, 174] FH TRB=0x0c010a070 [ 613.938779] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. [ 613.938930] iwlwifi :6e:00.0: Start IWL Error Log Dump: [ 613.938935] iwlwifi :6e:00.0: Status: 0x0200, count: 6 [ 613.938938] iwlwifi :6e:00.0: Loaded firmware version: 31.532993.0 [ 613.938943] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 613.938947] iwlwifi :6e:00.0: 0x0230 | trm_hw_status0 [ 613.938951] iwlwifi :6e:00.0: 0x0001 | trm_hw_status1 [ 613.938955] iwlwifi :6e:00.0: 0x0002484C | branchlink2 [ 613.938959] iwlwifi :6e:00.0: 0x0003936E | interruptlink1 [ 613.938962] iwlwifi :6e:00.0: 0x0003936E | interruptlink2 [ 613.938966] iwlwifi :6e:00.0: 0x | data1 [ 613.938969] iwlwifi :6e:00.0: 0x0080 | data2 [ 613.938972] iwlwifi :6e:00.0: 0x0783 | data3 [ 613.938976] iwlwifi :6e:00.0: 0x7780DFED | beacon time [ 613.938980] iwlwifi :6e:00.0: 0xAE1C40EB | tsf low [ 613.938983] iwlwifi :6e:00.0: 0x0614 | tsf hi [ 613.938986] iwlwifi :6e:00.0: 0x | time gp1 [ 613.938990] iwlwifi :6e:00.0: 0x226DC357 | time gp2 [ 613.938993] iwlwifi :6e:00.0: 0x0001 | uCode revision type [ 613.938997] iwlwifi :6e:00.0: 0x001F | uCode version major [ 613.939000] iwlwifi :6e:00.0: 0x00082201 | uCode version minor [ 613.939004] iwlwifi :6e:00.0: 0x0230 | hw version [ 613.939007] iwlwifi :6e:00.0: 0x00C89000 | board version [ 613.939011] iwlwifi :6e:00.0: 0x000B019C | hcmd [ 613.939014] iwlwifi :6e:00.0: 0x2402200A | isr0 [ 613.939018] iwlwifi :6e:00.0: 0x0080 | isr1 [ 613.939021] iwlwifi :6e:00.0: 0x0800180A | isr2 [ 613.939024] iwlwifi :6e:00.0: 0x004154C0 | isr3 [ 613.939028] iwlwifi :6e:00.0: 0x | isr4 [ 613.939031] iwlwifi :6e:00.0: 0x000B019C | last cmd Id [ 613.939035] iwlwifi :6e:00.0: 0x | wait_event [ 613.939038] iwlwifi :6e:00.0: 0x0080 | l2p_control [ 613.939041] iwlwifi :6e:00.0: 0x00010030 | l2p_duration [ 613.939045] iwlwifi :6e:00.0: 0x003F | l2p_mhvalid [ 613.939049] iwlwifi :6e:00.0: 0x0080 | l2p_addr_match [ 613.939052] iwlwifi :6e:00.0: 0x000D | lmpm_pmg_sel [ 613.939056] iwlwifi :6e:00.0: 0x15062149 | timestamp [ 613.939059] iwlwifi :6e:00.0: 0x00342838 | flow_handler [ 613.939123] iwlwifi :6e:00.0: 0x | ADVANCED_SYSASSERT [ 613.939126] iwlwifi :6e:00.0: 0x | umac branchlink1 [ 613.939130] iwlwifi :6e:00.0: 0x | umac branchlink2 [ 613.939133] iwlwifi :6e:00.0: 0x | umac interruptlink1 [ 613.939137] iwlwifi :6e:00.0: 0x | umac interruptlink2 [ 613.939140] iwlwifi :6e:00.0: 0x | umac data1 [ 613.939144] iwlwifi :6e:00.0: 0x | umac data2 [ 613.939147] iwlwifi :6e:00.0: 0x | umac data3 [ 613.939150] iwlwifi :6e:00.0: 0x | umac major [ 613.939154] iwlwifi :6e:00.0: 0x | umac minor [ 613.939157] iwlwifi :6e:00.0: 0x | frame pointer [ 613.939161] iwlwifi :6e:00.0: 0x | stack pointer [ 613.939164] iwlwifi :6e:00.0: 0x | last host cmd [ 613.939168] iwlwifi :6e:00.0: 0x | isr status reg [ 613.939175] ieee80211 phy0: Hardware restart was requested ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: chris 4153 F...m pulseaudio /dev/snd/controlC0: chris 4153 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 08:48:50 2017 InstallationDate: Installed on 2017-09-20 (16 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
Oh, it might be worth mentioning - on the boots where I wouldn't see anything, adding the fbcon=map:1 parameter to the kernel command line gives a usable system - the console and X¹ both come up correctly. ¹: For X there's an additional wrinkle in that the hybrid graphics detection in gpu-detect fails to correctly identify the need for offloading, but if I have a correct Xorg.conf already in place X will run just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Hello Mary, or anyone else affected, Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pulseaudio (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.
[Kernel-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
I've accepted this SRU to xenial-proposed. Can I confirm that this bug is already fixed in yakkety and zesty? If not, could you please upload fixes for those releases, too. We need to ensure that upgrades don't regress. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscript
[Kernel-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Hello Fabien, or anyone else affected, Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pulseaudio (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
Hello Dustin, or anyone else affected, Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pulseaudio (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset
Can you please describe what sort of testing has been done? Just a bare ‘verification-done-xenial’ is not very helpful. -- 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/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704363] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Released Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642709] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1642709 Title: Add i915/skl_guc_ver6.bin to linux-firmware in Trusty Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Released Bug description: Linux-firmware is missing the following i915 firmware files, required by the i915 driver in 4.4.0-47-generic: $ update-initramfs -k 4.4.0-47-generic -c W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module i915_bpo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1642709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Bug description: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659618] Re: Enable ARM64 support in kexec-tools
While this has passed testing on arm64, it introduces a FTBFS regression in the armhf package on Yakkety: https://launchpad.net/ubuntu/+source /kexec-tools/1:2.0.10-2ubuntu1.1/+build/12076905 Please resolve this build error and upload a new package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1659618 Title: Enable ARM64 support in kexec-tools Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Status in kexec-tools package in Debian: Fix Released Bug description: [IMPACT] * kexec-tools in Xenial (16.04) currently does not support ARM64 architecture. * Backport support for ARM64 arch from upstream https://github.com/horms/kexec-tools * Majority of the patches are contained in kexec/arch/arm64/ except for one patch that impacts purgatory and common device tree routines. [TEST CASE] * I built kexec-tools for ARM64 and tested it on HW using the following testcase: $ sudo kexec -l /boot/vmlinuz--generic --initrd=/boot/initrd.img--generic --command-line="root=UUID= ro vt.handoff=7" $ sudo kexec -e * I was able to kexec the new kernel successfully. * [ 6702.357899] kexec_core: Starting new kernel [0.00] Booting Linux on physical CPU 0x200 [0.00] Linux version -generic (buildd@bos01-arm64-008) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) [0.00] Boot CPU: AArch64 Processor [510f8000] [REGRESSION POTENTIAL] * Since patches are confined to arm[64] there is a low overall risk of regression. [OTHER INFO] * You can find a Xenial kexec-tools package built for AMD64, i386 and ARM64 in my PPA https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools * This package is built using the Xenial source package for kexec-tools with ARM64 enablement patches applied. * Please pull the changes from my PPA package and integrate into Ubuntu Xenial kexec-tools after review. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1324790] [NEW] Bluetooth problem with Parrot Zik headphones
Public bug reported: HSP profile fails to work on my bluetooth headset (a Parrot Zik); a2dp works fine. HSP profile doesn't get sound or have the mic working. This seems at least in part to be a kernel issue; the relevant bit of syslog is: ... May 30 08:34:43 RedTail bluetoothd[4864]: /org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd10: fd(25) ready May 30 08:34:44 RedTail kernel: [63184.627985] input: 90:03:B7:5F:6F:DF as /devices/virtual/input/input121 May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CSCS=? May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CPBS=? May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CIMI May 30 08:35:12 RedTail bluetoothd[4864]: /org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd11: fd(23) ready May 30 08:37:26 RedTail bluetoothd[4864]: Audio connection got disconnected May 30 08:37:55 RedTail kernel: [63376.126544] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126559] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126566] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126572] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126578] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126584] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126590] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126595] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126601] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126606] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126612] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126617] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126623] Bluetooth: hci0 SCO packet for unknown connection handle 7936 May 30 08:37:55 RedTail kernel: [63376.126629] Bluetooth: hci0 SCO packet for unknown connection handle 48 May 30 08:37:55 RedTail kernel: [63376.126635] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126641] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126647] Bluetooth: hci0 SCO packet for unknown connection handle 0 ... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-2-generic (not installed) ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6 Uname: Linux 3.15.0-2-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: chris 3967 F...m pulseaudio /dev/snd/pcmC1D0p: chris 3967 F...m pulseaudio /dev/snd/controlC1: chris 3967 F pulseaudio /dev/snd/controlC0: chris 3967 F pulseaudio CurrentDesktop: Unity Date: Fri May 30 08:56:58 2014 InstallationDate: Installed on 2013-08-06 (296 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash i915.i915_enable_rc6=7 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.15.0-2-generic N/A linux-backports-modules-3.15.0-2-generic N/A linux-firmware1.130 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2013-08-06 (296 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1324790 Title: Bluetooth problem with Parrot Zik headphones Status in “linux” package in Ubuntu: New Bug description: HSP profile fails to work on my bluetooth headset (a Parrot Zik)
[Kernel-packages] [Bug 1295483] [NEW] [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456!
Public bug reported: It looks like Chrome's GPU acceleration is very infrequently capable of taking down the kernel; I've been running it for a number of weeks and only just hit this BUG: Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here ] Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456! Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode: [#1] SMP Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_ nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_ probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction lttng_probe_btrfs lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_ buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k ath9k_common psmou se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci ptp pps_core wmi video Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome Not tainted 3.13.0-18-generic #38-Ubuntu Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013 Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 8802d47c6000 task.ti: 8802d47c6000 Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[] [] swiotlb_tbl_map_single+0x28d/0x2a0 Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70 EFLAGS: 00010246 Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX: RBX: RCX: Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: d4abd000 RDI: Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: R09: 880402f726d0 Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 0062 R12: 880409239098 Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 1600 R15: 0020 Mar 21 14:17:49 RedTail kernel: [58101.988607] FS: 7fa8d07d5a00() GS:88041fbc() knlGS: Mar 21 14:17:49 RedTail kernel: [58101.988627] CS: 0010 DS: ES: CR0: 80050033 Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 000362cb9000 CR4: 001407e0 Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack: Mar 21 14:17:49 RedTail kernel: [58101.988667] 1fa944c0 00058000 88039dff9e40 Mar 21 14:17:49 RedTail kernel: [58101.988691] 880409239098 001a957a Mar 21 14:17:49 RedTail kernel: [58101.988723] 880409239098 0040 1600 88021bf3f800 Mar 21 14:17:49 RedTail kernel: [58101.988759] Call Trace: Mar 21 14:17:49 RedTail kernel: [58101.988777] [] swiotlb_map_sg_attrs+0xba/0x150 Mar 21 14:17:49 RedTail kernel: [58101.988820] [] i915_gem_gtt_prepare_object+0x82/0xb0 [i915] Mar 21 14:17:49 RedTail kernel: [58101.988854] [] i915_gem_object_pin+0x47a/0x720 [i915] Mar 21 14:17:49 RedTail kernel: [58101.90] [] i915_gem_execbuffer_reserve_vma.isra.12+0x6c/0x1e0 [i915] Mar 21 14:17:49 RedTail kernel: [5810
[Kernel-packages] [Bug 1295483] Re: [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456!
apport information ** Tags added: apport-collected ** Description changed: It looks like Chrome's GPU acceleration is very infrequently capable of taking down the kernel; I've been running it for a number of weeks and only just hit this BUG: Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here ] Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456! Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode: [#1] SMP Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_ nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_ probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction lttng_probe_btrfs lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_ buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k ath9k_common psmou se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci ptp pps_core wmi video Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome Not tainted 3.13.0-18-generic #38-Ubuntu Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013 Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 8802d47c6000 task.ti: 8802d47c6000 Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[] [] swiotlb_tbl_map_single+0x28d/0x2a0 Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70 EFLAGS: 00010246 Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX: RBX: RCX: Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: d4abd000 RDI: Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: R09: 880402f726d0 Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 0062 R12: 880409239098 Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 1600 R15: 0020 Mar 21 14:17:49 RedTail kernel: [58101.988607] FS: 7fa8d07d5a00() GS:88041fbc() knlGS: Mar 21 14:17:49 RedTail kernel: [58101.988627] CS: 0010 DS: ES: CR0: 80050033 Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 000362cb9000 CR4: 001407e0 Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack: Mar 21 14:17:49 RedTail kernel: [58101.988667] 1fa944c0 00058000 88039dff9e40 Mar 21 14:17:49 RedTail kernel: [58101.988691] 880409239098 001a957a Mar 21 14:17:49 RedTail kernel: [58101.988723] 880409239098 0040 1600 88021bf3f800 Mar 21 14:17:49 RedTail kernel: [58101.988759] Call Trace: Mar 21 14:17:49 RedTail kernel: [58101.988777] [] swiotlb_map_sg_attrs+0xba/0x150 Mar 21 14:17:49 RedTail kernel: [58101.988820] [] i915_gem_gtt_prepare_object+0x82/0xb0 [i915] Mar 21 14:17:49 RedTail kernel: [58101.988854] [] i915_gem_object_pin+0x47a/0x720 [i915] Mar 21 14:1
Re: [Kernel-packages] [Bug 1295483] Re: [i915] kernel BUG at/build/buildd/linux-3.13.0/lib/swiotlb.c:456!
I'm now running the 3.14 rc7 build from there. However, it'll be difficult to tell if this is fixed or not; I've only encountered it once in a couple of weeks' solid use of Chrome. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295483 Title: [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456! Status in “linux” package in Ubuntu: Incomplete Bug description: It looks like Chrome's GPU acceleration is very infrequently capable of taking down the kernel; I've been running it for a number of weeks and only just hit this BUG: Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here ] Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456! Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode: [#1] SMP Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_ nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_ probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction lttng_probe_btrfs lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_ buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k ath9k_common psmou se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci ptp pps_core wmi video Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome Not tainted 3.13.0-18-generic #38-Ubuntu Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013 Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 8802d47c6000 task.ti: 8802d47c6000 Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[] [] swiotlb_tbl_map_single+0x28d/0x2a0 Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70 EFLAGS: 00010246 Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX: RBX: RCX: Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: d4abd000 RDI: Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: R09: 880402f726d0 Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 0062 R12: 880409239098 Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 1600 R15: 0020 Mar 21 14:17:49 RedTail kernel: [58101.988607] FS: 7fa8d07d5a00() GS:88041fbc() knlGS: Mar 21 14:17:49 RedTail kernel: [58101.988627] CS: 0010 DS: ES: CR0: 80050033 Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 000362cb9000 CR4: 001407e0 Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack: Mar 21 14:17:49 RedTail kernel: [58101.988667] 1fa944c0 00058000 88039dff9e40 Mar 21 14:17:49 RedTail kernel: [58101.988691] 880409239098 001a957a Mar 21 14:17:49 RedTail kernel: [58101.988723] 880
[Kernel-packages] [Bug 1274622] Please test proposed package
Hello michaelcole, or anyone else affected, Accepted linux-firmware into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/linux- firmware/1.116.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274622 Title: /lib/firmware/iwlwifi-7260-7.ucode is the wrong version Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Fix Committed Bug description: Hi, I ran into a bug that made wifi unstable on my Lenovo Ideapad Y710. I needed to disable/reenable networking about every 5 minutes. I was able to get some connectivity, but obviously, this is a pain in the ass. After working with the awesome support folks at Intel, I think we isolated the problem and solution. The problem likely affects all laptops with the Intel(R) Wireless 7260 chipset. The solution is to use updated firmware from here: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/iwlwifi-7260-7.ucode?id=824994715e0276e64cdbf2badbe02921a78fb287 Just replace the /lib/firmware/iwlwifi-7260-7.ucode binary with the new one. Below is the last email I got from Luca at ilw at linux.intel.com - if you have questions, they know the technical details to the solution. Thanks again! Mike -- Hi Mike, My colleague noticed that you are using an older version of the firmware which contains a bug that may be the cause of the problem you're seeing. We have pushed a new firmware (with a fix for this) to the linux-firmware.git repository. You can get it here: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/iwlwifi-7260-7.ucode?id=824994715e0276e64cdbf2badbe02921a78fb287 Just replace the /lib/firmware/iwlwifi-7260-7.ucode binary with the new one. I checked Ubuntu's packages and it seems that they only updated to the new one in the linux-firmware 1.122 package (for trusty). Ubuntu Saucy (13.10) still has the old version in the linux-firmware 1.116 package. It would be nice if someone would poke Ubuntu to add 1.122 to the saucy-updates or something. I believe Linux Mint is following Ubuntu in this case. I hope this helps! (And thanks to Emmanuel for the help ;) -- Cheers, Luca. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2173 F pulseaudio /dev/snd/controlC0: michael2173 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6ca2b9e3-fdd0-434e-b92a-06c69c90ca9b InstallationDate: Installed on 2013-12-25 (36 days ago) InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126 MachineType: LENOVO 20250 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=dccd14b6-5933-476f-b0f0-3175e5cd454a ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: petra Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/02/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7FCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Durian 7A1 dmi.board.vendor: LENOVO dmi.board.version: 3193Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z710 dmi.modalias: dmi:bvnLENOVO:bvr7FCN35WW:bd09/02/2013:svnLENOVO:pn20250:pvrLenovoZ710:rvnLENOVO:rnDurian7A1:rvr3193Std:cvnLENOVO:ct10:cvrLenovoIdeaPadZ710: dmi.product.name: 20250
[Kernel-packages] [Bug 1265436] Re: Saucy SRU: update firmware for 7260 / 3160 devices (Wilkins Peak)
Marking verification done as per comment #5 ** Tags added: verification-done -- 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/1265436 Title: Saucy SRU: update firmware for 7260 / 3160 devices (Wilkins Peak) Status in intel: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Committed Status in “linux-firmware” source package in Saucy: Fix Released Status in “linux-firmware” source package in Trusty: Fix Released Bug description: 2 new firmware versions are now available and need to update for 7260 / 3160 devices(Wilkins Peak) at http://wireless.kernel.org/en/users/Drivers/iwlwifi [1] Wireless 7260 3.10+ kernel -> iwlwifi-7260-ucode-22.1.7.0.tgz Wireless 3160 3.10+ kernel -> iwlwifi-3160-ucode-22.1.7.0.tgz also available in linux-firmware.git commit 824994715e0276e64cdbf2badbe02921a78fb287 iwlwifi: update firmware for 7260 / 3160 devices [2] Wireless 7260 3.13+ kernel -> iwlwifi-7260-ucode-22.15.8.0.tgz Wireless 3160 3.13+ kernel -> iwlwifi-3160-ucode-22.15.8.0.tgz Quote from Emmanuel: "OSVs can safely have both firmware files installed regardless of the kernel version. Kernel 3.10 won’t load 22.15.8.0 but 22.1.7.0 only. Kernel 3.13 will try to load 22.15.8.0 and if it is not there, it will try to load 22.1.7.0. So nothing bad will happen if OSVs have both firmware installed. Just a bit of a waste - but nothing worse than that." To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1265436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265436] Please test proposed package
Hello Yingying, or anyone else affected, Accepted linux-firmware into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/linux- firmware/1.116.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1265436 Title: Saucy SRU: update firmware for 7260 / 3160 devices (Wilkins Peak) Status in intel: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Committed Status in “linux-firmware” source package in Saucy: Fix Released Status in “linux-firmware” source package in Trusty: Fix Released Bug description: 2 new firmware versions are now available and need to update for 7260 / 3160 devices(Wilkins Peak) at http://wireless.kernel.org/en/users/Drivers/iwlwifi [1] Wireless 7260 3.10+ kernel -> iwlwifi-7260-ucode-22.1.7.0.tgz Wireless 3160 3.10+ kernel -> iwlwifi-3160-ucode-22.1.7.0.tgz also available in linux-firmware.git commit 824994715e0276e64cdbf2badbe02921a78fb287 iwlwifi: update firmware for 7260 / 3160 devices [2] Wireless 7260 3.13+ kernel -> iwlwifi-7260-ucode-22.15.8.0.tgz Wireless 3160 3.13+ kernel -> iwlwifi-3160-ucode-22.15.8.0.tgz Quote from Emmanuel: "OSVs can safely have both firmware files installed regardless of the kernel version. Kernel 3.10 won’t load 22.15.8.0 but 22.1.7.0 only. Kernel 3.13 will try to load 22.15.8.0 and if it is not there, it will try to load 22.1.7.0. So nothing bad will happen if OSVs have both firmware installed. Just a bit of a waste - but nothing worse than that." To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1265436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265436] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1265436 Title: Saucy SRU: update firmware for 7260 / 3160 devices (Wilkins Peak) Status in intel: New Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Committed Status in “linux-firmware” source package in Saucy: Fix Released Status in “linux-firmware” source package in Trusty: Fix Released Bug description: 2 new firmware versions are now available and need to update for 7260 / 3160 devices(Wilkins Peak) at http://wireless.kernel.org/en/users/Drivers/iwlwifi [1] Wireless 7260 3.10+ kernel -> iwlwifi-7260-ucode-22.1.7.0.tgz Wireless 3160 3.10+ kernel -> iwlwifi-3160-ucode-22.1.7.0.tgz also available in linux-firmware.git commit 824994715e0276e64cdbf2badbe02921a78fb287 iwlwifi: update firmware for 7260 / 3160 devices [2] Wireless 7260 3.13+ kernel -> iwlwifi-7260-ucode-22.15.8.0.tgz Wireless 3160 3.13+ kernel -> iwlwifi-3160-ucode-22.15.8.0.tgz Quote from Emmanuel: "OSVs can safely have both firmware files installed regardless of the kernel version. Kernel 3.10 won’t load 22.15.8.0 but 22.1.7.0 only. Kernel 3.13 will try to load 22.15.8.0 and if it is not there, it will try to load 22.1.7.0. So nothing bad will happen if OSVs have both firmware installed. Just a bit of a waste - but nothing worse than that." To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1265436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1324790] Re: Bluetooth problem with Parrot Zik headphones
Tried with the 3.16-rc4 kernel. Syslog output was different, but the headset still fails to switch to HSP mode, and similar messages are generated: Jul 9 09:38:02 RedTail bluetoothd[816]: Badly formated or unrecognized command: AT+CSCS=? Jul 9 09:38:02 RedTail bluetoothd[816]: Badly formated or unrecognized command: AT+CPBS=? Jul 9 09:38:03 RedTail bluetoothd[816]: Badly formated or unrecognized command: AT+CIMI Jul 9 09:38:03 RedTail bluetoothd[816]: /org/bluez/816/hci0/dev_90_03_B7_5F_6F_DF/fd2: fd(28) ready Jul 9 09:38:04 RedTail kernel: [ 437.195341] input: 90:03:B7:5F:6F:DF as /devices/virtual/input/input25 Jul 9 09:39:33 RedTail bluetoothd[816]: /org/bluez/816/hci0/dev_90_03_B7_5F_6F_DF/fd1: fd(25) ready Jul 9 09:39:33 RedTail kernel: [ 526.271851] Bluetooth: hci0 SCO packet for unknown connection handle 31 Jul 9 09:39:38 RedTail bluetoothd[816]: Audio connection got disconnected ** Tags removed: needs-upstream-testing regression-potential ** Tags added: kernel-bug-exists-upstream-3.16-rc4 ** 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/1324790 Title: Bluetooth problem with Parrot Zik headphones Status in “linux” package in Ubuntu: Confirmed Bug description: HSP profile fails to work on my bluetooth headset (a Parrot Zik); a2dp works fine. HSP profile doesn't get sound or have the mic working. This seems at least in part to be a kernel issue; the relevant bit of syslog is: ... May 30 08:34:43 RedTail bluetoothd[4864]: /org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd10: fd(25) ready May 30 08:34:44 RedTail kernel: [63184.627985] input: 90:03:B7:5F:6F:DF as /devices/virtual/input/input121 May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CSCS=? May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CPBS=? May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized command: AT+CIMI May 30 08:35:12 RedTail bluetoothd[4864]: /org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd11: fd(23) ready May 30 08:37:26 RedTail bluetoothd[4864]: Audio connection got disconnected May 30 08:37:55 RedTail kernel: [63376.126544] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126559] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126566] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126572] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126578] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126584] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126590] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126595] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126601] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126606] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126612] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126617] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126623] Bluetooth: hci0 SCO packet for unknown connection handle 7936 May 30 08:37:55 RedTail kernel: [63376.126629] Bluetooth: hci0 SCO packet for unknown connection handle 48 May 30 08:37:55 RedTail kernel: [63376.126635] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126641] Bluetooth: hci0 SCO packet for unknown connection handle 0 May 30 08:37:55 RedTail kernel: [63376.126647] Bluetooth: hci0 SCO packet for unknown connection handle 0 ... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-2-generic (not installed) ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6 Uname: Linux 3.15.0-2-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: chris 3967 F...m pulseaudio /dev/snd/pcmC1D0p: chris 3967 F...m pulseaudio /dev/snd/controlC1: chris 3967 F pulseaudio /dev/snd/controlC0: chris 3967 F pulseaudio CurrentDesktop: Unity Date: Fri May 30 08:56:58 2014 InstallationDate: Installed on 2013-08-06 (296 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Yup. Reproduced on 3.19 final. ** 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/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: Confirmed Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
I think I may have mis-remembered encountering the bug in 3.16; I'm pretty sure the broken commit referenced in https://lkml.org/lkml/2014/10/9/733 was in 3.17 but not 3.16. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
I am just in the process of rebooting that server. I'll check that the filesystem mounts, and then close the bug. If for some reason I forget about reporting back, that probably means that everything's worked. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Sorry, no dice: [ 1101.894735] kernel BUG at /build/buildd/linux-3.19.0/fs/btrfs/inode.c:3142! [ 1101.894862] invalid opcode: [#1] SMP [ 1101.894952] Modules linked in: binfmt_misc rc_it913x_v2 it913x kvm_amd amdkfd amd_iommu_v2 kvm radeon af9033 ttm drm_kms_helper dvb_usb_af9035 dvb_usb_v2 dvb_core amd64_edac_mod drm k10temp edac_core edac_mce_amd rc_core i2c_algo_bit shpchp i2c_piix4 tpm_infineon mac_hid autofs4 btrfs xor raid6_pq pata_acpi ahci tg3 ptp pps_core libahci pata_atiixp [ 1101.895721] CPU: 0 PID: 2536 Comm: btrfs-cleaner Not tainted 3.19.0-12-generic #12-Ubuntu [ 1101.895866] Hardware name: HP ProLiant MicroServer, BIOS O41 10/01/2013 [ 1101.895991] task: 88009fa02740 ti: 88009c83 task.ti: 88009c83 [ 1101.896124] RIP: 0010:[] [] btrfs_orphan_add+0x1c0/0x1e0 [btrfs] [ 1101.896339] RSP: 0018:88009c833c38 EFLAGS: 00010286 [ 1101.896436] RAX: ffe4 RBX: 8800a2320800 RCX: 8800a80dd000 [ 1101.896563] RDX: 019c RSI: 0004 RDI: 8800a80dd138 [ 1101.896689] RBP: 88009c833c78 R08: 8800a4c3ef28 R09: c010fafa [ 1101.896814] R10: 88011fc1d790 R11: ea0002d8ff00 R12: 8800a4d81100 [ 1101.896940] R13: 8800d2051420 R14: 8800a2320c58 R15: 0001 [ 1101.897068] FS: 7fc96ca70740() GS:88011fc0() knlGS: [ 1101.897211] CS: 0010 DS: ES: CR0: 8005003b [ 1101.897313] CR2: 7fc5b37e7000 CR3: d1991000 CR4: 07f0 [ 1101.897439] Stack: [ 1101.897479] 88009c833c78 c017dd0d 8800a80dd000 8800a69dd000 [ 1101.897632] 8800b63fc090 8800a4d81100 88009cf8c800 8800b6264000 [ 1101.897784] 88009c833d08 c01292ca 8800b63fc098 8800b63fc110 [ 1101.897936] Call Trace: [ 1101.898031] [] ? lookup_free_space_inode+0xcd/0xf0 [btrfs] [ 1101.898189] [] btrfs_remove_block_group+0x13a/0x760 [btrfs] [ 1101.898358] [] btrfs_remove_chunk+0x63a/0x760 [btrfs] [ 1101.898507] [] btrfs_delete_unused_bgs+0x249/0x270 [btrfs] [ 1101.898664] [] cleaner_kthread+0x144/0x1a0 [btrfs] [ 1101.898808] [] ? check_leaf+0x360/0x360 [btrfs] [ 1101.898927] [] kthread+0xc9/0xe0 [ 1101.899019] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 1101.899141] [] ret_from_fork+0x58/0x90 [ 1101.899242] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 1101.899358] Code: 60 04 00 00 e9 b0 fe ff ff 66 90 89 45 c8 f0 41 80 64 24 80 fd 4c 89 e7 e8 9e 21 fe ff 8b 45 c8 e9 1b ff ff ff 66 0f 1f 44 00 00 <0f> 0b b8 f4 ff ff ff e9 10 ff ff ff 4c 89 f7 45 31 f6 e8 e9 93 [ 1101.900087] RIP [] btrfs_orphan_add+0x1c0/0x1e0 [btrfs] [ 1101.900251] RSP [ 1101.918149] ---[ end trace 02688f585e76e0a8 ]--- chris@Bebop:~⟫ uname -a Linux Bebop 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:26 UTC 2015 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/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Hm. The rc7 kernel doesn't seem to have that bug, but it *does* seem to have deleted all but 50MB of data on that array. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
So, let's call that a qualified success? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] [NEW] Kernel BUG shortly after mounting btrfs filesystem
Public bug reported: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: New Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Relevant snippet of dmesg: [ 70.591237] BTRFS info (device sdd): disk space caching is enabled [ 71.428714] BTRFS: bdev /dev/sdc errs: wr 0, rd 0, flush 0, corrupt 371004212, gen 0 [ 102.225649] [ cut here ] [ 102.225748] kernel BUG at /build/buildd/linux-3.18.0/fs/btrfs/inode.c:3123! [ 102.225871] invalid opcode: [#1] SMP [ 102.225950] Modules linked in: radeon kvm_amd kvm ttm amd64_edac_mod drm_kms_helper k10temp edac_core edac_mce_amd drm i2c_algo_bit tpm_infineon sp5100_tco i2c_piix4 shpchp mac_hid autofs4 btrfs xor raid6_pq pata_acpi hid_generic tg3 usbhid hid pata_atiixp ptp pps_core ahci libahci [ 102.226483] CPU: 1 PID: 1456 Comm: btrfs-cleaner Not tainted 3.18.0-9-generic #10-Ubuntu [ 102.226624] Hardware name: HP ProLiant MicroServer, BIOS O41 10/01/2013 [ 102.226748] task: 8800d2aaa800 ti: 8800d2ba8000 task.ti: 8800d2ba8000 [ 102.226878] RIP: 0010:[] [] btrfs_orphan_add+0x1c0/0x1e0 [btrfs] [ 102.227089] RSP: 0018:8800d2babc38 EFLAGS: 00010286 [ 102.227183] RAX: ffe4 RBX: 88011914b800 RCX: 8800d193d000 [ 102.227306] RDX: 019a RSI: 0004 RDI: 8800d193d138 [ 102.227429] RBP: 8800d2babc78 R08: 8800d0e0f7b8 R09: c03ad66a [ 102.227551] R10: 88011fc9cbe0 R11: ea00046ca040 R12: 8800d0e19910 [ 102.227674] R13: 88011b0d62c0 R14: 88011914bc58 R15: 0001 [ 102.227798] FS: 7fcbf6678700() GS:88011fc8() knlGS: [ 102.227938] CS: 0010 DS: ES: CR0: 8005003b [ 102.228038] CR2: 7fcbf5260d68 CR3: d2fd7000 CR4: 07e0 [ 102.228160] Stack: [ 102.228197] 8800d2babc78 c041b61d 8800d193d000 8800d0b66000 [ 102.228334] 88011b281120 0002 8800d0e19910 8800d2ae7600 [ 102.228470] 8800d2babd08 c03c6d66 88011b281128 88011b2811a0 [ 102.228605] Call Trace: [ 102.228695] [] ? lookup_free_space_inode+0xcd/0xf0 [btrfs] [ 102.228847] [] btrfs_remove_block_group+0x136/0x520 [btrfs] [ 102.229012] [] btrfs_remove_chunk+0x68b/0x800 [btrfs] [ 102.229157] [] btrfs_delete_unused_bgs+0x21e/0x250 [btrfs] [ 102.229308] [] cleaner_kthread+0x154/0x1b0 [btrfs] [ 102.229449] [] ? check_leaf+0x360/0x360 [btrfs] [ 102.229563] [] kthread+0xdb/0x100 [ 102.229655] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 102.229773] [] ret_from_fork+0x7c/0xb0 [ 102.229870] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 102.229983] Code: 60 04 00 00 e9 b0 fe ff ff 66 90 89 45 c8 f0 41 80 64 24 80 fd 4c 89 e7 e8 ee 23 fe ff 8b 45 c8 e9 1b ff ff ff 66 0f 1f 44 00 00 <0f> 0b b8 f4 ff ff ff e9 10 ff ff ff 4c 89 f7 45 31 f6 e8 29 7b [ 102.230511] RIP [] btrfs_orphan_add+0x1c0/0x1e0 [btrfs] [ 102.230669] RSP [ 102.230794] ---[ end trace 7bb8d319159a4c32 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: New Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dm
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Relevant to my interests: https://lkml.org/lkml/2014/10/9/733 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Confirmed Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] [NEW] USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Public bug reported: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: New Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.07
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Ah, there we go. Reproduced on: Linux RedTail 3.19.0-031900rc5-generic #201501180935 SMP Sun Jan 18 09:36:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Tags added: kernel-bug-exists-upstream ** 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/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: Confirmed Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
>From memory it has occurred in all the Vivid kernels; I can't recall whether or not it applied to earlier kernels. I'll test the rc6 kernel, but is there any particular reason to think it got fixed since rc5? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: Confirmed Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
(This means it has occurred at least as far back as the 3.16 kernel) ** 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/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: Confirmed Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
I have not yet reproduced it with 3.19-rc6, but it generally only happens about once a day, and I'm in Brussels for this week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in linux package in Ubuntu: Incomplete Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Just to ensure unambiguous communication: I cannot test, as testing the 4.0-rc7 kernel destroyed the filesystem that exhibited this bug for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Incomplete Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Yes, unless someone else can reproduce. I haven't had a filesystem that triggers this since the test kernel which mounted the broken filesystem but destroyed all the data. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Incomplete Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 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: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252874] Re: Kernel panic shortly after pairing Apple Magic Touchpad
Hm. I don't think I've ever successfully used the Apple touchpad with this laptop; I've only recently started to try. I'll give the 3.11 final kernel a try 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/1252874 Title: Kernel panic shortly after pairing Apple Magic Touchpad Status in “linux” package in Ubuntu: In Progress Bug description: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello Alberto, or anyone else affected, Accepted nvidia-settings into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia- settings/331.20-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1259237] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304-updates/304.116-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello Alberto, or anyone else affected, Accepted screen-resolution-extra into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /screen-resolution-extra/0.14ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: screen-resolution-extra (Ubuntu Precise) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1259237] Please test proposed package
Hello Alberto, or anyone else affected, Accepted lightdm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252874] [NEW] Kernel panic shortly after pairing Apple Magic Touchpad
Public bug reported: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "Kern.log showing the part of the panic that made it to disc." https://bugs.launchpad.net/bugs/1252874/+attachment/3912858/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252874 Title: Kernel panic shortly after pairing Apple Magic Touchpad Status in “linux” package in Ubuntu: New Bug description: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/Lis
[Kernel-packages] [Bug 1252874] Re: Kernel panic shortly after pairing Apple Magic Touchpad
I've tried Andy's kernels from http://people.canonical.com/~apw /unstable-trusty/, but I can't tell whether this is fixed in 3.13 or not - bluetooth entirely fails to work in 3.13. bluetoothd repeatedly spawns and crashes, with: [ 31.268389] general protection fault: [#2] SMP [ 31.268418] Modules linked in: rfcomm bnep binfmt_misc joydev x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nls_iso8859_1 microcode arc4 psmouse serio_raw ath9k snd_hda_codec_via snd_seq_midi ath9k_common snd_seq_midi_event ath9k_hw snd_rawmidi ath snd_hda_codec_hdmi uvcvideo mac80211 videobuf2_vmalloc snd_hda_intel videobuf2_memops videobuf2_core snd_hda_codec snd_seq videodev snd_hwdep snd_seq_device ath3k cfg80211 snd_pcm lpc_ich btusb bluetooth rtsx_pci_ms snd_page_alloc memstick snd_timer snd mei_me mei soundcore mac_hid lp parport dm_crypt usb_storage rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 i915 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit e1000e drm_kms_helper ahci libahci drm rtsx_pci ptp pps_core wmi video [ 31.269003] CPU: 0 PID: 1165 Comm: bluetoothd Tainted: G D 3.13.0-0-generic #1~unstable201311192152 [ 31.269075] Hardware name: System76, Inc. Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013 [ 31.269138] task: 880402ac6000 ti: 8804093e task.ti: 8804093e [ 31.269195] RIP: 0010:[] [] rfcomm_sock_getsockopt+0x10b/0x290 [rfcomm] [ 31.269272] RSP: 0018:8804093e1f00 EFLAGS: 00010246 [ 31.269309] RAX: b8763f78eb76 RBX: 0012 RCX: 7fff73fcef88 [ 31.269360] RDX: 0003 RSI: 0012 RDI: 880404493700 [ 31.269411] RBP: 8804093e1f38 R08: 7fff73fcef8c R09: 7fff73fcf208 [ 31.269462] R10: 88040f010430 R11: 0202 R12: 88040932ec00 [ 31.269514] R13: 7fff73fcef88 R14: 0003 R15: 880404493700 [ 31.269565] FS: 7f86afcb5740() GS:88041fa0() knlGS: [ 31.269622] CS: 0010 DS: ES: CR0: 80050033 [ 31.269662] CR2: 7f86aef2bec0 CR3: 000406aa9000 CR4: 001407f0 [ 31.269707] Stack: [ 31.269720] 0246 8804093e1f58 880404493700 0012 [ 31.269775] 0003 7fff73fcef88 7fff73fcef8c 8804093e1f78 [ 31.269833] 81614448 0001 7fff73fcf208 [ 31.269896] Call Trace: [ 31.269923] [] SyS_getsockopt+0x68/0xd0 [ 31.269973] [] tracesys+0xe1/0xe6 [ 31.270010] Code: f1 48 83 c4 10 44 89 c8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 4d 8b 67 20 f6 05 47 6f 00 00 04 49 8b 84 24 e8 02 00 00 <48> 8b 18 0f 85 48 01 00 00 4c 89 c0 e8 f4 52 d7 e0 85 c0 49 89 [ 31.270233] RIP [] rfcomm_sock_getsockopt+0x10b/0x290 [rfcomm] [ 31.270294] RSP [ 31.270322] ---[ end trace cd2dc7599da16d4a ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252874 Title: Kernel panic shortly after pairing Apple Magic Touchpad Status in “linux” package in Ubuntu: Confirmed Bug description: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc,
[Kernel-packages] [Bug 1252874] Re: Kernel panic shortly after pairing Apple Magic Touchpad
Oh, the getsockopt bug might be http://www.spinics.net/lists/linux- wireless/msg114186.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/1252874 Title: Kernel panic shortly after pairing Apple Magic Touchpad Status in “linux” package in Ubuntu: In Progress Bug description: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252874] Re: Kernel panic shortly after pairing Apple Magic Touchpad
The 3.11 kernel also panics in the same circumstances ; I can't tell if it's *exactly* the same panic, because the log didn't make it to disc, but it's triggered in the same way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252874 Title: Kernel panic shortly after pairing Apple Magic Touchpad Status in “linux” package in Ubuntu: In Progress Bug description: My kernel reliably panics shortly after - maybe 10 seconds or so? - pairing an Apple Magic Touchpad. Other bluetooth devices don't cause the same problem - I've tried a pair of bluetooth headphones, a bluetooth speaker, a bluetooth printer, and a Nexus 4; all of these work as expected. This would seem to suggest a problem in hid_magicmouse? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2576 F pulseaudio /dev/snd/controlC0: chris 2576 F pulseaudio Date: Wed Nov 20 08:26:11 2013 InstallationDate: Installed on 2013-08-06 (105 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-08-06 (105 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
FWIW I can't recall getting this error on the 4.2 kernels currently in Wily. This might be fixed in 15.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489045] Update Released
The verification of the Stable Release Update for dkms has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1489045 Title: Backport autopkgtest script to precise/trusty Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Precise: Fix Released Status in dkms source package in Trusty: Fix Committed Bug description: The kernel team has requested that we run DKMS tests via autopkgtests for precise and trusty the same way that we now do for vivid and upwards. For this we need to backport debian/scripts/dkms-autopkgtest from https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu1. TEST CASE: Run autopkgtest for a DKMS package: adt-run bcmwl --- qemu adt-trusty-amd64-cloud.img # or use a precise image, or "--- lxc " This currently fails with adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest adt-run [15:18:24]: test command1: [--- bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory With the proposed packages this should work and look more like Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu4) ... Loading new bcmwl-6.30.223.248+bdcom DKMS files... First Installation: checking all kernels... Building only for 4.1.0-3-generic Building for architecture x86_64 Building initial module for 4.1.0-3-generic Done. wl: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.1.0-3-generic/updates/dkms/ depmod DKMS: install completed. update-initramfs: deferring update (trigger activated) Setting up libfakeroot:amd64 (1.20.2-1ubuntu1) ... Setting up fakeroot (1.20.2-1ubuntu1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up manpages-dev (3.74-1ubuntu1) ... Processing triggers for initramfs-tools (0.120ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic I: Testing binary package bcmwl-kernel-source I: Testing if bcmwl modules are correctly installed bcmwl, 6.30.223.248+bdcom, 4.1.0-3-generic, x86_64: installed adt-run [17:23:43]: test command1: ---] REGRESSION POTENTIAL: Almost zero. dkms is an arch: all package, thus no miscompilation possible. The new script is not being used in dkms' actual operation, only when being invoked through autopkgtest. As every DKMS package test fails right now, there is no test regression possible either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1489045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
This is a bit more difficult, because the primary way that users get zfs in Ubuntu is via the module built with the *kernel* image. My understanding is that fixing that requires a zfs-linux upload and then a further kernel upload to pull in the new zfs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
I've run that debugging script. Unfortunately, Launchpad currently OOPSes when I try to attach the output to the bug. I'll keep trying every now and then. The throttling did not occur during that test, and doesn't seem to have occurred while running the build of thermald from git, but this does not necessarily mean the bug doesn't still occur. I'll continue running the build of thermald from git. Should I catch it in the bug-state, I'll re-collect the output of that script. -- 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/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels
Hm. It's not clear what the actual user impact of this is? Reading from the original description, it seems that if a user uses an invalid label to set one address and *also* uses a valid label to set another address *then* tools can be confused? “Our parser is actually more lenient than the manpage states” on its own is definitely not SRU-worthy, but if it breaks other tools then maybe? On the other hand, from the bug it looks like if you *don't* mix valid and invalid labels then everything actually works? So this would potentially be breaking currently working setups? I think we need more information before determining whether this should be accepted as an SRU. ** Changed in: iproute2 (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Incomplete Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test [Where problems could occur] * While the fix indeed "corrects" behavior I must say that if someone relied on the non-intended behavior it would now break e.g. his scripting or automation. [Other Info] * It was too easy to fix and too long dormant to ignore it further, but if the SRU team says this is too much regression risk relative to the gain we will mark it Won't Fix based on that decision. --- ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
For some reason this doesn't seem to have the normal SRU verification tags, but this appears to be verified to me. Releasing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
Hello Andrew, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.14 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == SRU Focal/Hirsute == [Impact] ZFS: Fix a panic while acquiring a lock. If TX_WRITE is create on a file, and the file is later deleted and a new directory is created on the same object id, it is possible that when zil_commit happens, zfs_get_data will be called on the new directory. This may result in panic as it tries to do range lock. Upstream ZFS bug #10593, #11682, upstream fix: commit 296a4a369bc1078a694f88570972330985b3b1b8 Author: Chunwei Chen Date: Fri Mar 19 22:53:31 2021 -0700 Fix zfs_get_data access to files with wrong generation This patch fixes this issue by record the generation number during zfs_log_write, so zfs_get_data can check if the object is valid. The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a relatively simple backport with only minor backporting effort required in moving some of the module specific upstream changes into the pre- renamed module specific os specific parts of the ZFS module. [Test Plan] This is difficult to reproduce, see https://github.com/openzfs/zfs/issues/10593 The fix has been tested with the complete ubuntu autotest ZFS regression tests that exercise ZFS core functionality (smoke tests), file system POSIX compliance (fs tests), extra XFS tests and every mount option with stress-ng file I/O stress tests. [Where problems could occur] This fix could regress the ZIL (ZFS intent log) commit writes since it modifies this code to now checks for generation numbers. Testing with ZFS autotests with intent logs have not found any regressions, but there is a risk that the ZIL functionality is affected. This could lead to corruption. -- As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039731] Re: After upgrade 20.04 LTS -> 23.10, closing laptop lid causes all GUI apps to be quit
An interesting test might be to run “echo mem | sudo tee
/sys/power/state” from a terminal; this will *just* get the kernel to
suspend, without executing any other suspend hooks (like locking the
screen, etc).
I concur with “that person on Mastodon” (☺), though; it looks a lot like
that mutter bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2039731
Title:
After upgrade 20.04 LTS -> 23.10, closing laptop lid causes all GUI
apps to be quit
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a brand new Lenovo ThinkPad T14 (AMD) Gen 3 with touchscreen. I
was told this is a good laptop for Linux and Lenovo says it is
"certified" on Ubuntu 20.04.
Yesterday I installed Ubuntu 22.04 LTS off a USB stick. It worked
pretty well. Later in the day I decided to upgrade to a newer Ubuntu
and installed Ubuntu 23.10 off a USB stick (I did not upgrade, I told
it to delete the partition and create a new one). This has had a
couple new, serious problems (see also
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/2039722 ).
With 23.10 I am seeing a behavior where if I close the lid, wait for
the red light on the Thinkpad logo to begin blinking to indicate it is
in sleep, then open the lid, it asks me to log in, and when I log in I
am looking at a new, blank desktop session. All my apps have been
quit. I see this behavior both when I am plugged into power and when I
am not plugged into power. I am 95% certain I did not see this
yesterday in 22.04 LTS. I closed and reopened the laptop multiple
times.
I have made fumbling attempts to fix this myself but because this is a
common laptop, Lenovo-certified with Ubuntu, with default settings,
and I *THINK* it is a regression (seemed to work with 22.04 LTS?) I
think it should work out of the box.
MY FUMBLING ATTEMPTS TO FIX THIS MYSELF
I learned Linux on servers and before the systemd era. I do not
currently know how to find out: - Where is there a log of which
applications have crashed, and when? - Where is there a log of
reboots? On Windows there is an "event viewer" which tells you the
last reboot (and whether it was caused by a power event, the OS or
user requesting the reboot, or what). At the moment I don't know in
Linux if it is trying to hibernate and failing, intentionally powering
down, or if it is correctly hibernating and waking but at some step a
critical software (like the wayland server) is dying. I am happy to
gather any information needed.
The Arch wiki, which in my experience is often a good source of
general Linux information, has a page on this device
https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14_(AMD)_Gen_3
containing the suspicious line:
"According to Lenovo staff the CPU generation in this device only
supports s2idle and not S3 sleep."
They recommend running: $ cat /sys/power/mem_sleep to see what suspend
methods are "advertised". This file contains only the line "[s2idle]".
The arch wiki says that "shallow" or "deep" should be next to s2idle
and I want to pick one of them. But I don't see either of those so I
don't know how to proceed. Google searching seems to imply that this
is about hibernating vs going into some special mode. Arch wiki also
says:
"If you run system firmware version 0.1.17 do not set the suspend mode
in UEFI setup to Linux (S3). This sleep mode is not supported by the
CPU. If you set S3 mode and upgrade the system firmware you need to do
a downgrade to 0.1.17 to change it back, because the option is removed
in newer firmware. If you set S3 mode nevertheless and try to suspend
to mem/S3 mode the system will crash and you need to reset it by
holding the power button for a few seconds."
I have not yet explored this in the pre-OS UEFI settings but will try
that after filing this bug.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 15:08:29 2023
InstallationDate: Installed on 2023-10-18 (1 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=ecb1730b-cbe1-457c-a4f8-23e2eaf89020 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux
[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
So, the test plan was:
```
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-generated
known affected vmcore to compress it. The unpatched version fails.
```
I'm not familiar with this area, but as far as I can tell only the 3rd
step has been tested here? Am I misunderstanding the comments, or have
we missed some of the test plan?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Ok. My understanding of this is that when (3) fails it fails for the
same reason that (2) would. We've verified that making a dumpfile works
in general, and definitely fixed (3), so I'm going to release this now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970672] Update Released
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
So, looking at 2.1.14 in lunar-proposed - This is not bugfix-only (or even bugfix and hardware-enablement only - it includes, at least, changes to colourise the output of some commands). Also, I think this will introduce bug #2046082 into lunar and jammy? I see we've accepted some ZFS micro-releases in the past. I'm not familiar with the circumstances surrounding those, but I'm uncomfortable with this one. It seems clear that zfs upstream do not have the same expectations of stable releases as we do, so I'm not confident that just taking an upstream microrelease will be acceptable. I'm not saying a hard “no”, but what investigation was done to determine how much effort cherry-picks to jammy/lunar would be? What are the actual set of changes between 2.1.9 (/2.1.5 for jammy) and 2.1.14, and are any of those changes maybe unsuitable for an SRU? We don't appear to have any special process documented for zfs - maybe we should? Regressions have extremely high potential impact but at the same time we *do* need to sometimes make significant updates for hardware enablement, and, to the best of my knowledge, unlike the hwe kernel the zfs changes are not opt-in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Additionally: my understanding is that the corruption fix is minimally invasive and should be easy to backport. Should we quickly do such a minimal backport to get that fix out quickly, and then have less pressure to handle the hardware enablement kernel quickly? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072643] Update Released
The verification of the Stable Release Update for ipu6-drivers has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2072643
Title:
Embedded camera using camera sensors ov02e10 and ov08a10 doesn't work:
missing kernel driver
Status in OEM Priority Project:
New
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux-signed-oem-6.5 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Jammy:
Won't Fix
Status in linux-signed-oem-6.5 source package in Jammy:
New
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux-signed-oem-6.5 source package in Noble:
Invalid
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux-signed-oem-6.5 source package in Oracular:
Invalid
Bug description:
[SRU Justfication]
[Impact]
Device camera won't work.
[Fix]
The current version in -proposed pocket may skip installation of built
kernel module ov02e10 and ov08a10. The fix is to use fixed index
numbers in dkms.conf.
[Test Case]
Install the dkms and check if ov02e10.ko and ov08a10.ko have been
installed to /lib/modules//updates/dkms.
[Where problems could occur]
Minimal, as this is restoring driver modules that were previously
installed prior to the regression.
[Other Info]
While this happens to ipu6-drivers/{oracualr,noble} only, proposed
fixes are therefore nominated accordingly.
== original bug report =
Description: Ubuntu 22.04.4 LTS
Release: 22.04
linux-oem-22.04d 6.5.0.1026.28
com.canonical.certification::camera/camera-quality_video0 test fails:
[ WARN:0] global ./modules/videoio/src/cap_gstreamer.cpp (1100) open OpenCV |
GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
/bin/sh: 1: kill: Illegal number: -
Traceback (most recent call last):
File
"/tmp/nest-oh_l6kjy.e6eacba27b81ed7929f808c3af9ceaf803facf6256ab97b917f65943c394f09d/camera_quality_test.py",
line 178, in
sys.exit(main(sys.argv[1:]))
File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py",
line 93, in _f
return run_with_timeout(f, timeout_s, *args, **kwargs)
File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py",
line 78, in run_with_timeout
raise TimeoutError("Task unable to finish in {}s".format(timeout_s))
TimeoutError: Task unable to finish in 120s
It passed on 6.5.1024.25 on the same device.
It fails on all Dell Oasis MTL machines
202312-33186 (usbio, ov02e10)
202312-33187 (usbio, ov02e10)
202312-33214 (usbio, hi556, checkbox test pass)
202312-33215 (usbio, hi556, checkbox test pass)
202312-32371 (usbio, hi556, checkbox test pass)
202312-32372 (usbio, ov02e10)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-1026-oem 6.5.0-1026.27
ProcVersionSignature: Ubuntu 6.5.0-1026.27-oem 6.5.13
Uname: Linux 6.5.0-1026-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jul 10 06:38:38 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-oddish13+X120
InstallationDate: Installed on 2024-02-27 (134 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
SourcePackage: linux-signed-oem-6.5
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2072643/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hello cipricus, or anyone else affected, Accepted apparmor into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-noble ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
** Attachment added: "thermald debug script output" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+attachment/5539066/+files/try-again.tar.zstd -- 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/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
