[Kernel-packages] [Bug 1767324] Re: Extreme regression in battery autonomy with kernel 4.15
As per jacob's comment have added the tag and changed to Confirmed, Joseph do you know how this bug should be progressed? Where it should be forwarded upstream or what further debug work could be done? A test against a yet newer kernel probably wouldn't go amiss but not sure not doing that should put the bug back to Incomplete since then we may always be behind. ** 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/1767324 Title: Extreme regression in battery autonomy with kernel 4.15 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts less than one hour on a fully charged battery. On Ubuntu 17.10 with kernel 4.13, the autonomy was typically in excess of 5 hours. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-lowlatency 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jzimm 3538 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:10:02 2018 InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-lowlatency N/A linux-backports-modules-4.15.0-20-lowlatency N/A linux-firmware1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749277] Re: [nfp] NIC stops transmitting for small MSS values when TSO is enabled
Does that mean you can close this bug as Fix Released then (presumably Invalid for Backports)? :) -- 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/1749277 Title: [nfp] NIC stops transmitting for small MSS values when TSO is enabled Status in Bionic Backports: New Status in linux-firmware package in Ubuntu: New Bug description: Description of problem: When TCP Segmentation Offload (TSO) is enabled on Netronome Agilio SmartNICs, the interface TX ring hangs when sending packets that require more than 64 segments to send. Steps to reproduce: 1. Enable TSO (ethtool -K tso on) 2. Run an iperf session with a suitably small MSS Actual results: The iperf traffic rate drops to zero, after which, the NIC accepts no more TX packets. Expected results: The iperf session should complete normally. Suggested resolution: This bug has been fixed in version 2.0.4 of the Agilio SmartNIC firmware available in the upstream linux-firmware repository as of commit 2a91ed954213eabc90154ccd682cbfed7195c4b0. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=2a91ed954213eabc90154ccd682cbfed7195c4b0 Please backport as appropriate into Bionic and other releases. To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1749277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Sorry if this question has already been dealt with (in which case, may be nice to have it in the bug description) but has there been an update released which automatically fixes the issue for people affected? I'm sure there are many who wouldn't realize that their BIOS is broken for a while (or have already realized) and then wouldn't know to come here to find a fix... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Only two days ago this was posted by Canonical employee Anthony Wong: '@britgreek Even though we now have a kernel that can prevent the issue happening, we are still finding the root cause with Lenovo, please be patient.' Saying 'me too' 'any more news' and 'what's the ETA on this' will not help the bug to be fixed faster. They know this bug is serious, you can mark yourself as affected by this bug with the button at the top (and maybe you could check that your friends who are affected have also done so) and then you'll just have to be patient! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
** Tags added: xenial ** Tags added: yakkety -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477593] Re: nvidia-340-updates 340.76-0ubuntu2: nvidia-340-updates kernel module failed to build [FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'flush_
** Tags added: yakkety -- 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/1477593 Title: nvidia-340-updates 340.76-0ubuntu2: nvidia-340-updates kernel module failed to build [FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'flush_workqueue'] Status in bcmwl package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352 package in Ubuntu: Fix Released Bug description: Dont build modules nvidia for kernel 4.2.* ProblemType: Package DistroRelease: Ubuntu 15.04 Package: nvidia-340-updates 340.76-0ubuntu2 [modified: usr/src/nvidia-340-updates-340.76/nv-pat.c] Uname: Linux 4.1.2-040102-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 DKMSKernelVersion: 4.2.0-040200rc3-generic Date: Thu Jul 23 16:46:29 2015 InstallationDate: Installed on 2015-05-25 (58 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageVersion: 340.76-0ubuntu2 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: nvidia-graphics-drivers-340-updates Title: nvidia-340-updates 340.76-0ubuntu2: nvidia-340-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1477593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
