[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Brad, they cannot support BIOS flashing because they are changing pc components every batch. Jumper sells for very few something that we know is "as it". The touchpad is working, I can use it at 100% on Windows 10, the issue should be fixed by software BUT we need a fix 'ad personam'... is it worth it? -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1737913 Title: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737911 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737913/+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 1737911] Re: linux: 3.13.0-138.187 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1737911 Title: linux: 3.13.0-138.187 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737913 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737911/+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 1663727] Re: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors
I went ahead and tried to file an upstream bug at bugzilla but apparently this bug has previously been reported and fixed. Anydoby interested can go and read the link below. https://bugs.freedesktop.org/show_bug.cgi?id=34457 Basically this is what you have to do. QUOTE "Either upgrade your system to Ubuntu Oneiric or install the fixed kernel (with backported kernel patches) from Launchpad PPA for Ubuntu Maverick. Both solutions will fix the problem, as it did for the others having this special buggy chipset." END OF QUOTE. Thank you. ** Bug watch added: freedesktop.org Bugzilla #34457 https://bugs.freedesktop.org/show_bug.cgi?id=34457 -- 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/1663727 Title: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors Status in linux package in Ubuntu: Confirmed Bug description: I've just performed an "apt-get update" on a Dell 2950 Server - which was already running 16.04.1 and now it's spewing EDID errors - I'm not sure what changed from 16.04.1 to 16.04.2.. I've attached dmesg to this, but basically it's dumping the following in logs and to the screen. [drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but no|invalid EDID --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 10 13:51 seq crw-rw 1 root audio 116, 33 Feb 10 13:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=97c6470f-0ecf-4fda-8400-9dcded48500c InstallationDate: Installed on 2014-04-18 (1034 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. PowerEdge 2950 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=089f7527-5b99-4ebc-9092-cd4461eebeb9 ro ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (206 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/30/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.0 dmi.board.name: 0H603H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.0:bd10/30/2010:svnDellInc.:pnPowerEdge2950:pvr:rvnDellInc.:rn0H603H:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge 2950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663727/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I really need some ideas, here's my situation: I formatted my SSD, my BIOS is in UEFI mode with secure boot enabled and i can't change any settings. I can only boot from PXE over network ipv4 / ipv6. I tried to install ubuntu on my SSD with another computer but an user noticed me that EFI boot is looking for an UUID partition of ubuntu that it changed after i formatted my drive. So i thought that the solution was install successfully ubuntu on my SSD in my stucked laptop and then through efibootmgr command i were able to read which UUID i need to setup into the partition to make the OS bootable. Using AIOBOOT i'm able to boot grub2 and creating a bootable image of ubuntu the installation begins but it stops for some reason (i think uefi blocked the installation). In this situation i don't know how to do a kernel update to fix the BIOS. If anyone have a UEFI (with secure boot) compatible guide to boot and install linux please tell us, i think it's the only way to fix our laptops -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737916] Re: linux: 4.4.0-105.128 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1737916 Title: linux: 4.4.0-105.128 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737918,1737919 derivatives: 1737920,1737921,1737922,1737923,1737925,1737927 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737916/+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 1716819] Re: Ubuntu 17.04 does not wake up from suspension on MacBook Air 7, 2
** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716819 Title: Ubuntu 17.04 does not wake up from suspension on MacBook Air 7,2 Status in linux package in Ubuntu: New Bug description: I just upgraded my 16.04 to 17.04. Suspension does not work too well. Most of the times the computer does not wake up from suspension (closing the lid). I tried both opening the lid and pressing the power key on the keyboard to see if it would wake up, but I get nothing. No key press or mouse movement brings it back on. There is a subtle noise that suggests that the computer "tries" to turn back on, but the apple light on the back of the screen remains off. This was not as bad on 16.04 (I used to get a black screen, but still be able to type in my password and increase the screen brightness). -- Thanks in advance for your help! --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: dash 2355 F...m pulseaudio /dev/snd/controlC1: dash 2355 F pulseaudio /dev/snd/controlC0: dash 2355 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=89097c16-4307-467e-b6ef-1d3175493898 InstallationDate: Installed on 2016-04-29 (501 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir7,2 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-4.10.0-33-generic.efi.signed ro root=UUID=39e0c884-c808-46ba-ae10-b048fa5c49f8 initrd=boot\initrd.img-4.10.0-33-generic ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-09-11 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA71.88Z.0166.B13.1611031424 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-937CB26E2E02BB01 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir7,2 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-937CB26E2E02BB01 dmi.modalias: dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B13.1611031424:bd11/03/2016:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01: dmi.product.name: MacBookAir7,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716819/+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 1716819] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716819 Title: Ubuntu 17.04 does not wake up from suspension on MacBook Air 7,2 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded my 16.04 to 17.04. Suspension does not work too well. Most of the times the computer does not wake up from suspension (closing the lid). I tried both opening the lid and pressing the power key on the keyboard to see if it would wake up, but I get nothing. No key press or mouse movement brings it back on. There is a subtle noise that suggests that the computer "tries" to turn back on, but the apple light on the back of the screen remains off. This was not as bad on 16.04 (I used to get a black screen, but still be able to type in my password and increase the screen brightness). -- Thanks in advance for your help! --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: dash 2355 F...m pulseaudio /dev/snd/controlC1: dash 2355 F pulseaudio /dev/snd/controlC0: dash 2355 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=89097c16-4307-467e-b6ef-1d3175493898 InstallationDate: Installed on 2016-04-29 (501 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir7,2 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-4.10.0-33-generic.efi.signed ro root=UUID=39e0c884-c808-46ba-ae10-b048fa5c49f8 initrd=boot\initrd.img-4.10.0-33-generic ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-09-11 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA71.88Z.0166.B13.1611031424 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-937CB26E2E02BB01 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir7,2 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-937CB26E2E02BB01 dmi.modalias: dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B13.1611031424:bd11/03/2016:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01: dmi.product.name: MacBookAir7,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716819/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Sorry about the delay but we wanted to make sure the proposed fix can
recover the two test systems we have reliably before asking others to
try it.
I've attached a patch to this bug that should fix the still affected
systems. It applies on top of v4.15-rc6 and I'll be sending it upstream
as well. Canonical already created a kernel package including the fix
and it can be installed from the following link:
http://people.canonical.com/~ypwong/lp1734147/linux-
image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
The reason why v4.14.9 which includes 9d63f17661e2 ("spi-nor: intel-spi:
Fix broken software sequencing codes") recovers many systems but not all
is because:
- These systems have CMP=1 in the other status register (SR2) making
the flash read-only (this is the symptom).
- Linux SPI-NOR core clears status register properly for flash chips
that have SPI_NOR_HAS_LOCK set.
- Serial flashes automatically clear CMP and few other bits if 0 is
written to the first status register using WRSR command.
- In order to WRSR take effect the serial flash need to be write
enabled (WREN must have been issued before WRSR at some point).
- The systems that recovered the WREN was in effect (probably issued
by the BIOS before handing off to the OS) so when Linux writes 0 to
the status register CMP bit is also automatically cleared and the
problem goes away.
Those systems that were not recovered WREN was not in effect so clearing
the status register and CMP bit was ignored by the serial flash chip.
Normally WREN is send as a preopcode part of an atomic sequence when
software sequencing is used. This has been enabled since commit
8c473dd61bb5 ("spi-nor: intel-spi: Don't assume OPMENU0/1 to be
programmed by BIOS").
However, many systems have two write enable preopcodes available the
PREOP_OPTYPE register:
0x50 - Write enable for volatile status register
0x06 - Write enable (WREN)
The current code picks the former which does not enable write for
non-volatile bits so any writes to the status register non-volatile
bits, including BP0/1/2 protection bits do not take effect.
The attached patch changes the driver so that it prefers WREN over other
write enable preopcodes. Booting to the kernel with the patch applied on
a system where the issue still persists should reset the protection bits
and allow the BIOS to save settings again.
** Patch added:
"0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5030406/+files/0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
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:
Description: An update to linux kernel on Ubuntu 17.10 that enabled
the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
Settings being not stored, USB Boot impossible and EFI entries read-
only.
Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
affected machines still suffered from a broken BIOS.
Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
Linux and BIOS should be restored to a working state.
---
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 Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY
Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
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 (not fixed by 4.14.9)
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM
HP 14-r012la
---
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
[Kernel-packages] [Bug 1481347] Comment bridged from LTC Bugzilla
--- Comment From kalsh...@in.ibm.com 2018-01-03 04:59 EDT--- This is just a clarification on test support matrix to test Ubuntu distro on P9. As per my understanding, Power9 support officially will be there from Ubuntu 18.04 onwards. Test is committed to validate this P9 Nest PMU feature only on Ubuntu 18.04 at this point. Test team is not testing any of the P9 features on earlier releases of Ubuntu(artful or zesty or xenial SRU builds). -- 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/1481347 Title: Power8 Nest PMU Instrumentation support Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Fix Released Bug description: This is a bug for Canonical awareness that we want to have the following patches included in 15.10. They are still under development/review: https://patchwork.ozlabs.org/patch/482968/ https://patchwork.ozlabs.org/patch/482969/ https://patchwork.ozlabs.org/patch/482970/ https://patchwork.ozlabs.org/patch/482971/ https://patchwork.ozlabs.org/patch/482972/ https://patchwork.ozlabs.org/patch/482973/ https://patchwork.ozlabs.org/patch/482974/ Patches under review. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481347/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Ref #439 Mika I installed the kernel from your link with the patch and my Acer E3 - 111 notebook with the InsydeH20 BIOS is still not saving changes. In order to boot form USB i still have to boot GRUB2 - select c for prompt and then exit and wait for the PXE application to exit and USB drive is autoselected for boot. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690669] Re: Please build libxnvctrl0/-dev for s390x
** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: New => Triaged ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => Medium -- 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/1690669 Title: Please build libxnvctrl0/-dev for s390x Status in nvidia-settings package in Ubuntu: Triaged Bug description: The Debian version of this package is built for all architectures: https://buildd.debian.org/status/package.php?p=nvidia-settings Please do the same for Ubuntu also. In particular, qtwebengine-opensource-src needs libxnvctrl-dev (which depends on libxnvctrl0) to build on s390x. qtwebengine in turned is needed for the KDE PIM components (and probably other parts of the KDE platfrom). https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.7.1 +dfsg-6build1/+build/12459543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1690669/+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 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data
Thanks. That all looks fine then. > Regarding amd64 smoke test, I've been using the updated package on my machine (artful/amd64). Does that actually exercise the ip command though? Or are you using Network Manager, and does it speak to the kernel directly? -- 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/1732032 Title: ip maddr show and ip maddr show dev enP20p96s0 show different data Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: Fix Committed Status in iproute2 source package in Xenial: Fix Committed Status in iproute2 source package in Zesty: Fix Committed Status in iproute2 source package in Artful: Fix Committed Bug description: [Impact] When a nic has a long enough name such that there is no space between the name and the ":" in /proc/net/igmp, ip maddr show dev will miss the IPV4 addresses which is otherwise shown with "ip maddr show". This is inconsistent behavior and can break scripts and tests, as shown in this bug's original description. Three patches from upstream were taken to fix this bug, and they were used individually instead of being merged into one single patch so it's easier to track and recognize authorship: https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9 [Test Case] * deploy the ubuntu release under test. Please use bare metal or a VM instead of containers, because the ip tool parses a file in /proc. Make sure iproute2 is installed: sudo apt install iproute2 * Run these commands to setup a dummy interface with a long name and an IPv4 address. Please change the address if it conflicts with a real network you might have available on that machine: sudo ip link add dummylongnic0 type dummy sudo ip addr add 192.168.199.10/24 dev dummylongnic0 sudo ip link set dev dummylongnic0 up * Compare the output of these two commands with regards to the dummylongnic0 interface: sudo ip maddr show sudo ip maddr show dev dummylongnic0 * With the buggy iproute2 package installed, the more specific output "ip maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line: ip maddr show dev dummylongnic0 2:dummylongnic0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 inet6 ff02::1 inet6 ff01::1 Whereas the less specific command, which lists all interfaces, will have it listed for dummylongnic0: 2:dummylongnic0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 inet 224.0.0.1 inet6 ff02::1 inet6 ff01::1 * With the fixed iproute2 package, all dummylongnic0 addresses will be present in both outputs. [Regression Potential] In the end, the ip tool is parsing a text file produced by the kernel. As most parsing done in C, it's pretty low level and sensitive to changes in the file it's reading. [Other Info] I suggest to conduct the tests in VMs instead of containers (LXD) because the ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you use a container, then it's the host's kernel that will be providing that file and it might not be the same as with the native kernel of that particular ubuntu release. --- Original description --- Attn. Canonical: Please make sure that the existing iproute2 package gets updated with the two referenced patches as the missing information is impacting our standard test suites. Thanks. == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 == ---Problem Description--- ip maddr show and ip maddr show dev enP20p96s0 show different data ---uname output--- Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Steps to Reproduce--- run these at command line: root@roselp1:~# ip maddr show ... 10: enP20p96s0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 link 33:33:ff:6d:d0:d0 link 01:00:5e:00:00:fc link 33:33:00:01:00:03 inet 224.0.0.252 inet 224.0.0.1 inet6 ff02::1:3 inet6 ff02::1:ff6d:d0d0 users 3 inet6 ff02::1 inet6 ff01::1 ... root@roselp1:~# ip maddr show dev enP20p96s0 10: enP20p96s0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 link 33:33:ff:6d:d0:d0 link 01:00:5e:00:00:fc link 33:33:00:01:00:03
[Kernel-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
Hello All, For me the problem went away after I upgraded to Kubuntu 16.10. I no longer have a Linux box available to check with. However to those still experiencing the problem, first make sure you disabled the voice prompt on your bose headset: https://www.bose.com/en_us/support/article/disabling-voice-prompts- soundlink-mini-ii.html Verify prompt is disabled before testing. This is how the bug was manifesting for me initially. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741042] [NEW] ubuntu 17.00 kernel freeze
Public bug reported: My laptop hangs frequently, with a high cpu comsumption, don't react to Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B any other fn-alt-print screen combination doesn't works. I don't know how to trace what's wrong, or what component can be responsible. I have tried several X-servers, I have tried to disable hardware nvidia acceleration, etc. with no success ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-22-generic 4.13.0-22.25 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rogelio2095 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 3 13:37:36 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1 InstallationDate: Installed on 2017-05-04 (244 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-22-generic N/A linux-backports-modules-4.13.0-22-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful package-from-proposed -- 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/1741042 Title: ubuntu 17.00 kernel freeze Status in linux package in Ubuntu: New Bug description: My laptop hangs frequently, with a high cpu comsumption, don't react to Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B any other fn-alt-print screen combination doesn't works. I don't know how to trace what's wrong, or what component can be responsible. I have tried several X-servers, I have tried to disable hardware nvidia acceleration, etc. with no success ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-22-generic 4.13.0-22.25 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rogelio2095 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 3 13:37:36 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1 InstallationDate: Installed on 2017-05-04 (244 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-22-generic N/A linux-backports-modules-4.13.0-22-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications abo
[Kernel-packages] [Bug 1741042] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741042 Title: ubuntu 17.00 kernel freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop hangs frequently, with a high cpu comsumption, don't react to Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B any other fn-alt-print screen combination doesn't works. I don't know how to trace what's wrong, or what component can be responsible. I have tried several X-servers, I have tried to disable hardware nvidia acceleration, etc. with no success ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-22-generic 4.13.0-22.25 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rogelio2095 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 3 13:37:36 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1 InstallationDate: Installed on 2017-05-04 (244 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-22-generic N/A linux-backports-modules-4.13.0-22-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741042/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
On 3.1.2018 10:06, Mika Westerberg wrote:
> Sorry about the delay but we wanted to make sure the proposed fix can
> recover the two test systems we have reliably before asking others to
> try it.
>
> I've attached a patch to this bug that should fix the still affected
> systems. It applies on top of v4.15-rc6 and I'll be sending it upstream
> as well. Canonical already created a kernel package including the fix
> and it can be installed from the following link:
>
> http://people.canonical.com/~ypwong/lp1734147/linux-
> image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
>
> The reason why v4.14.9 which includes 9d63f17661e2 ("spi-nor: intel-spi:
> Fix broken software sequencing codes") recovers many systems but not all
> is because:
>
> - These systems have CMP=1 in the other status register (SR2) making
> the flash read-only (this is the symptom).
>
> - Linux SPI-NOR core clears status register properly for flash chips
> that have SPI_NOR_HAS_LOCK set.
>
> - Serial flashes automatically clear CMP and few other bits if 0 is
> written to the first status register using WRSR command.
>
> - In order to WRSR take effect the serial flash need to be write
> enabled (WREN must have been issued before WRSR at some point).
>
> - The systems that recovered the WREN was in effect (probably issued
> by the BIOS before handing off to the OS) so when Linux writes 0 to
> the status register CMP bit is also automatically cleared and the
> problem goes away.
>
> Those systems that were not recovered WREN was not in effect so clearing
> the status register and CMP bit was ignored by the serial flash chip.
>
> Normally WREN is send as a preopcode part of an atomic sequence when
> software sequencing is used. This has been enabled since commit
> 8c473dd61bb5 ("spi-nor: intel-spi: Don't assume OPMENU0/1 to be
> programmed by BIOS").
>
> However, many systems have two write enable preopcodes available the
> PREOP_OPTYPE register:
>
> 0x50 - Write enable for volatile status register
> 0x06 - Write enable (WREN)
>
> The current code picks the former which does not enable write for
> non-volatile bits so any writes to the status register non-volatile
> bits, including BP0/1/2 protection bits do not take effect.
>
> The attached patch changes the driver so that it prefers WREN over other
> write enable preopcodes. Booting to the kernel with the patch applied on
> a system where the issue still persists should reset the protection bits
> and allow the BIOS to save settings again.
>
> ** Patch added:
> "0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5030406/+files/0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch
>
Hi Mika,
The new kernel is installed and up and running.
Still unable to save settings in BIOS.
Leo
--
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:
Unknown
Status in linux package in Ubuntu:
Confirmed
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:
Description: An update to linux kernel on Ubuntu 17.10 that enabled
the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
Settings being not stored, USB Boot impossible and EFI entries read-
only.
Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
affected machines still suffered from a broken BIOS.
Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
Linux and BIOS should be restored to a working state.
---
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 Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY
Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
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 (not fixed by 4.14.9)
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM
HP 14-r012la
---
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 BIO
[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup
@Daniel I can't really follow those steps exactly, as the machine hangs as soon as either GDM or gnome-shell is started -- 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/1697450 Title: Gnome Shell hangs at startup Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I'm trying to install from the daily Artful desktop image (20170612). After boot, the gnome session hangs at startup, while the "zoom" animation is being shown. I have an intel card: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 I'm not sure how to debug this further, but I had similar issues with the installer from Zesty as well (see https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846) With Artful, at least it gets past the splash screen but then it hangs. Note that the system is currently running Yakkety with no issue. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-30 (71 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Tags: artful wayland-session Uname: Linux 4.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697450/+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 1738736] Re: ACPI error message flooding syslog
FYI, still got it with "4.13.0-21-generic". Sorry, but I still won't be able to test on the upstream kernel 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/1738736 Title: ACPI error message flooding syslog Status in linux package in Ubuntu: Incomplete Bug description: This message : Dec 18 09:20:13 tignasse kernel: [ 85.652805] ACPI Error: Needed type [Reference], found [Integer] 99eae08481f8 (20170531/exresop-103) Dec 18 09:20:13 tignasse kernel: [ 85.652831] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170531/dswexec-461) Dec 18 09:20:13 tignasse kernel: [ 85.652847] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20170531/psparse-550) Is flooding my syslog at a pace of on message every 200 ms ! This is really annoying. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 5166 F pulseaudio /dev/snd/controlC1: alex 5166 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 18 09:22:16 2017 HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583 InstallationDate: Installed on 2015-11-10 (768 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Skylake System dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738736/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
You can potentially use numactl to launch the process and set a policy of interleaving allocations between NUMA nodes to avoid these 1 sided allocations. Tends to happen with servers that make big allocations from a single thread during startup, as commonly seen on mysqld servers and the innodb_buffer_pool for example. numactl --interleave all /path/to/server/process --argument-1 #etc Reference: https://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: Confirmed Status in linux-raspi2 source package in Xenial: Fix Committed Bug description: After a fix for LP#1647400, a bug that caused freezes under some workloads, some users noticed regular OOMs. Those regular OOMs were reported under this bug, and fixed after some releases. Some of the affected kernels are documented below. In order to check your particular kernel, read its changelog and lookup for 1655842 and 1647400. If it has the fix for 1647400, but not the fix for 1655842, then it's affected. It's still possible that you notice regressions compared to kernels that didn't have the fixes for any of the bugs. However, reverting all fixes would cause the freeze bug to come back. So, it's not a possible solution moving forward. If you see any regressions, in the form of OOMs, mainly, please report a new bug. Different workloads may require different solutions, and it's possible that further fixes are needed, be them upstream or not. The best way to get such fixes applied is reporting that under a new bug, one that can be verified, so being able to reproduce the bug makes it possible to verify the fixes really fix the identified bug. Kernels affected: linux 4.4.0-58, 4.4.0-59, 4.4.0-60, 4.4.0-61, 4.4.0-62. linux-raspi2 4.4.0-1039 to 4.4.0-1042 and 4.4.0-1044 to 4.4.0-1071 Particular kernels NOT affected by THIS bug: linux-aws To reiterate, if you find an OOM with an affected kernel, please upgrade. If you find an OOM with a non-affected kernel, please report a new bug. We want to investigate it and fix it. === I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 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: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Adding some information obtained last night: On my YEPO 737A I flashed both Lubuntu and Elementary images to test if the suspend/wake "trick" would initialize the trackpad, and it did not. Both flashes making use of 4.15rc6. Attacking this problem via BIOS seems problematic, as so many brand names produce cheap apollo lake machines with similar SYNA trackpad hardware: Jumper, chuwei, yepo, etc. It really does feel like this is a delay issue as mentioned above, and jumper must have tightened this up of their own accord. I sincerely doubt the dozen or more other makers will do the same. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1740438] Re: Kernel has troule recognizing Corsair Harpoon RGB mouse
I'm not sure whether it may be relevant in this context, but there is unofficial driver support for your mouse: https://github.com/mattanger /ckb-nex. I don't know if the source is part of the Linux kernel; if that is the case, just ignore/delete my comment. -- 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/1740438 Title: Kernel has troule recognizing Corsair Harpoon RGB mouse Status in linux package in Ubuntu: Confirmed Bug description: I recently started using a Corsair Harpoon RGB mouse and the kernel is having trouble recognizing it. About half of the time when I boot, I see messages like this: [7.132078] usb 1-14: unable to read config index 0 descriptor/all [7.132081] usb 1-14: can't read configurations, error -110 Occasionally they repeat after a few seconds. The mouse will not function until I unplug the mouse and plug it back in. So far, one unplug and plug has fixed it every time. I am running Xubuntu 17.10 on 4.13.0-21.24-generic 4.13.13. I have attached the extra debug information that is generated by ubuntu-bug linux. I can provide additional information, if needed, and I am available to troubleshoot this issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ben 937 F pulseaudio /dev/snd/controlC0: ben 937 F pulseaudio /dev/snd/controlC1: ben 937 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 28 14:13:19 2017 InstallationDate: Installed on 2017-12-20 (8 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A59 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z270 SLI (MS-7A59) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd11/20/2017:svnMSI:pnMS-7A59:pvr1.0:rvnMSI:rnZ270SLI(MS-7A59):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A59 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740438/+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 1741061] [NEW] Bionic update to v4.14.11 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.14.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.14.11 stable release shall be applied: tracing: Remove extra zeroing out of the ring buffer page tracing: Fix possible double free on failure of allocating trace buffer tracing: Fix crash when it fails to alloc ring buffer x86/cpufeatures: Add X86_BUG_CPU_INSECURE x86/mm/pti: Disable global pages if PAGE_TABLE_ISOLATION=y x86/mm/pti: Prepare the x86/entry assembly code for entry/exit CR3 switching x86/mm/pti: Add infrastructure for page table isolation x86/pti: Add the pti= cmdline option and documentation x86/mm/pti: Add mapping helper functions x86/mm/pti: Allow NX poison to be set in p4d/pgd x86/mm/pti: Allocate a separate user PGD x86/mm/pti: Populate user PGD x86/mm/pti: Add functions to clone kernel PMDs x86/mm/pti: Force entry through trampoline when PTI active x86/mm/pti: Share cpu_entry_area with user space page tables x86/entry: Align entry text section to PMD boundary x86/mm/pti: Share entry text PMD x86/mm/pti: Map ESPFIX into user space x86/cpu_entry_area: Add debugstore entries to cpu_entry_area x86/events/intel/ds: Map debug buffers in cpu_entry_area x86/mm/64: Make a full PGD-entry size hole in the memory map x86/pti: Put the LDT in its own PGD if PTI is on x86/pti: Map the vsyscall page if needed x86/mm: Allow flushing for future ASID switches x86/mm: Abstract switching CR3 x86/mm: Use/Fix PCID to optimize user/kernel switches x86/mm: Optimize RESTORE_CR3 x86/mm: Use INVPCID for __native_flush_tlb_single() x86/mm: Clarify the whole ASID/kernel PCID/user PCID naming x86/dumpstack: Indicate in Oops whether PTI is configured and enabled x86/mm/pti: Add Kconfig x86/mm/dump_pagetables: Add page table directory to the debugfs VFS hierarchy x86/mm/dump_pagetables: Check user space page table for WX pages x86/mm/dump_pagetables: Allow dumping current pagetables x86/ldt: Make the LDT mapping RO ring-buffer: Mask out the info bits when returning buffer page length ring-buffer: Do no reuse reader page if still in use iw_cxgb4: Only validate the MSN for successful completions ASoC: codecs: msm8916-wcd: Fix supported formats ASoC: wm_adsp: Fix validation of firmware and coeff lengths ASoC: da7218: fix fix child-node lookup ASoC: fsl_ssi: AC'97 ops need regmap, clock and cleaning up on failure ASoC: twl4030: fix child-node lookup ASoC: tlv320aic31xx: Fix GPIO1 register definition gpio: fix "gpio-line-names" property retrieval IB/hfi: Only read capability registers if the capability exists IB/mlx5: Serialize access to the VMA list IB/uverbs: Fix command checking as part of ib_uverbs_ex_modify_qp() IB/core: Verify that QP is security enabled in create and destroy ALSA: hda: Drop useless WARN_ON() ALSA: hda - Add MIC_NO_PRESENCE fixup for 2 HP machines ALSA: hda - change the location for one mic on a Lenovo machine ALSA: hda - fix headset mic detection issue on a Dell machine ALSA: hda - Fix missing COEF init for ALC225/295/299 cpufreq: schedutil: Use idle_calls counter of the remote CPU block: fix blk_rq_append_bio block: don't let passthrough IO go into .make_request_fn() kbuild: add '-fno-stack-check' to kernel build options ipv4: igmp: guard against silly MTU values ipv6: mcast: better catch silly mtu values net: fec: unmap the xmit buffer that are not transferred by DMA net: igmp: Use correct source address on IGMPv3 reports netlink: Add netns check on taps net: qmi_wwan: add Sierra EM7565 1199:9091 net: reevalulate autoflowlabel setting after sysctl setting ptr_ring: add barriers RDS: Check cmsg_len before dereferencing CMSG_DATA tcp_bbr: record "full bw reached" decision in new full_bw_reached bit tcp md5sig: Use skb's saddr when replying to an incoming segment tg3: Fix rx hang on MTU change with 5717/5719 tcp_bbr: reset full pipe detection on loss recovery undo tcp_bbr: reset long-term bandwidth sampling on loss recovery undo s390/qeth: apply takeover changes when mode is toggled s390/qeth: don't apply takeover changes to RXIP s390/qeth: lock IP table while applying takeover changes s390/qeth: update takeover IPs after configuration change net: ipv4: fix for a race condition in raw_sendmsg net: mvmdio: disable/unprepare clocks in EPROBE_DEFER case sctp: Replace use of sockets_allocated with specified macro. adding missing rcu_read_unlock in ipxip6_rcv ip6_gre: fix device features for ioctl setup ipv4: Fix use-after-free when flushing FIB tables net: bridge: fix early call to br_stp_change_bridge_id and plug newl
[Kernel-packages] [Bug 1740438] Re: Kernel has troule recognizing Corsair Harpoon RGB mouse
There is a typo in my previous comment, the correct URL is: https://github.com/mattanger/ckb-next/. Sorry for this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740438 Title: Kernel has troule recognizing Corsair Harpoon RGB mouse Status in linux package in Ubuntu: Confirmed Bug description: I recently started using a Corsair Harpoon RGB mouse and the kernel is having trouble recognizing it. About half of the time when I boot, I see messages like this: [7.132078] usb 1-14: unable to read config index 0 descriptor/all [7.132081] usb 1-14: can't read configurations, error -110 Occasionally they repeat after a few seconds. The mouse will not function until I unplug the mouse and plug it back in. So far, one unplug and plug has fixed it every time. I am running Xubuntu 17.10 on 4.13.0-21.24-generic 4.13.13. I have attached the extra debug information that is generated by ubuntu-bug linux. I can provide additional information, if needed, and I am available to troubleshoot this issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ben 937 F pulseaudio /dev/snd/controlC0: ben 937 F pulseaudio /dev/snd/controlC1: ben 937 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 28 14:13:19 2017 InstallationDate: Installed on 2017-12-20 (8 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A59 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z270 SLI (MS-7A59) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd11/20/2017:svnMSI:pnMS-7A59:pvr1.0:rvnMSI:rnZ270SLI(MS-7A59):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A59 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740438/+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 44008] Re: Shutdown still doesn't turn off my computer
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/44008 Title: Shutdown still doesn't turn off my computer Status in linux package in Ubuntu: Invalid Bug description: Shutdown on my machine (HP Vectra VL 450 mhz Pentium III) still does not turn off the computer. The HD shutsdown but power is left applied to the computer. Dapper used to shut down everything until about 3 months ago. Breezy also worked properly. I am using the latest Kernel , and Dapper is up to date(May 10th). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/44008/+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 85894] Re: ThinkPad overheats
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/85894 Title: ThinkPad overheats Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.20 package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Invalid Bug description: Binary package hint: acpi Edgy on my ThinkPad Z60t doesn't manage its temperature very well. It is enough to leave the laptop alone just with inactive Firefox running and the temperature rises soon at dangerous 93°C (200°F). That causes the fan to speed up, however only to keep the temp at the same 93˚C. The average temperature is also higher than it should be, eg. when playing Wormux it rises above 72˚C. I tried to fix the problem by using fan speed script ( http://www.thinkwiki.org/wiki/ACPI_fan_control_script#Variable_speed_control_scripts ) from ThinkWiki but with no result, because ibm-acpi module ( http://www.thinkwiki.org/wiki/Ibm-acpi ) did not work correctly for me ($ sudo modprobe ibm_acpi experimental=1 returns something like "access denied") It also might be connected that the CPU frequency never drops bellow 800MHz. I hope the bug is caused by acpi as I fillwd it, please let me know what files I might provide. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/85894/+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 68824] Re: Ubuntu destroys filesystem on attached USB harddrive!
Closing that old report which not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/68824 Title: Ubuntu destroys filesystem on attached USB harddrive! Status in gnome-volume-manager: Invalid Status in linux package in Ubuntu: Invalid Bug description: I already reported this bug # 68744 But instead of only mounting it multiple times ubuntu edgy has also destroyed the FAT32 filesystem on it, so that all my data are lost. It started to mount the drive over and over again, then I shutdown ubuntu which resulted in "I/O buffer error on /dev/sdb1" and a hangup on shutdown, and then windows checked the filesystem and most of my files were gone. Other linux systems also show the "multiple mount" bug. Please set this to "critical", because destroying data just by plugging in an USB drive (I didn´t change any data on it) isn´t acceptable at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-volume-manager/+bug/68824/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Tags removed: kernel-key -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 116803] Re: ReiserFS filename hash collision causing DoS
The problem was reported against a now too old unsupported kernel; closing that report as no recent comment have been sent. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/116803 Title: ReiserFS filename hash collision causing DoS Status in linux package in Ubuntu: Invalid Bug description: Binary package hint: linux-image-2.6-k7 If you create files in a directory on reiserfs, it is possible to saturate the hash table such that new files with particular filenames cannot be created. This bug actually dates back to about 2004, but is still extant: http://marc.info/?l=reiserfs&m=110434667931228&w=2 (The above post contains a script that demonstrates the problem which works on my Feisty system.) This theoretically allows attackers to DoS temporary directories, etc, but does not appear to cause actual data loss. According to the originally post, this has also actually been seen in real life, although accidentally, not part of an attack. It surprises me slightly that this bug has been around for so long, given the potential seriousness... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/116803/+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 112088] Re: laptop with Nat. Semi. PC87591 Super IO becomes too hot and shuts down
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/112088 Title: laptop with Nat. Semi. PC87591 Super IO becomes too hot and shuts down Status in linux package in Ubuntu: Invalid Bug description: Whenever I watch a movie or try to compile something for more than few minutes, the cpu reaches 100C and the laptop shuts down. When idle, the cpu temperature is usually around 65C. My laptop is HP Pavilion dv4000. I am running Feisty. Also, $cat /proc/acpi/thermal_zone/THR0/polling_frequency tells me that polling is disabled. $cat trip_points says: critical (S5): 100 C passive: 95 C: tc1=2 tc2=5 tsp=300 devices=0xdf838e50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/112088/+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 112272] Re: /proc/mounts has lines with embedded spaces, update-manager doesn't understand them
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/112272 Title: /proc/mounts has lines with embedded spaces, update-manager doesn't understand them Status in linux package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Fix Released Bug description: Binary package hint: update-manager upgrade tool crash before getting downloading Traceback (most recent call last): File "/tmp/kde-root/adept_manager6vJwfa.tmp-extract/dist-upgrade.py", line 56, in ? app.run() File "/tmp/kde-root/adept_manager6vJwfa.tmp-extract/DistUpgradeControler.py", line 1025, in run self.fullUpgrade() File "/tmp/kde-root/adept_manager6vJwfa.tmp-extract/DistUpgradeControler.py", line 1000, in fullUpgrade if not self.askDistUpgrade(): File "/tmp/kde-root/adept_manager6vJwfa.tmp-extract/DistUpgradeControler.py", line 604, in askDistUpgrade if not self._checkFreeSpace(): File "/tmp/kde-root/adept_manager6vJwfa.tmp-extract/DistUpgradeControler.py", line 551, in _checkFreeSpace (what, where, fs, options, a, b) = line.split() ValueError: too many values to unpack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/112272/+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 107232] Re: Very low volume with HDA/ALC883
closing that old report, as it has not got recent comment. ** Changed in: alsa-driver Importance: Unknown => Undecided ** Changed in: alsa-driver Remote watch: ALSA Bug Tracker (discontinued) #3932 => None ** Changed in: alsa-driver Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/107232 Title: Very low volume with HDA/ALC883 Status in ALSA driver: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.20 package in Ubuntu: Won't Fix Bug description: I have an Intel ICH8 + Realtek ALC883 onboard chip on my motherboard. Everything works fine but the volume is very low even when all the controls are at 100%. I found this line in dmesg: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... This bug is probably related to bug #77024 (nVidia based mb) and bug #64356 (ICH3 chipset). This happens with Feisty beta (16 April 2007) and alsa-driver 1.0.13. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3133 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 43' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1462f603,0012' Controls : 47 Simple ctrls : 22 CasperVersion: 1.311 DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120319) MachineType: To Be Filled By O.E.M. MS-7276 Package: linux-image-3.2.0-19-generic-pae 3.2.0-19.30 PackageArchitecture: i386 ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 RelatedPackageVersions: linux-restricted-modules-3.2.0-19-generic-pae N/A linux-backports-modules-3.2.0-19-generic-pae N/A linux-firmware1.71 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise Uname: Linux 3.2.0-19-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/08/06 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V7.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7276 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV7.1:bd12/08/06:svnToBeFilledByO.E.M.:pnMS-7276:pvr1.0:rvnMSI:rnMS-7276:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7276 dmi.product.version: 1.0 dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/107232/+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 117083] Re: HP Pavilion ze54xx/ze44xx onetouch-keys appears "dead"
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/117083 Title: HP Pavilion ze54xx/ze44xx onetouch-keys appears "dead" Status in linux package in Ubuntu: Invalid Bug description: Binary package hint: hotkey-setup Onetouch-keys for TV, Lock, ? and Mute appeared dead on my system when i installed Feisty Final. Volume, Email and Web worked perfectly. With dead i mean that they did not reveal their keycode to any of the methods on https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch I beleive this is a common problem for HP ze5/4xx and some compaq presario-types. When i use "./omke.pl -k 1" from this bug: https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/20223 1. Mute-button (right side) works. 2. TV, Lock and ?-keys start sending their keycodes to syslog ( e070, e071, e073), but ONLY TO SYSLOG(gnome-system-log), not to showkey. I can then use setkeycodes and use them in gnome-keybinding-properties. #My temporary solution, in /etc/init.d/bootmisc.sh add: /path/to/omke.pl -k 1 setkeycodes e070 129 setkeycodes e071 130 setkeycodes e073 131 #Then add in gnome-keybinding-properties # Might work for other, find keycode in gnome-system-log afer omke.pl Computerinfo: bios-version:KF_KH.F.24 system-manufacturer:Hewlett-Packard system-product-name:Pavilion ze5400 (DM947A) system-version:KH.F.24 Sold to me in Norway, 2003 as HP Pavilion ZE5413EA Other bugrefereses: http://lists.debian.org/debian-laptop/2002/02/msg00299.html https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/25099 https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/20223 http://www.cybersym.com/pages/linux-ze4100.html (One-Touch Multimedia Keys) I'm going to add a page to https://wiki.ubuntu.com/LaptopTesting in a couple of days, including a detailed explanation of this solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/117083/+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 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1711104
Title:
[P9][Ubuntu 16.04.03] Additional PMU fixes for P9
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
== Comment: #0 - Shriya R. Kulkarni - 2017-08-16
04:07:45 ==
Please integrate the following PMU fixes for P9.
93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in
Power9 event list')
91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9
event list')
70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from
power8')
7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on
Power9')
3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and
PM_RUN_INST_CMPL events')
20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on
Power9')
24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711104/+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 145125] Re: LiveView FlyDVB Trio CardBus
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: kaffeine Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/145125 Title: LiveView FlyDVB Trio CardBus Status in Kaffeine: Invalid Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.20 package in Ubuntu: Won't Fix Bug description: Currently there seems to be no support for the LiveView FlyDVB Trio CardBus (DVB-S, DVB-T, analogue, video) card. The "big" desktop pc variant has been reported to be supported, but there is no information about this notebook card variant. This plug-in card is able to receive DVB-S, DVB-T *and* to capture analogue tv signals (conventional terrestric TV, VHS etc.). Note that support for this multi-functional tv card might imho greatly enhance the respectability of Ubuntu when it comes to multimedia and consumer entertainment. To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/145125/+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 119730] Re: Slow SATA performance
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/119730 Title: Slow SATA performance Status in linux package in Ubuntu: Invalid Bug description: Hi This issue has been discussed over at http://ubuntuforums.org/showthread.php?t=447474, and seems to affect a number of us. File copy speed is very slow (roughly 5-10MBps) on SATA hard drives. Copying within the same physical drive is just as slow as copying to another physical drive. The issue occurs with GUI tools (Nautilus, Krusader) as well as at the terminal using the CP command. This has occured since upgrading to Feisty; Edgy was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/119730/+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 139080] Re: Network Manager rejects WEP keys for IPW 3945
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/139080 Title: Network Manager rejects WEP keys for IPW 3945 Status in linux package in Ubuntu: Invalid Status in linux-ubuntu-modules-2.6.22 package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in linux source package in Feisty: Won't Fix Status in linux-ubuntu-modules-2.6.22 source package in Feisty: Won't Fix Status in network-manager source package in Feisty: Invalid Status in linux source package in Gutsy: Won't Fix Status in linux-ubuntu-modules-2.6.22 source package in Gutsy: Won't Fix Status in network-manager source package in Gutsy: Fix Released Bug description: Binary package hint: network-manager Hello. I am using Ubuntu 7.04 with the said wireless card. I can see the network. When i try to connect it asks for my WEP, which is entered correctly. It then does not connect to the network. Any fix for this would be greatly appreciated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/139080/+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 144166] Re: LCD display 1360x768 not configured after intallation
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/144166 Title: LCD display 1360x768 not configured after intallation Status in linux package in Ubuntu: Invalid Status in linux-ubuntu-modules-2.6.22 package in Ubuntu: Fix Released Bug description: This is kind of simple, but it took me some time to make it work. I am using: 1.- ATI RdeonVideo card: 01:00.0 VGA compatible controller: ATI Technologies Inc RV530LE [Radeon X1600/X1650 PRO] 01:00.1 Display controller: ATI Technologies Inc RV530LE [Radeon X1650 PRO] (Secondary) Connected to the tv by the HDMI/DVI port+cable 2.- Display: Samsung LN32R71B LCD TV as the ONLY display, which is suppose to operate at 1360x768@60Hz maximum. During the installation process, the default screen runs at 1024x640, but after booting for the first time it when to 1920x1080i@60Hz, YES, believed or not that was a problem because the menus (top and bottom) weren't visible. I had to modify the xorg.conf fiel and add the 1360x768 and 60 in the listed options: Section monitor modeline "1360x768@60" 60.0 1024 1048 1184 1360 768 768 768 768 -vsync -hsync Section screen Modes "640x480@60""800x600@56""800x600@60" "1024x768@60" "1360x768@60" It is finally working, but it woulb be great if you include this modes under the generic version when chosing in screen and graphics (by the way the title of the windows is still in English (I am running the Spanish version) Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/144166/+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 147203] Re: 1385:4251 Netgear WG111T not auto-sensed
unsupported project since a while ** Changed in: madwifi Importance: Unknown => Undecided ** Changed in: madwifi Remote watch: madwifi-project.org/ #2114 => None ** Changed in: madwifi Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/147203 Title: 1385:4251 Netgear WG111T not auto-sensed Status in MadWifi: Invalid Status in linux package in Ubuntu: Invalid Bug description: My WG111T works fine on 7.04, recognized right after installation. However, under 7.10, it doesn't work directly, and seems not to be recognized as a WiFi USB Key To manage notifications about this bug go to: https://bugs.launchpad.net/madwifi/+bug/147203/+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 147203] Re: 1385:4251 Netgear WG111T not auto-sensed
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/147203 Title: 1385:4251 Netgear WG111T not auto-sensed Status in MadWifi: Invalid Status in linux package in Ubuntu: Invalid Bug description: My WG111T works fine on 7.04, recognized right after installation. However, under 7.10, it doesn't work directly, and seems not to be recognized as a WiFi USB Key To manage notifications about this bug go to: https://bugs.launchpad.net/madwifi/+bug/147203/+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 147250] Re: Alternate install CD (both x86, AMD64) not booting on HP NX6325
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/147250 Title: Alternate install CD (both x86, AMD64) not booting on HP NX6325 Status in linux package in Ubuntu: Invalid Status in Debian: Fix Released Bug description: The x86 as well as the AMD64 alternate installation CD stops booting immediately after the kernel is being loaded (when switching the screen). So if I remove "quiet" from the kernel parameters, I see all the kernel messages, but immediately after that the screen goes black. The system only responds to Ctrl-Alt-Del works, terminal windows are not active. I tried several "typical" laptop kernel parameters but that did not help. The problem exists for the Beta CD set as well the following daily builds. I had no problem with the daily builds before September 24, 2007. Installed systems seem also still to work, also the LiveCD does boot (well at least until Gnome gets started, but this is another bug). I guess it might be related to a problem with the initrd and/or the framebuffer. Media are ok as I tested them on a different system without this problem. Funny thing is: When I ask for the CD being tested, that seems to work, there is some HD/CD-activity. However, the screen also remains black. Overview on the HP NX6325 specs: https://wiki.ubuntu.com/LaptopTestingTeam/HPNX6325?highlight=%28hpnx6325%29 Details of lshw: http://vale.homelinux.net/wordpress/wp-content/uploads/2007/02/myhpnx6325.html -- Description modified by Hans Deragon, to reflect current status. Currently this occurs also with the HP 6510b and HP 2510p using Hardy Heron 08.04 Alpha 6 Alternate install CD. Both of these systems have an Intel GM965/GL960 Integrated Graphic Controller. There is a workaround. On the main menu, press "F6 Other Options", replace "quiet --" with "fb=false" and try it. The bug seams to be with the framebuffer, thus disabling it get the installer displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/147250/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read-only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. - Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux - and BIOS should be restored to a working state. + 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. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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!! ** Description changed: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read-only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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 + $ 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'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything w
[Kernel-packages] [Bug 156639] Re: During Boot Get nk.c:unexpected responsefd/build/buildd/linux-source-2.6.22-2.6.22/driver/input/misc/yeali Keeps repeating this with no end to the repeat. Requires r
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/156639 Title: During Boot Get nk.c:unexpected responsefd/build/buildd/linux- source-2.6.22-2.6.22/driver/input/misc/yeali Keeps repeating this with no end to the repeat. Requires reboot. Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Bug description: ubuntu 7.1 During Boot Get nk.c:unexpected responsefd/build/buildd/linux-source-2.6.22-2.6.22/driver/input/misc/yeali Keeps repeating this with no end to the repeat. Requires reboot. Tried to recover boot and get this every time. The first time I saw this was while switching users. Now sometimes get it during bootup, but always during recover boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/156639/+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 150515] Re: et131x causing ksoftirqd to eat up cpu
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/150515 Title: et131x causing ksoftirqd to eat up cpu Status in linux package in Ubuntu: Invalid Status in linux-ubuntu-modules-2.6.22 package in Ubuntu: Won't Fix Status in linux-ubuntu-modules-2.6.24 package in Ubuntu: Fix Released Bug description: I have a LG T1 Express Dual laptop with an Agere et131x ethernet adapter. In Feisty, the driver (compiled from their SF.net project page, version 1.2.3) worked fine without any major problems. Now, in Gutsy, after upgrading to linux-ubuntu-modules version 2.6.22-13.33, the driver is included in the Ubuntu distribution. When the et131x module is loaded, I experience the process ksoftirqd to be busy quite often, producing heat and draining my battery faster. The solution is to unload the module if I don't need wired ethernet, but of course it would be cool to have ethernet and not haing 25-20% of your cpu eaten up by the kernel. The exact same problem exists with a self-compiled kernel module with the patch found at http://sourceforge.net/tracker/index.php?func=detail&aid=1709009&group_id=179406&atid=889025 . Unfortunately, I don't know how to debug this problem or narrow it down. I suspect the driver not being compatible with the new kernel's tickless interface, but obviously I'm not sure about this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/150515/+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 154271] Re: xenU sending too big packets
closing that old report, as it has not got recent comment.
** Changed in: xen-3.3 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xen-3.2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xen-3.1 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/154271
Title:
xenU sending too big packets
Status in linux package in Ubuntu:
Invalid
Status in xen-3.1 package in Ubuntu:
Invalid
Status in xen-3.2 package in Ubuntu:
Invalid
Status in xen-3.3 package in Ubuntu:
Invalid
Bug description:
etup: amd64, xen0 = ubuntu 7.10 ("gutsy"), xenU = ubuntu 7.10 ("gutsy"),
network config with xenU routing via xen0.
scp xenU:file . very slow, ~50KB/s
scp xen0:file . several MB/s
on xen0:
scp xenU:file . many MB/s
had a look at tcpdump, I see lines like this:
10:55:30.319389 IP (tos 0x8, ttl 64, id 59286, offset 0, flags [DF], proto TCP
(6), length 2948) xenU.22 > desktop: . 47785:50681(2896) ack 0 win 404
10:55:30.319399 IP (tos 0xc8, ttl 64, id 52994, offset 0, flags [none], proto
ICMP (1), length 576) xen0 > xenU: ICMP desktop unreachable - need to frag
(mtu 1500), length 556 IP (tos 0x8, ttl 64, id 59286, offset 0, flags [DF],
proto TCP (6), length 2948) xenU.22 > desktop.41056: . 47785:50681(2896) ack
0 win 404 [|icmp]
so the xenU is sending packets with size 2948? why?
ifconfig on xenU:
eth0 Link encap:Ethernet HWaddr 00:16:3E:6D:03:2D
inet addr:xenU Bcast:... Mask:255.255.255.255
inet6 addr: fe80::216:3eff:fe6d:32d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34918213 errors:0 dropped:0 overruns:0 frame:0
TX packets:34262839 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12337072144 (11.4 GB) TX bytes:48486812526 (45.1 GB)
so the MTU is 1500 which is fine. xenU sending too big packets.
== WORK AROUND ==
It seems that turning off TX checksum offloading within the domU
eliminates the issue:
ethtool -K ethN tx off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/154271/+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 149622] Re: Only PCM volume control takes effect
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Assignee: teresa (teresadd1-0) => (unassigned) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: alsa-driver Importance: Unknown => Undecided ** Changed in: alsa-driver Status: In Progress => New ** Changed in: alsa-driver Remote watch: ALSA Bug Tracker (discontinued) #3460 => None ** Changed in: alsa-driver Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/149622 Title: Only PCM volume control takes effect Status in ALSA driver: Invalid Status in linux package in Ubuntu: Invalid Bug description: I'm using Gutsy Beta, with fully updated packages as of 5 Oct 2007. The PCM volume control appears to be the only one that has effect. This means that I can only have REALLY loud, and REALLY soft, leaving me no room for comfort. I have tested this using the GNOME volume control applet and the Sound (System>>Preferences item) panel, using the test sound and adjusting the Master and PCM controls. This appears to be a problem in any ALSA greater than 1.0.14rc2. I'll note that this problem also occurred with ALSA compiled on Feisty, with the Gutsy kernel on Feisty, in Gutsy itself, and in the latest ALSA compiled on good ol' Gutsy. I have an HDA-Intel sound card. To be specific, I have a Compaq Presario V5204NR, with an onboard Conexant HD sound card. To further this, partial output of my lspci is "00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)". I'll post more info as soon as I figure out how to upload text files. EDIT: This appears to be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/120515 . However, it is listed as fixed while, or me at least, it clearly isn't To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/149622/+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 1738761] Re: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA
Question expired. Can we reopen the bug as an enhancement request? -- 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/1738761 Title: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA Status in linux package in Ubuntu: Invalid Bug description: In order to resolve some bugs, to workaround some hardware quirk, or to help developers test some bug-fixing patch it would be able to: - Get the sources of the *current* (non mainline) ubuntu kernel - Apply some patch - Rebuild the kernel in a PPA (so that it can be made available to multiple people for testing). Unfortunately, there is no documentation on how to do this. In fact, to the best of my understanding there is no documentation on how to build patched kernels in PPAs at all. This seems to be both possible and involving some special recipes, because in some occasions I've been pointed by ubuntu developers to try some specially patched version of the current kernel made available via a PPA. Specifically, at the present time, I would like to try and help trying the patch in git://github.com/vsyrjala/linux.git plane_assert_v4.13 which is not yet available in mainline. In other occasions I had similar situations with other patches. Please let me remark again that I am not looking for ways of building patched versions of the mainline kernel in a PPA (for this I have found some informal instructions in https://askubuntu.com/questions/784796/ppa-upload-of-custom-kernel- package/841981#841981 (incidentally, this too should in my opinion be officially documented). I am looking for ways to build a patched current kernel, so that: - systems needing proprietary drivers can be supported - patches can be tested with the current ubuntu kernel - as new versions of the ubuntu kernel for some distro come out, it is easy to bring forward the patch if needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-source (not installed) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 20848 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 18 11:42:45 2017 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Precision WorkStation T5400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-25 (53 days ago) WpaSupplicantLog: dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738761/+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 162347] Re: no sound on rev3 MacBook (Santa Rosa)
closing that old report, as it has not got recent comment. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: mactel-support Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/162347 Title: no sound on rev3 MacBook (Santa Rosa) Status in Mactel Support: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Bug description: amd64 alternate 7.10 install on a rev3 MacBook (2.2 ghz). Sound preference module runs tests, but no sound comes through speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/162347/+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 269081] Re: nat routes internal ip's over extrenal networks lan ips over wan networks
closing that old report, as it has not got recent comment. ** Changed in: ppp (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/269081 Title: nat routes internal ip's over extrenal networks lan ips over wan networks Status in linux package in Ubuntu: Invalid Status in ppp package in Ubuntu: Invalid Bug description: Hardy tcpdump -i ppp0 01:05:50.337659 IP 10.10.0.10.60726 > unknown.nscnap.net.www: F 0:0(0) ack 1 win 65535 6 pages of information and trouble shooting at - http://tennessee.ubuntuforums.com/showthread.php?s=8a1250eda87f9cede861165a9b79204a&t=906126 I confirmed the problem with my original belief. Anyone dealing with verizon it took me over 2 hours of heated supervisor to supervisor hopping until i finally got a guy willing to help provide me with the information i needed. Which he in turn had their tech team monitor my connection for a a day after the ticket had to be escalated several times (over a two week process) In the end this is the confirmed problem. Because i have had this issue on several different ubuntu machines, i am certain it is an issue in ubuntu iptables or routing. The bottom line is right now windows is a more stable platform for ics, which makes me sick... The problem is its routing my lan ip's over the wan (or randomly bridging the connection rather then routing it) my terminology might be off, verizon explained it to me "it is leaking internal ip address's to our network which is why we are disconnecting you" this is exactly what i guessed was going on as my tcpdump logs show (example) tcpdump -i ppp0 -v 10.10.0.x > google.com I have tried setting up my ics through the tutorial, through guide + guard dog , and through firestarter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269081/+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 1734744] Re: OOM killer with kernel 4.4.0-92
Unfortunately the out of memory errors persisted with 4.4.0-104, so 6 days ago we switched to 4.8.0-58. No more OOM errors so far, but it seems the performance was affected a bit, there seem to be some freezes during the nightly jobs. Seeing that the similar bug, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 was introduced while fixing "LP#1647400, a bug that caused freezes under some workloads", it seems plausible that, since the two issues are related, fixing one breaks the other and the other way around. In any case, I can live with freezes on this particular machine, instead of OOM errors, so for the time being I'll stay on 4.8.0-58. I may experiment again with newer 4.4.0 kernels at the end of the month. -- 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/1734744 Title: OOM killer with kernel 4.4.0-92 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When putting pressure on a Linux Node in Azure we see OOM killers (similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this is a different kernel) Reverting the kernel to 4.4.0-57 fixes the problem. dmesg and kernel.log attached --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 11 15:21 seq crw-rw 1 root audio 116, 33 Dec 11 15:21 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic root=UUID=512611f4-b05a-4d8a-b743-438b71c5385d ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-92-generic N/A linux-backports-modules-4.4.0-92-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: D88904A9-DF88-454F-9F50-7A8DE8964445 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734744/+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 159404] Re: Intel ICH5 audio: master volume control ignored
closing that old report, as it has not got recent comment.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/159404
Title:
Intel ICH5 audio: master volume control ignored
Status in linux package in Ubuntu:
Invalid
Bug description:
Applying "mute" or raising/lowering the master volume does nothing:
the sound stays at the same level, "mute" does not mute.
This is on a desktop PC for office use (hp Compaq D530) with integrated audio
and mono output (no headphones required to listen sound).
http://h2.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?&lang=en&cc=us&contentType=SupportManual&docIndexId=179166&prodTypeId=12454&prodSeriesId=316713&lang=en&cc=us#2
Controlling sound level/mute is working on Master mono or on headphones as
expected. The common usage on an office PC is to use the internal audio
("Master mono") but this is by default hidden in the Gnome sound mixer, so the
user is lost.
$ LANG=C aplay --list-devices
List of PLAYBACK Hardware Devices
card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 4: Intel ICH - IEC958 [Intel ICH5 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ lspci -nv
00:00.0 0600: 8086:2570 (rev 02)
Subsystem: 103c:12bc
Flags: bus master, fast devsel, latency 0
Memory at f800 (32-bit, prefetchable) [size=64M]
Capabilities:
00:02.0 0300: 8086:2572 (rev 02) (prog-if 00 [VGA])
Subsystem: 103c:12bc
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f000 (32-bit, prefetchable) [size=128M]
Memory at fc40 (32-bit, non-prefetchable) [size=512K]
I/O ports at 14e0 [size=8]
Capabilities:
00:1d.0 0c03: 8086:24d2 (rev 02) (prog-if 00 [UHCI])
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 1440 [size=32]
00:1d.1 0c03: 8086:24d4 (rev 02) (prog-if 00 [UHCI])
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 1460 [size=32]
00:1d.2 0c03: 8086:24d7 (rev 02) (prog-if 00 [UHCI])
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1480 [size=32]
00:1d.7 0c03: 8086:24dd (rev 02) (prog-if 20 [EHCI])
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at fc48 (32-bit, non-prefetchable) [size=1K]
Capabilities:
00:1e.0 0604: 8086:244e (rev c2) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=64
Memory behind bridge: fc50-fc7f
00:1f.0 0601: 8086:24d0 (rev 02)
Flags: bus master, medium devsel, latency 0
00:1f.1 0101: 8086:24db (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 14c0 [size=16]
Memory at 3000 (32-bit, non-prefetchable) [size=1K]
00:1f.2 0101: 8086:24d1 (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: 103c:12bc
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
I/O ports at 14f8 [size=8]
I/O ports at 1810 [size=4]
I/O ports at 1800 [size=8]
I/O ports at 1814 [size=4]
I/O ports at 14d0 [size=16]
00:1f.3 0c05: 8086:24d3 (rev 02)
Subsystem: 103c:12bc
Flags: medium devsel, IRQ 11
I/O ports at fc00 [size=32]
00:1f.5 0401: 8086:24d5 (rev 02)
Subsystem: 103c:12bc
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at 1000 [size=256]
I/O ports at 1400 [size=64]
Memory at fc480400 (32-bit, non-prefetchable) [size=512]
Memory at fc480600 (32-bit, non-prefetchable) [size=256]
Capabilities:
05:02.0 0200: 14e4:1696 (rev 03)
Subsystem: 103c:12bc
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
Memory at fc50 (64-bit, non-prefetchable) [size=64K]
Capabilities:
05:09.0 0200: 168c:001a (rev 01)
Subsystem: 1113:4211
Flags: bus master, medium devsel, latency 168, IRQ 18
Memory at fc51 (32-bit, non-prefetchable) [size=64K]
Capabilities:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159404/+subscriptions
--
Mail
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
The description of this bug has been updated for how to repair affected BIOS. If you are still suffering from this issue and the Ubuntu system on your laptop is functional, please give it a try. Including the solution into v4.13 kernel is being investigated. However, if you can no longer boot to Ubuntu for some reasons, besides posting your questions here, https://askubuntu.com/ or https://ubuntuforums.org/ are two other excellent support channels that you can ask for help and advice from the wider community. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests
ping - still broken as of today in Bionic when updating openvswitch. Asking for a bump of the force-badtest for now ... -- 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/1712831 Title: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hi, this seems to me to be a kernel crash of some sorts. Somewhat in the spirit of older bugs: - bug 1630940 - bug 1630578 Xnox asked me to look into a hang on openvswitch dep8 tests. What I found initially was in the log just "ERROR: Removing temporary files on testbed timed out" That message brought me to the two bugs above. But in there I read that this was the infra running dep8 crashing. So for a better bug report I tried to reproduce locally and that actually seems to work very reliable. To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing But with that running you can attach to the console and monitor of that guest. For example: $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0 That gave me a crash on the hang which kind of matches the older bugs, here the console: [ 54.256253] BUG: unable to handle kernel NULL pointer dereference at (null) [ 54.257156] IP: add_grec+0x28/0x440 [ 54.257553] *pdpt = 1a869001 *pde = [ 54.257555] [ 54.258338] Oops: [#1] SMP [ 54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net floppy pata_acpi [ 54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.12.0-11-generic #12-Ubuntu [ 54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 54.263610] task: c7b622c0 task.stack: c7b5a000 [ 54.264039] EIP: add_grec+0x28/0x440 [ 54.264378] EFLAGS: 00010202 CPU: 0 [ 54.264711] EAX: EBX: dd062540 ECX: 0006 EDX: dd062540 [ 54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0 [ 54.265793] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.266297] CR0: 80050033 CR2: CR3: 1e930d80 CR4: 06f0 [ 54.266885] Call Trace: [ 54.267120] [ 54.267349] mld_ifc_timer_expire+0xfe/0x250 [ 54.267754] ? mld_dad_timer_expire+0x50/0x50 [ 54.268173] call_timer_fn+0x30/0x120 [ 54.268524] ? mld_dad_timer_expire+0x50/0x50 [ 54.268942] ? mld_dad_timer_expire+0x50/0x50 [ 54.269364] run_timer_softirq+0x3c5/0x420 [ 54.269760] ? __softirqentry_text_start+0x8/0x8 [ 54.270198] __do_softirq+0xa9/0x245 [ 54.270539] ? __softirqentry_text_start+0x8/0x8 [ 54.270976] do_softirq_own_stack+0x24/0x30 [ 54.271373] [ 54.271611] irq_exit+0xad/0xb0 [ 54.271913] smp_apic_timer_interrupt+0x38/0x50 [ 54.272344] apic_timer_interrupt+0x39/0x40 [ 54.272745] EIP: native_safe_halt+0x5/0x10 [ 54.273139] EFLAGS: 0246 CPU: 0 [ 54.273624] EAX: EBX: ECX: 0001 EDX: [ 54.274000] ESI: EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10 [ 54.274361] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.274687] default_idle+0x1c/0xf0 [ 54.274896] arch_cpu_idle+0xe/0x10 [ 54.275286] default_idle_call+0x1e/0x30 [ 54.275787] do_idle+0x145/0x1c0 [ 54.276092] cpu_startup_entry+0x65/0x70 [ 54.276441] rest_init+0x62/0x70 [ 54.276718] start_kernel+0x3be/0x3d7 [ 54.276974] i386_start_kernel+0x9d/0xa1 [ 54.277260] startup_32_smp+0x16b/0x16d [ 54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b [ 54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0 [ 54.279829] CR2: [ 54.280143] ---[ end trace 3164b1c0dd7745bc ]--- [ 54.280550] Kernel panic - not syncing: Fatal exception in interrupt [ 54.281078] Kernel Offset: 0x600 from 0xc100 (relocation range: 0xc000-0xdfbfdfff) [ 54.281797] ---[ end Kernel panic - not syncing: Fatal exception in interrupt But since this is lovely qemu the machine isn't as dead as real HW now, so via the monitor $ sudo nc -U
[Kernel-packages] [Bug 1741080] [NEW] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped
Public bug reported: Hello, dmesg: [ 141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 142.828101] usbcore: registered new interface driver usbserial [ 142.828159] usbcore: registered new interface driver usbserial_generic [ 142.828207] usbserial: USB Serial support registered for generic [ 142.840302] usbcore: registered new interface driver option [ 142.840350] usbserial: USB Serial support registered for GSM modem (1-port) [ 146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.14.0-13-generic 4.14.0-13.15 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1740 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 13:13:02 2018 InstallationDate: Installed on 2017-10-13 (82 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.14.0-13-generic N/A linux-backports-modules-4.14.0-13-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- 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/1741080 Title: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [ 141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 142.828101] usbcore: registered new interface driver usbserial [ 142.828159] usbcore: registered new interface driver usbserial_generic [ 142.828207] usbserial: USB Serial support registered for generic [ 142.840302] usbcore: registered new interface driver option [ 142.840350] usbserial: USB Serial support registered for GSM modem (1-port) [ 146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.14.0-13-generic 4.14.0-13.15 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1740 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 13:13:02 2018 InstallationDate: Installed on 2017-10-13 (82 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.14.0-13-generic N/A linux-backports-modules-4.14.0-13-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSA
[Kernel-packages] [Bug 1740290] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped
*** This bug is a duplicate of bug 1741080 *** https://bugs.launchpad.net/bugs/1741080 ** This bug has been marked a duplicate of bug 1741080 cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped -- 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/1740290 Title: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, dmesg: [ 5519.779175] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.779186] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.779193] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.785793] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.785803] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.819250] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 1655 F...m pulseaudio /dev/snd/controlC0: caravena 1655 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 15:30:53 2017 InstallationDate: Installed on 2017-10-13 (75 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1740290/+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] [NEW] zfs-import-cache.service fails on startup
Public bug reported: 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. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 + ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service - ^^ per upstream minus modprobe plus Requires=zfs-load-module.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, zfs-import-scan.service doesn't seem to have run at all. If run manually, it works. 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? ** Description changed: 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, zfs-import-scan.service doesn't seem to have run at all. - If run manually, it works. 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? + 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? ** Description changed: I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. B
[Kernel-packages] [Bug 1741080] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741080 Title: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 142.828101] usbcore: registered new interface driver usbserial [ 142.828159] usbcore: registered new interface driver usbserial_generic [ 142.828207] usbserial: USB Serial support registered for generic [ 142.840302] usbcore: registered new interface driver option [ 142.840350] usbserial: USB Serial support registered for GSM modem (1-port) [ 146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.14.0-13-generic 4.14.0-13.15 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1740 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 13:13:02 2018 InstallationDate: Installed on 2017-10-13 (82 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.14.0-13-generic N/A linux-backports-modules-4.14.0-13-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741080/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read-only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G - Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) + 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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!! -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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
[Kernel-packages] [Bug 1741084] [NEW] rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229]
Public bug reported: A friend's card reader in his ThinkPad L430 [10ec:5229] was not automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had to manually load the rtsx_pci module. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "lspci-vnvn.txt" https://bugs.launchpad.net/bugs/1741084/+attachment/5030580/+files/lspci-vnvn.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741084 Title: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Status in linux package in Ubuntu: Confirmed Bug description: A friend's card reader in his ThinkPad L430 [10ec:5229] was not automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had to manually load the rtsx_pci module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741084/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@theyield, It could be that 4.14.3 (and later 4.14.X versions) work better than 4.15.X I found this true in my case. See this post on the TT forum: https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-the-ezbook-3-pro-v4/page/3/#post-76098 -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hi there, so it feels I am a special case of this. I am running Linux Mint 18.3 as my main distro. However to check a problem with standby based on Ubuntu I tried to run Ubuntu 17.10 from USB. Since then I have the same trouble to save my BIOS, etc. However Linux Mint is starting from hard disk without problems. I read the possible repair solution and before trying to do anything, I wanted to check, if it is likely that this kernel will work with Linux Mint 18.3, which is based on Ubuntu 16.04? Highest available Kernel by package manager is 4.13.0-21 right now. Regards Chris -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741084] Re: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741084 Title: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Status in linux package in Ubuntu: Confirmed Bug description: A friend's card reader in his ThinkPad L430 [10ec:5229] was not automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had to manually load the rtsx_pci module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741084/+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 1741084] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1741084 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. -- 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/1741084 Title: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] Status in linux package in Ubuntu: Confirmed Bug description: A friend's card reader in his ThinkPad L430 [10ec:5229] was not automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had to manually load the rtsx_pci module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741084/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in openvswitch source package in Bionic: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in openvswitch source package in Bionic: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
>From the Dup - FYI To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing Really easy to reproduce (and close to 100% fail rate) -- 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/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in openvswitch source package in Bionic: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@Brad - As much as I dislike using "old" kernels, this is definitely worth testing. I'll try as you've suggested tonight and report back ASAP. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests
*** This bug is a duplicate of bug 1736390 *** https://bugs.launchpad.net/bugs/1736390 ** This bug has been marked a duplicate of bug 1736390 openvswitch: kernel opps destroying interfaces on i386 -- 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/1712831 Title: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hi, this seems to me to be a kernel crash of some sorts. Somewhat in the spirit of older bugs: - bug 1630940 - bug 1630578 Xnox asked me to look into a hang on openvswitch dep8 tests. What I found initially was in the log just "ERROR: Removing temporary files on testbed timed out" That message brought me to the two bugs above. But in there I read that this was the infra running dep8 crashing. So for a better bug report I tried to reproduce locally and that actually seems to work very reliable. To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing But with that running you can attach to the console and monitor of that guest. For example: $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0 That gave me a crash on the hang which kind of matches the older bugs, here the console: [ 54.256253] BUG: unable to handle kernel NULL pointer dereference at (null) [ 54.257156] IP: add_grec+0x28/0x440 [ 54.257553] *pdpt = 1a869001 *pde = [ 54.257555] [ 54.258338] Oops: [#1] SMP [ 54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net floppy pata_acpi [ 54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.12.0-11-generic #12-Ubuntu [ 54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 54.263610] task: c7b622c0 task.stack: c7b5a000 [ 54.264039] EIP: add_grec+0x28/0x440 [ 54.264378] EFLAGS: 00010202 CPU: 0 [ 54.264711] EAX: EBX: dd062540 ECX: 0006 EDX: dd062540 [ 54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0 [ 54.265793] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.266297] CR0: 80050033 CR2: CR3: 1e930d80 CR4: 06f0 [ 54.266885] Call Trace: [ 54.267120] [ 54.267349] mld_ifc_timer_expire+0xfe/0x250 [ 54.267754] ? mld_dad_timer_expire+0x50/0x50 [ 54.268173] call_timer_fn+0x30/0x120 [ 54.268524] ? mld_dad_timer_expire+0x50/0x50 [ 54.268942] ? mld_dad_timer_expire+0x50/0x50 [ 54.269364] run_timer_softirq+0x3c5/0x420 [ 54.269760] ? __softirqentry_text_start+0x8/0x8 [ 54.270198] __do_softirq+0xa9/0x245 [ 54.270539] ? __softirqentry_text_start+0x8/0x8 [ 54.270976] do_softirq_own_stack+0x24/0x30 [ 54.271373] [ 54.271611] irq_exit+0xad/0xb0 [ 54.271913] smp_apic_timer_interrupt+0x38/0x50 [ 54.272344] apic_timer_interrupt+0x39/0x40 [ 54.272745] EIP: native_safe_halt+0x5/0x10 [ 54.273139] EFLAGS: 0246 CPU: 0 [ 54.273624] EAX: EBX: ECX: 0001 EDX: [ 54.274000] ESI: EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10 [ 54.274361] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.274687] default_idle+0x1c/0xf0 [ 54.274896] arch_cpu_idle+0xe/0x10 [ 54.275286] default_idle_call+0x1e/0x30 [ 54.275787] do_idle+0x145/0x1c0 [ 54.276092] cpu_startup_entry+0x65/0x70 [ 54.276441] rest_init+0x62/0x70 [ 54.276718] start_kernel+0x3be/0x3d7 [ 54.276974] i386_start_kernel+0x9d/0xa1 [ 54.277260] startup_32_smp+0x16b/0x16d [ 54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b [ 54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0 [ 54.279829] CR2: [ 54.280143] ---[ end trace 3164b1c0dd7745bc ]--- [ 54.280550] Kernel panic - not syncing: Fatal exception in interrupt [ 54.281078] Kernel Offset: 0x600 from 0xc100 (relocation range: 0xc000-0xdfbfdfff) [ 54.281797] ---[ end Kernel panic - not syncing: Fatal exception in interrupt But since this is love
[Kernel-packages] [Bug 1731163] Re: Trackpoint device not working by default on Thinkpad L570
Someone else seems to have reported this issue on kernel.org in the meantime: https://bugzilla.kernel.org/show_bug.cgi?id=198223 ** Bug watch added: Linux Kernel Bug Tracker #198223 https://bugzilla.kernel.org/show_bug.cgi?id=198223 ** Tags added: kernel-bug-reported-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731163 Title: Trackpoint device not working by default on Thinkpad L570 Status in linux package in Ubuntu: Triaged Bug description: Installing Ubuntu 17.10 on a ThinkPad L570 (L470 should be the same in this regard) leaves the trackpoint as well as the trackpoint buttons in a non-working state. Most probably, it is not correctly detected on startup; dmesg shows kernel: [ 2.997182 ] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input6 As far as I understand it, "GlidePoint" only refers to a touch pad without track point. All events coming from the track point are consequently actively discarded, seen in dmesg as kernel: [ 2279.323441 ] psmouse serio1: alps: Rejected trackstick packet from non DualPoint device Searching for this problem I found this kernel developer discussion which seems related: https://patchwork.kernel.org/patch/9941661/ As suggested by one of the kernel developers there, I added "psmouse.proto=imps" as a kernel boot parameter. The touch pad and track point now show up in the system log as input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6 And it works well now, just as it should. I also noted that the touch pad became a lot more usable at the same time. Previously (with the default installation) it was lagging and could produce pseudo clicks at random. I am submitting this report here in order to help improve the hardware detection in Ubuntu / linux kernel. Ubuntu version: 17.10 Kernel version: 4.13.0.16.17 Default GNOME desktop, Wayland, etc, just as it comes in the default install --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dirichs 896 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:111c Acer, Inc Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20J8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=f2a92db0-5f37-4d70-b878-a4ba4c80e890 ro quiet splash psmouse.proto=imps vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1XET43W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20J8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1XET43W(1.21):bd07/12/2017:svnLENOVO:pn20J8CTO1WW:pvrThinkPadL570:rvnLENOVO:rn20J8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L570 dmi.product.name: 20J8CTO1WW dmi.product.version: ThinkPad L570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731163/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Possible problem with Dell XPS 13 9350. Upgraded to 17.10 before christmas, with kernel ...19. Sudden freeze, when doing powercycle I got a "no bootable device found". I was able to update the BIOS but with no luck. Then I booted 17.04 from USB but Linux was unable to find the disk. However the Samsung controller was found. Has sent the unit in for repair. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741080] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped
** Bug watch added: Linux Kernel Bug Tracker #198291 https://bugzilla.kernel.org/show_bug.cgi?id=198291 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=198291 Importance: Unknown Status: Unknown -- 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/1741080 Title: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 142.828101] usbcore: registered new interface driver usbserial [ 142.828159] usbcore: registered new interface driver usbserial_generic [ 142.828207] usbserial: USB Serial support registered for generic [ 142.840302] usbcore: registered new interface driver option [ 142.840350] usbserial: USB Serial support registered for GSM modem (1-port) [ 146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.14.0-13-generic 4.14.0-13.15 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1740 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 13:13:02 2018 InstallationDate: Installed on 2017-10-13 (82 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.14.0-13-generic N/A linux-backports-modules-4.14.0-13-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1741080/+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 1740290] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped
*** This bug is a duplicate of bug 1741080 *** https://bugs.launchpad.net/bugs/1741080 ** No longer affects: 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/1740290 Title: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Status in linux package in Ubuntu: Triaged Bug description: Hello, dmesg: [ 5519.779175] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.779186] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.779193] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.785793] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.785803] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped [ 5519.819250] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 1655 F...m pulseaudio /dev/snd/controlC0: caravena 1655 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 15:30:53 2017 InstallationDate: Installed on 2017-10-13 (75 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740290/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Kernel 4.14 is LTS (Long Term Support) for SIX years!... so maybe it gets more dev attention than 4.15? dunno. I did read there are some related Touchpad fixes to be rolled into 4.16 and no doubt back ported to 4.14.X -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
This particular bug cannot affect Dell XPS 13 9350 as it is based on Skylake and the intel-spi driver does not even support it. However, in order to boot Linux I think you need at least to switch the SATA controller to AHCI mode as described in: https://wiki.archlinux.org/index.php/Dell_XPS_13_(9350) -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
That's fair enough. I'll be sure to try 4.14.3 as well as the newer .11 variant. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1730904] Re: 17.10 freezes every hour ramdomly
the problem persist after under new kernel: Linux rogelio-K55A 4.14.11-041411-generic #201801022143 SMP Tue Jan 2 21:44:21 UTC 2018 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/1730904 Title: 17.10 freezes every hour ramdomly Status in linux package in Ubuntu: Incomplete Bug description: on 17.04 I had frequent errors reported, now hangs all the computer, please some workaround or way back to 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rogelio1645 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 09:07:15 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1 InstallationDate: Installed on 2017-05-04 (187 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730904/+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 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Amitkumar Karwar (amitkarwar) -- 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/1738773 Title: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno Fix: Updated firmware from Redpine containing a fix for the issue. Regression Potential: Below stress tests are conducted to ensure there is no regression with updated firmware BT mouse + BT keyboard BT mouse + BLE keyboard BT keyboard + BLE mouse BLE keyboard + BLE mouse BT mouse or keyboard + Wifi connected BT mouse + BT keyboard + WiFi connected BLE mouse + BLE keyboard + WiFi Connected BT mouse + BLE keyboard + Wifi connected BLE mouse + BT keyboard + Wifi connected (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + BLE scan BT file transfer from mobile + WiFi connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738773/+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 1741103] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
Public bug reported: starting system ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1027 F pulseaudio piero 1387 F pulseaudio Date: Wed Jan 3 19:19:44 2018 Failure: oops HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a InstallationDate: Installed on 2018-01-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp0s15 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 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: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903 dmi.board.name: P5N-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops -- 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/1741103 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445] Status in linux package in Ubuntu: Confirmed Bug description: starting system ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1027 F pulseaudio piero 1387 F pulseaudio Date: Wed Jan 3 19:19:44 2018 Failure: oops HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a InstallationDate: Installed on 2018-01-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp0s15 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 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: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903 dmi.board.name: P5N-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741103/+subscriptions -- Mailing list: h
[Kernel-packages] [Bug 1741103] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741103 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445] Status in linux package in Ubuntu: Confirmed Bug description: starting system ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1027 F pulseaudio piero 1387 F pulseaudio Date: Wed Jan 3 19:19:44 2018 Failure: oops HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a InstallationDate: Installed on 2018-01-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp0s15 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 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: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903 dmi.board.name: P5N-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741103/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
The problem linked to the bios has Just solved thank to your new instructions (Acer Aspire es1-111m). Thank you guys! -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739765] Re: xt_TCPMSS buffer overflow bug
Use CVE-2017-18017. Thanks ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18017 -- 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/1739765 Title: xt_TCPMSS buffer overflow bug Status in linux package in Ubuntu: Incomplete Bug description: Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13 In few words - corrupted packet might be used to modify memory at router who has xt_TCPMSS used as iptables action. This is really nasty bug, and can be triggered remotely by malicious person on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or VPN provider, for example). This bug existed for several years, i guess. I waited for a while since April, as it's already pushed to stable, and probably all distributions have it updated, so now it's time to do bugreport, to make sure it is really fixed everywhere. Maybe worth to assign CVE for it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+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 1739765] Re: xt_TCPMSS buffer overflow bug
Perfect! Thanks a lot, now i have big reason to ask some sysadmins and vendors to upgrade their kernels. -- 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/1739765 Title: xt_TCPMSS buffer overflow bug Status in linux package in Ubuntu: Incomplete Bug description: Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13 In few words - corrupted packet might be used to modify memory at router who has xt_TCPMSS used as iptables action. This is really nasty bug, and can be triggered remotely by malicious person on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or VPN provider, for example). This bug existed for several years, i guess. I waited for a while since April, as it's already pushed to stable, and probably all distributions have it updated, so now it's time to do bugreport, to make sure it is really fixed everywhere. Maybe worth to assign CVE for it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+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 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
** Summary changed: - openvswitch: kernel opps destroying interfaces on i386 + openvswitch: kernel oops destroying interfaces on i386 -- 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/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in openvswitch source package in Bionic: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1581799] Re: radeon driver hangs : nothing else that static effect on display
Ok, thank you for the information, do I need to report here upstream bug reference after I created bug report? -- 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/1581799 Title: radeon driver hangs : nothing else that static effect on display Status in linux package in Ubuntu: Triaged Bug description: Hi, since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard due to drop support of fglrx driver (that was working) and due to radeon opensource driver not working with my VGA. Mine video card: $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645] $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) . --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: magowiz4930 F...m pulseaudio /dev/snd/pcmC0D0p: magowiz4930 F...m pulseaudio /dev/snd/controlC0: magowiz4930 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a InstallationDate: Installed on 2012-01-03 (1615 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 12/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A55-M LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Re #446 Just for the record - also solved and also running Acer Aspire E3 -111 - P60s with InsydeH20 BIOS. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738791] Re: linux: 4.13.0-22.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1738791 Title: linux: 4.13.0-22.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1738792,1738793,1738794,1738796,1738797 derivatives: 1738798 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1738791/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
The second kernel from step 8 of the new description has solved the problem on my Lenovo S20-30 touch. Thanks for fixing. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737918 Title: linux-aws: 4.4.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737916 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737918/+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 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737920 Title: linux-aws: 4.4.0-1045.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737916 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737920/+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 1739678] Re: HDMI audio makes loud popping noises while playing audio
Thank you. The bug still exists on the latest mainline PPA kernel, 4.15.0-041500rc6-generic. ** 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/1739678 Title: HDMI audio makes loud popping noises while playing audio Status in linux package in Ubuntu: Confirmed Bug description: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P205 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739678/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Step 8 of the updated description on top of the page has solved this issue on a Lenovo Yoga 300 (Ubuntu 17.10) and a Ideapad 100-14IBY (Ubuntu 16.04LTS). Thanks to everybody. Hats off, true piece of master work. I am sorry, if I have written something too emotional. -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739678] Re: HDMI audio makes loud popping noises while playing audio
I've just discovered that, despite my earlier testing, the bug is now also happening on linux-image-4.9.71-040971-generic. I'm going to mark as incomplete once more until I can further narrow down the issue. One other element that might be relevant is that I'm using two video ports: an HDMI port for video, and a DisplayPort cable for audio. In my current round of tests, running both streams over one cable seems to address the issue (but has not always done so), and changing to an interlaced resolution (1080 to 1080i) also seems to fix it (the regular screen is jittery, but YouTube video is clear). I will test for a few days and with different kernels to see if I can isolate the problem and update the bug with my results. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739678 Title: HDMI audio makes loud popping noises while playing audio Status in linux package in Ubuntu: Incomplete Bug description: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P205 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739678/+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 1276651] Re: BCM wl driver crashes during roaming
** Tags added: bionic -- 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/1276651 Title: BCM wl driver crashes during roaming Status in bcmwl package in Ubuntu: Triaged Bug description: Whenever my wireless connection roams from one AP to another AP, I see the following crash [ 5089.124259] [ cut here ] [ 5089.124283] WARNING: CPU: 1 PID: 605 at /home/apw/COD/linux/net/wireless/sme.c:797 cfg80211_roamed+0x97/0xa0 [cfg80211]() [ 5089.124284] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_cirrus parport_pc bnep ppdev rfcomm binfmt_misc nls_iso8859_1 lib80211_crypt_tkip intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd wl(POF) hid_apple joydev hid_generic btusb bluetooth uvcvideo snd_hda_intel snd_hda_codec snd_hwdep nouveau videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core usbhid snd_page_alloc videodev hid snd_seq_midi snd_seq_midi_event bcm5974 i915 snd_rawmidi applesmc snd_seq input_polldev mxm_wmi snd_seq_device wmi lib80211 snd_timer ttm drm_kms_helper cfg80211 snd drm mei_me soundcore microcode i2c_algo_bit mei apple_gmux lpc_ich video apple_bl mac_hid lp parport ahci sdhci_pci libahci sdhci [ 5089.124316] CPU: 1 PID: 605 Comm: wl_event_handle Tainted: PF O 3.13.0-031300-generic #201401192235 [ 5089.124317] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [ 5089.124318] 031d 880457115d68 8173356d 0007 [ 5089.124321] 880457115da8 81067bbc 88045528be1a [ 5089.124323] 880454dc5000 8800362e6120 0095 880407c603c0 [ 5089.124325] Call Trace: [ 5089.124331] [] dump_stack+0x46/0x58 [ 5089.124334] [] warn_slowpath_common+0x8c/0xc0 [ 5089.124336] [] warn_slowpath_null+0x1a/0x20 [ 5089.124345] [] cfg80211_roamed+0x97/0xa0 [cfg80211] [ 5089.124367] [] wl_bss_connect_done.isra.21+0x98/0x1a0 [wl] [ 5089.124383] [] wl_notify_connect_status+0x1fc/0x410 [wl] [ 5089.124399] [] wl_event_handler+0x55/0x220 [wl] [ 5089.124414] [] ? wl_get_assoc_ies+0x240/0x240 [wl] [ 5089.124417] [] kthread+0xc9/0xe0 [ 5089.124419] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124422] [] ret_from_fork+0x7c/0xb0 [ 5089.124424] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124425] ---[ end trace 8ddb9ebe0f635ec5 ]--- [ 5099.616376] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5112.795658] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5127.215934] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1276651/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
suggested fix by Anthony Wong in the description fixed the issue on Lenovo Y50-70. Many thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hello guys, Installing the kernel reported in the bug description step #8 by @'Anthony Wong (anthonywong)' finally solved my problem. Dear @'Anthony Wong (anthonywong)' thank you so much for spending your invaluable time solving this problem. Grettings from Colombia! -- 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: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739807] Re: hisi_sas: driver robustness fixes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739807 Title: hisi_sas: driver robustness fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] There are several bugs in the driver that can cause it to fail during teardown/error recovery. [Test Case] Regression tested by issuing sg_reset commands in a loop during an iozone3 run on a disk attached to a hisi_sas controller. $ iozone -i & $ while :; do sudo sg_reset --device /dev/sda; sleep 5; done [Regression Risk] All fixes are encapsulated within a single driver which was explicitly tested for regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739807/+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 1741139] [NEW] linux: 4.14.0-14.16 -proposed tracker
Public bug reported: This bug is for tracking the 4.14.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Wednesday, 03. January 2018 23:30 UTC -- swm properties -- phase: Packaging ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.
[Kernel-packages] [Bug 1741139] Re: linux: 4.14.0-14.16 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.14.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-phase:Packaging + kernel-phase-changed:Wednesday, 03. January 2018 23:30 UTC ** Description changed: This bug is for tracking the 4.14.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Wednesday, 03. January 2018 23:30 UTC + + -- swm properties -- + phase: Packaging -- 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/1741139 Title: linux: 4.14.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.14.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Wednesday, 03. January 2018 23:30 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1741139/+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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hi. I have Lenovo G50-80. No way to apply the fix, since I'm not able to load Ubuntu. I had dual boot Win 10- Ubuntu 17.10. Didn't know about the bug, so I deleted Ubuntu partition. Now, with original HDD, I have Grub that: "GNU GRUB version 2.02~beta2-36ubuntu11.2 Minimal Bash-like line editing is suppor". I am trying all, booting from Usb, CD ROM, external HDD, also without HDD. No way to load Ubuntu and apply the 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: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed 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: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. 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'. --- 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 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 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
