[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
I've now running: "Linux ucl09404 4.10.0-11-generic #13-Ubuntu SMP Wed Mar 1 21:27:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux" and I still have the problem on my Dell Precision 7510. $ xinput list xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=13 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=14 [slave pointer (2)] Using the stick is impossible, it's far too sensitive. -- 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/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
@Robert, on Ubuntu 16.10 you can install the nvidia-378 drivers that contains the fix for the kernel 4.10 (I'm using it). The patches are available here also : https://devtalk.nvidia.com/default/topic/995636/linux/-patches-378-13-4-10-and-4-11-rc1/ -- 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install
Can you try if either one of "i8042.kbdreset=1" or "i8042.noloop=1" works? The parameter "i8042.reset" and xorg config files should be temporarily removed while testing. -- 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/1641393 Title: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install Status in linux package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded November 13 2016 from the official site) on the above machine, the Elan touchpad was not detected at all. An external mouse works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641393/+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 1664809] Re: [0bda:0328] Card reader failed after S3
verify on 4.4.0-67 & 4.8.0-42 ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- 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/1664809 Title: [0bda:0328] Card reader failed after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Summary: [0bda:0328] Card reader failed after S3 Steps: 1. Check card reader can be used before S3 2. Enter into S3 3. Resume from S3 4. Insert SD/MMC/SDHC into the card reader Expected results: Card reader passed after S3 Actual results: Card reader failed after S3 The card reader device is gone from lsusb Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1664809/+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 1671854] Re: Bluetooth not enabling
Is the bluetooth a USB device? At least it's not listed in your USB devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671854 Title: Bluetooth not enabling Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: i m using hp probook 6460b and i am unbale to enable my bluetooth. i have tried everything i can find on google and http://askubuntu.com. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamran F pulseaudio CurrentDesktop: Unity Date: Fri Mar 10 20:37:29 2017 HibernationDevice: RESUME=UUID=4c928787-6e98-4d4c-9712-faabc24813da InstallationDate: Installed on 2017-03-09 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 003: ID 0461:4dc7 Primax Electronics, Ltd Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ProBook 6460b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=e339ab8f-1d8f-44ed-bba2-a8e950cdbe55 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.08 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU14903Y9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6460b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671854/+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 1668031] Re: Network adapter keeps on hanging up
Gerardus, Can you make a Zesty LiveUSB and test if this issue happens? I just grabbed a Killer 1535 and seems like the issue does not happen on Zesty. I'd like to make sure this issue is solved in 4.10, so I can bisect and backport needed 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/1668031 Title: Network adapter keeps on hanging up Status in linux package in Ubuntu: Incomplete Bug description: Every hour or so, I'm unable to access the internet through this laptop. dmesg usually reports errors related to the network adapter, but not always. Disconnecting from the current Wifi network and connecting to another, usually works. Immediately connecting to the original network after that does not cause the problem to reoccur. At least, not for another hour or so. I'm not sure how to better describe this bug. The network also provides a nfs drive that is mounted on the laptop, if that is significant. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-39-generic 4.8.0-39.42 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruud 2810 F pulseaudio CurrentDesktop: Unity Date: Sun Feb 26 02:13:55 2017 HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b InstallationDate: Installed on 2016-11-08 (109 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668031/+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 1655521] Re: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1655521 Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: Just trying to update using Software Updater ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mitchell 3143 F pulseaudio /dev/snd/controlC1: mitchell 3143 F pulseaudio /dev/snd/controlC0: mitchell 3143 F pulseaudio Date: Tue Jan 10 19:57:12 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2015-08-10 (519 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655521/+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 1655978] Re: Bluetooth not working in Ubuntu 16.4 LTS
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1655978 Title: Bluetooth not working in Ubuntu 16.4 LTS Status in linux package in Ubuntu: Expired Bug description: Bluetooth not working in Ubuntu 16.4 LTS Dear, I want to send files from my phone to my Laptop and vice versa through Bluetooth. But the Bluetooth on my system doesn't work. When I turn on the Bluetooth switch in System Settings > Bluetooth, nothing happens and also the visibility switch on the right hand side is always disabled. please resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naveen 1643 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:33:21 2017 HibernationDevice: RESUME=UUID=f3d17055-5b0c-4721-97fe-46797078d645 InstallationDate: Installed on 2015-07-25 (536 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=8f697990-854f-4760-a486-9c9ba3bf274e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-01-09 (2 days ago) dmi.bios.date: 01/24/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 166D dmi.board.vendor: Hewlett-Packard dmi.board.version: 09.4C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr05941120461610100:rvnHewlett-Packard:rn166D:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 05941120461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655978/+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 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
I've tried manually copy the binary blobs into /boot and the rainbow square disappeared. And when the power is not enough it displayed a "lightning" icon. So if we rebuild an image based on the gadget in edge channel we should be able to fix the problem. -- 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/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+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 1664809] Re: [0bda:0328] Card reader failed after S3
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1664809 Title: [0bda:0328] Card reader failed after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Summary: [0bda:0328] Card reader failed after S3 Steps: 1. Check card reader can be used before S3 2. Enter into S3 3. Resume from S3 4. Insert SD/MMC/SDHC into the card reader Expected results: Card reader passed after S3 Actual results: Card reader failed after S3 The card reader device is gone from lsusb Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1664809/+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 1671459] alkaid (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-55-00/results-index.html -- 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/1671459 Title: linux-lts-trusty: 3.13.0-113.160~precise1 -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 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: In Progress 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: New Bug description: This bug is for tracking the 3.13.0-113.160~precise1 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: 1671232 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/1671459/+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 1671459] alkaid (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_02-15-00/results-index.html -- 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/1671459 Title: linux-lts-trusty: 3.13.0-113.160~precise1 -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 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: In Progress 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: New Bug description: This bug is for tracking the 3.13.0-113.160~precise1 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: 1671232 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/1671459/+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 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove
** Tags added: kernel-da-key kernel-hyper-v ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury) -- 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/1670518 Title: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: Looks like the rebase work missed some prerequisite patches in drivers/pci/host/pci-hyperv.c (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom) commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e Author: Long Li Date: Tue Nov 8 14:04:38 2016 -0800 PCI: hv: Allocate physically contiguous hypercall params buffer hv_do_hypercall() assumes that we pass a segment from a physically contiguous buffer. A buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is set. Use kmalloc() to allocate this buffer. commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614 Author: Tobias Klauser Date: Mon Oct 31 12:04:09 2016 +0100 PCI: hv: Make unnecessarily global IRQ masking functions static Make hv_irq_mask() and hv_irq_unmask() static as they are only used in pci-hyperv.c This fixes a sparse warning. commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3 Author: Dexuan Cui Date: Thu Nov 10 07:19:52 2016 + PCI: hv: Delete the device earlier from hbus->children for hot- remove After we send a PCI_EJECTION_COMPLETE message to the host, the host will immediately send us a PCI_BUS_RELATIONS message with relations->device_count == 0, so pci_devices_present_work(), running on another thread, can find the being-ejected device, mark the hpdev->reported_missing to true, and run list_move_tail()/list_del() for the device -- this races hv_eject_device_work() -> list_del(). Move the list_del() in hv_eject_device_work() to an earlier place, i.e., before we send PCI_EJECTION_COMPLETE, so later the pci_devices_present_work() can't see the device. commit 17978524a636d007e6b929304ae3eb5ea0371019 Author: Dexuan Cui Date: Thu Nov 10 07:18:47 2016 + PCI: hv: Fix hv_pci_remove() for hot-remove 1. We don't really need such a big on-stack buffer when sending the teardown_packet: vmbus_sendpacket() here only uses sizeof(struct pci_message). 2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE to the host, the host will send a RESCIND_CHANNEL message to us and the host won't access the per-channel ringbuffer any longer, so we needn't send PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect the host's completion message of PCI_BUS_D0EXIT, which will never come. 3. We should send PCI_BUS_D0EXIT after hv_send_resources_released(). Signed-off-by: Dexuan Cui Signed-off-by: Bjorn Helgaas Reviewed-by: Jake Oshins Acked-by: K. Y. Srinivasan CC: Haiyang Zhang CC: Vitaly Kuznetsov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670518/+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 1671459] alkaid (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-34-00/results-index.html -- 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/1671459 Title: linux-lts-trusty: 3.13.0-113.160~precise1 -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 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: In Progress 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: New Bug description: This bug is for tracking the 3.13.0-113.160~precise1 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: 1671232 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/1671459/+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 1672563] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1672563 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. ** Changed in: linux (Ubuntu) Status: New => 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/1672563 Title: ubuntu 16.04 doesnt boot normally on my asus k550vx Status in linux package in Ubuntu: Incomplete Bug description: i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in this case when i try to install my nividia graphic cards driver, it never boots again after installation. my graphic card: nvidia 950m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672563/+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 1672563] [NEW] ubuntu 16.04 doesnt boot normally on my asus k550vx
Public bug reported: i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in this case when i try to install my nividia graphic cards driver, it never boots again after installation. my graphic card: nvidia 950m ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672563 Title: ubuntu 16.04 doesnt boot normally on my asus k550vx Status in linux package in Ubuntu: New Bug description: i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in this case when i try to install my nividia graphic cards driver, it never boots again after installation. my graphic card: nvidia 950m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672563/+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 1672198] Re: RTL8723b Kernel driver not loading on normal boot.
It did start as I had to use kernel 4.8 in order to get my multimedia keys and suspend to ram working on that machine. With Kernel 4.4 I had to compile the the driver from lwfinger in order to use wifi. I will test kernel 4.11 tomorrow and 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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Incomplete Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 InstallationDate: Installed on 2016-12-23 (79 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: serena Uname: Linux 4.9.10-040910-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
same, very annoying Thinkpad T440, with Linux Mint 18.1 Cinnamon (based on Ubuntu 16.04) and a Logitech K380 bluetooth keyboard lsb_release -rd Description:Linux Mint 18.1 Serena Release:18.1 uname -a Linux xochiquetzal 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux the error, 2x (note it seems to reconnecct the device with a different number): [71585.431481] usb 2-7: USB disconnect, device number 12 [71585.902507] usb 2-7: new full-speed USB device number 14 using xhci_hcd [71586.032157] usb 2-7: New USB device found, idVendor=8087, idProduct=07dc [71586.032166] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [71586.046505] Bluetooth: hci0: read Intel version: 370710018002030d55 [71586.046510] Bluetooth: hci0: Intel device is already patched. patch num: 55 [71594.739976] hid-generic 0005:046D:B342.0009: unknown main item tag 0x0 [71594.740229] input: Keyboard K380 as /devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B342.0009/input/input25 [71594.740774] hid-generic 0005:046D:B342.0009: input,hidraw2: BLUETOOTH HID v42.00 Keyboard [Keyboard K380] on 5c:c5:d4:04:83:db [71922.708526] usb 2-7: USB disconnect, device number 14 [71923.127502] usb 2-7: new full-speed USB device number 16 using xhci_hcd [71923.256785] usb 2-7: New USB device found, idVendor=8087, idProduct=07dc [71923.256790] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [71923.271836] Bluetooth: hci0: read Intel version: 370710018002030d55 [71923.271838] Bluetooth: hci0: Intel device is already patched. patch num: 55 [71930.531386] hid-generic 0005:046D:B342.000A: unknown main item tag 0x0 [71930.531558] input: Keyboard K380 as /devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B342.000A/input/input26 [71930.532179] hid-generic 0005:046D:B342.000A: input,hidraw2: BLUETOOTH HID v42.00 Keyboard [Keyboard K380] on 5c:c5:d4:04:83:db -- 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/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 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.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/1385113/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
Dear All, I had exactly the same situation of post #23. Coming from Kubuntu 16.04, bought a new system Ryzen 1800x+GA-AB350 Gaming 3. First boot, using the "old" SSD worked fine, so I decided to upgrade to version 16.10. The procedure goes well, but after the reboot got plenty of error message "IRQ VECTOR 07". So I tried with a USB stick and Kubuntu live version 17.04 both beta 1 and Nightly but got the same error. The only way to make the system working, is to manually select kernel 4.4.0-64-generic from grub. I've also tried to install ubuntu kernel 4.10 and 4.11rc1, but I always get the same error. Hope this helps -- 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
Thanks Jonathan, I'll get around to that first thing tomorrow morning. Much appreciated. -- 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/1671063 Title: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM) Status in linux package in Ubuntu: In Progress Bug description: Two test cases failed on this arch: == lttng smoke test list kernel events == PASSED (lttng list --kernel) Error: Unable to list system calls: Not enough memory Error: Command error FAILED (lttng list --kernel --syscall) FAILED (lttng list --kernel --syscall more output expected) == lttng smoke test trace open/close system calls == ... FAILED (did not trace any open system calls) Please find attachment for complete log. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-40-generic 4.8.0-40.43 ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17 Uname: Linux 4.8.0-40-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Mar 8 06:39:24 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.8.0-40-generic N/A linux-backports-modules-4.8.0-40-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671063/+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 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg- 0ubuntu5.3 from yakkety-updates and the tests pass. -- 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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Incomplete Bug description: [Impact] * Some newer Power8 derivates fail to work correctly e.g. Power S822LC (8335-GTB) * This is a toleration change (no exploitation) for those HW releases following the SRU policy of "For Long Term Support releases we regularly want to enable new hardware. Such changes are appropriate provided that we can ensure not to affect upgrades on existing hardware." * Without the Fix that hardware won't run Xenial guests under current Xenials Qemu version * The fix lets processors that support it run in PowerISA 2.07 compatibility mode (plus a few no-op changes as backport dependencies) [Test Case] * Run a Xenial Guest in KVM on one of the specific HW revisions being affected. [Regression Potential] * Changes are PPC only, so fallout should be contained to that * Patches were created by IBM and in Upstream qemu since 2.7 * The effective change is rather small, only allow different compat level on this other cpu class * There are a few refactoring changes needed to get the backport done, while they should be a no-op that is a regression potential (still limited to ppc64el) [Other Info] * Needed for certifying this Hardware for Ubuntu Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el 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 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 Pr
[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
Hi Colin, Please take a look at the following patch https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html Could you report to us if it fixes your issue? Please note that s390 is not supported/tested by LTTng-modules. You probably encountered this bug since no syscalls tracepoints are getting defined on lttng-modules side. Please take a look at this git subtree [1] and the following readme [2] on how to generate it and add the headers for the S390 architecture if you wish to. Cheers [1] https://github.com/lttng/lttng-modules/tree/master/instrumentation/syscalls [2] https://github.com/lttng/lttng-modules/blob/master/instrumentation/syscalls/README -- 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/1671063 Title: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM) Status in linux package in Ubuntu: In Progress Bug description: Two test cases failed on this arch: == lttng smoke test list kernel events == PASSED (lttng list --kernel) Error: Unable to list system calls: Not enough memory Error: Command error FAILED (lttng list --kernel --syscall) FAILED (lttng list --kernel --syscall more output expected) == lttng smoke test trace open/close system calls == ... FAILED (did not trace any open system calls) Please find attachment for complete log. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-40-generic 4.8.0-40.43 ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17 Uname: Linux 4.8.0-40-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Mar 8 06:39:24 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.8.0-40-generic N/A linux-backports-modules-4.8.0-40-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671063/+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 1596469] Re: [Bug]tpm initialization fails on x86
This is a BIOS issue can you please attach dmidecode of your platform, I'd like to know more detailed platform and bios information. Also please add the while dmesg and cat /proc/iomem 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/1596469 Title: [Bug]tpm initialization fails on x86 Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: When trying to test TPM with Ubuntu 16.04 on Intel x86_64 platform, there's tpm initialization failure found in kernel log: root@SKLU1-leg:~# dmesg | grep -i tpm [0.00] ACPI: SSDT 0x7FFE4000 0004D6 (v02 Intel_ Tpm2Tabl 1000 INTL 20141107) [0.00] ACPI: TPM2 0x7FFE2000 34 (v03 ) [2.532245] ima: No TPM chip found, activating TPM-bypass! [3.489431] tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f] [3.489437] tpm_crb: probe of MSFT0101:00 failed with error -16 which leads to tpm device missing under /dev: root@SKLU1-leg:~# ls -l /dev/tpm* ls: cannot access '/dev/tpm*': No such file or directory This error has been fixed with patch below, but not yet merged to upstream kernel: http://git.infradead.org/users/jjs/linux-tpmdd.git/commit/0af6e0a2da2e4fedaa274da438d3b879192b Patch 0af6e0a has dependency to this patch: http://git.infradead.org/users/jjs/linux-tpmdd.git/commit/3f944075e75e28c9cf1af8f82798398b So 0af6e0a has to be applied upon 3f94407, otherwise patch apply fails. I've verified with kernel 4.7-rc4 that above 2 patches can fix this TPM issue. So please Ubuntu team help on backporting these 2 patches into the kernel of their next release. PS, below are some information about Ubuntu & kernel & cpu info on my test server, for your reference: root@SKLU1-leg:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial root@SKLU1-leg:~# uname -a Linux SKLU1-leg 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1596469/+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 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
We received the hardware back and have started testing all blockers again. The latest test of the above mentioned PPA did not yield positive results: "Unable to find PowerPC CPU definition" $ apt-cache policy qemu-system-ppc qemu-system-ppc: Installed: 1:2.5+dfsg-5ubuntu10.10 Candidate: 1:2.5+dfsg-5ubuntu10.10 Version table: *** 1:2.5+dfsg-5ubuntu10.10 500 500 http://ppa.launchpad.net/ci-train-ppa-service/2502/ubuntu xenial/main ppc64el Packages 100 /var/lib/dpkg/status 1:2.5+dfsg-5ubuntu10.9 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 1:2.5+dfsg-5ubuntu10.6 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el Packages 1:2.5+dfsg-5ubuntu10 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages $ uname -a Linux fesenkov 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:30:20 UTC 2017 ppc64le ppc64le ppc64le 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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Incomplete Bug description: [Impact] * Some newer Power8 derivates fail to work correctly e.g. Power S822LC (8335-GTB) * This is a toleration change (no exploitation) for those HW releases following the SRU policy of "For Long Term Support releases we regularly want to enable new hardware. Such changes are appropriate provided that we can ensure not to affect upgrades on existing hardware." * Without the Fix that hardware won't run Xenial guests under current Xenials Qemu version * The fix lets processors that support it run in PowerISA 2.07 compatibility mode (plus a few no-op changes as backport dependencies) [Test Case] * Run a Xenial Guest in KVM on one of the specific HW revisions being affected. [Regression Potential] * Changes are PPC only, so fallout should be contained to that * Patches were created by IBM and in Upstream qemu since 2.7 * The effective change is rather small, only allow different compat level on this other cpu class * There are a few refactoring changes needed to get the backport done, while they should be a no-op that is a regression potential (still limited to ppc64el) [Other Info] * Needed for certifying this Hardware for Ubuntu Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arec
[Kernel-packages] [Bug 1672536] Re: task btrfs:841 blocked for more than 120 seconds.
** Description changed: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:55] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,09] btrfs D 9158a5cd3b08 0 841 26458 0x
Re: [Kernel-packages] [Bug 1672550] [NEW] i40e Intel X710 error during device probe prevents link set up and ip association
Leann, This looks like a kernel patch for your team to evaluate. Thanks. Michael On 03/13/2017 02:49 PM, Launchpad Bug Tracker wrote: > bugproxy (bugproxy) has assigned this bug to you for Ubuntu: > > == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == > While investigating bug #145959 I got blocked in the reproduction process due > to the follow issue during interface link bring up: > > [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC > failed = 14 > [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 > [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map > 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL > > which prevented me to bring the interface up and associate an ip to it. > > == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == > some missing Information kernel is Ubuntu's 4.4.0-62-generic. > > When testing with 4.8.0-36-generic (from xenial's proposed) device probe > works fine, no similar message is seen. > > To obtain some more data on this I added some statements to see which TC > MAP was applied in a healthy probe (note that the other functions, like > function 1 works fine but those functions have no cable on them). > > root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# > dmesg > [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 > [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 > [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 > [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 > [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - > version 1.4.25-k > [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. > [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass > [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 > 0.0.0 > [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 > [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c > [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 > [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC > failed = 14 > [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 > [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map > 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL > [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 > [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 > [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 > RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA > [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass > [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 > 0.0.0 > [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 > [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d > [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 > [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 > [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 > [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 > RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA > > Comparing function 0: > [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 > and function 1: > [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 > > > Then looking at 4.8: > [ 123.425399] i40e: loading out-of-tree module taints kernel. > [ 123.428958] i40e: module verification failed: signature and/or required > key missing - tainting kernel > [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - > version 1.6.11-k > [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. > [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass > [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 > 0.0.0 > [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 > [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c > [ 123.681915] Non-contiguous TC - Disabling DCB > [ 123.690177] i40e 0045:01:00.0: DEBUG DATA vsi > 399, enabled_tc 1 > [ 123.713262] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 > [ 123.864601] i40e 0045:01:00.0: Added LAN device PF0 bus=0x00 func=0x00 > [ 123.864611] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 > [ 123.893254] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 128 > RSS FD_ATR DCB VxLAN Geneve PTP VEPA > [ 123.893321] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass > [ 123.914829] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 > 0.0.0 > [ 124.152980] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 > [ 124.156999] i40e 0045:01:00.1: SAN MAC: 68:05:ca
[Kernel-packages] [Bug 1672550] a more complete log of i40e steps
Default Comment by Bridge ** Attachment added: "a more complete log of i40e steps" https://bugs.launchpad.net/bugs/1672550/+attachment/4837309/+files/file_151930.txt ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672550 Title: i40e Intel X710 error during device probe prevents link set up and ip association Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == While investigating bug #145959 I got blocked in the reproduction process due to the follow issue during interface link bring up: [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL which prevented me to bring the interface up and associate an ip to it. == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == some missing Information kernel is Ubuntu's 4.4.0-62-generic. When testing with 4.8.0-36-generic (from xenial's proposed) device probe works fine, no similar message is seen. To obtain some more data on this I added some statements to see which TC MAP was applied in a healthy probe (note that the other functions, like function 1 works fine but those functions have no cable on them). root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# dmesg [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.25-k [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA Comparing function 0: [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 and function 1: [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 Then looking at 4.8: [ 123.425399] i40e: loading out-of-tree module taints kernel. [ 123.428958] i40e: module verification failed: signature and/or required key missing - tainting kernel [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.6.11-k [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [ 123.681915] Non-contiguous TC - Disabling DCB [ 123.690177] i40e 0045:01:00.0: DEBUG DATA vsi > 399, enabled_tc 1 [ 123.713262] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [ 123.864601] i40e 0045:01:00.0: Added LAN device PF0 bus=0x00 func=0x00 [ 123.864611] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 123.893254] i40e 00
[Kernel-packages] [Bug 1672550] [NEW] i40e Intel X710 error during device probe prevents link set up and ip association
You have been subscribed to a public bug: == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == While investigating bug #145959 I got blocked in the reproduction process due to the follow issue during interface link bring up: [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL which prevented me to bring the interface up and associate an ip to it. == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == some missing Information kernel is Ubuntu's 4.4.0-62-generic. When testing with 4.8.0-36-generic (from xenial's proposed) device probe works fine, no similar message is seen. To obtain some more data on this I added some statements to see which TC MAP was applied in a healthy probe (note that the other functions, like function 1 works fine but those functions have no cable on them). root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# dmesg [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.25-k [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA Comparing function 0: [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 and function 1: [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 Then looking at 4.8: [ 123.425399] i40e: loading out-of-tree module taints kernel. [ 123.428958] i40e: module verification failed: signature and/or required key missing - tainting kernel [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.6.11-k [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [ 123.681915] Non-contiguous TC - Disabling DCB [ 123.690177] i40e 0045:01:00.0: DEBUG DATA vsi > 399, enabled_tc 1 [ 123.713262] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [ 123.864601] i40e 0045:01:00.0: Added LAN device PF0 bus=0x00 func=0x00 [ 123.864611] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 123.893254] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 128 RSS FD_ATR DCB VxLAN Geneve PTP VEPA [ 123.893321] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [ 123.914829] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 124.152980] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [ 124.156999] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [ 124.171266] i40e 0045:01:00.1: DEBUG DATA vsi > 398, enabled_tc 1 [ 124.196080] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [ 124.253353] i40e 0045:01:00.1: Added LAN device PF1 bus=0x00 func=0x01 [ 124.253387] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [ 124.263908] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs
[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf
The following build dependency packages have to be installed when building perf in order to have C++ symbol demangling work. Packages: libiberty-dev, binutils-dev Otherwise if you're building perf via it's Makefile in the linux source code. It will print "libbfd [OFF]" when auto-detecting features. -- 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/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Yakkety: Incomplete Status in linux source package in Zesty: Incomplete Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+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 1672536] 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/1672536 Title: task btrfs:841 blocked for more than 120 seconds. Status in linux package in Ubuntu: Confirmed Bug description: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03]
[Kernel-packages] [Bug 1672544] [NEW] Zesty update to v4.10.2 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.10.2 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.10.2 stable release shall be
applied:
MIPS: pic32mzda: Fix linker error for pic32_get_pbclk()
MIPS: Fix special case in 64 bit IP checksumming.
MIPS: BCM47XX: Fix button inversion for Asus WL-500W
MIPS: OCTEON: Fix copy_from_user fault handling for large buffers
MIPS: Lantiq: Keep ethernet enabled during boot
MIPS: Clear ISA bit correctly in get_frame_info()
MIPS: Prevent unaligned accesses during stack unwinding
MIPS: Fix get_frame_info() handling of microMIPS function size
MIPS: Fix is_jump_ins() handling of 16b microMIPS instructions
MIPS: Calculate microMIPS ra properly when unwinding the stack
MIPS: Handle microMIPS jumps in the same way as MIPS32/MIPS64 jumps
mmc: sdhci-acpi: support deferred probe
am437x-vpfe: always assign bpp variable
uvcvideo: Fix a wrong macro
media: fix dm1105.c build error
cxd2820r: fix gpio null pointer dereference
dvb-usb: don't use stack for firmware load
lirc_dev: LIRC_{G,S}ET_REC_MODE do not work
media: Properly pass through media entity types in entity enumeration
ext4: fix deadlock between inline_data and ext4_expand_extra_isize_ea()
spi: s3c64xx: fix inconsistency between binding and driver
ARM: at91: define LPDDR types
ARM: dts: at91: Enable DMA on sama5d4_xplained console
ARM: dts: at91: Enable DMA on sama5d2_xplained console
ALSA: hda/realtek - Cannot adjust speaker's volume on a Dell AIO
ALSA: hda - fix Lewisburg audio issue
ALSA: timer: Reject user params with too small ticks
ALSA: ctxfi: Fallback DMA mask to 32bit
ALSA: seq: Fix link corruption by event error handling
ALSA: hda - Add subwoofer support for Dell Inspiron 17 7000 Gaming
ALSA: hda - Fix micmute hotkey problem for a lenovo AIO machine
hwmon: (it87) Do not overwrite bit 2..6 of pwm control registers
hwmon: (it87) Ensure that pwm control cache is current before updating values
staging: greybus: loopback: fix broken udelay
staging/lustre/lnet: Fix allocation size for sv_cpt_data
staging: rtl: fix possible NULL pointer dereference
coresight: STM: Balance enable/disable
coresight: fix kernel panic caused by invalid CPU
regulator: Fix regulator_summary for deviceless consumers
tpm_tis: use default timeout value if chip reports it as zero
tpm_tis: fix the error handling of init_tis()
iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu
iommu/vt-d: Tylersburg isoch identity map check is done too late.
CIFS: Fix splice read for non-cached files
mm, devm_memremap_pages: hold device_hotplug lock over mem_hotplug_{begin, done}
mm/page_alloc: fix nodes for reclaim in fast path
mm: vmpressure: fix sending wrong events on underflow
mm: do not access page->mapping directly on page_endio
mm balloon: umount balloon_mnt when removing vb device
mm, vmscan: cleanup lru size claculations
mm, vmscan: consider eligible zones in get_scan_count
sigaltstack: support SS_AUTODISARM for CONFIG_COMPAT
ipc/shm: Fix shmat mmap nil-page protection
ima: fix ima_d_path() possible race with rename
PM / devfreq: Fix available_governor sysfs
PM / devfreq: Fix wrong trans_stat of passive devfreq device
dm cache: fix corruption seen when using cache > 2TB
dm stats: fix a leaked s->histogram_boundaries array
dm round robin: revert "use percpu 'repeat_count' and 'current_path'"
dm raid: fix data corruption on reshape request
scsi: qla2xxx: Cleaned up queue configuration code.
scsi: qla2xxx: Fix response queue count for Target mode.
scsi: qla2xxx: Fix Regression introduced by pci_alloc_irq_vectors_affinity call.
Revert "scsi: aacraid: Reorder Adapter status check"
scsi: aacraid: Reorder Adapter status check
scsi: use 'scsi_device_from_queue()' for scsi_dh
power: reset: at91-poweroff: timely shutdown LPDDR memories
Fix: Disable sys_membarrier when nohz_full is enabled
jbd2: don't leak modified metadata buffers on an aborted journal
block/loop: fix race between I/O and set_status
loop: fix LO_FLAGS_PARTSCAN hang
ext4: Include forgotten start block on fallocate insert range
ext4: do not polute the extents cache while shifting extents
ext4: trim allocation requests to group size
ext4: fix data corruption in data=journal mode
ext4: fix use-after-iput when fscrypt contexts are inconsistent
ext4: fix inline data error paths
ext4: preserve the needs_recovery flag when the journal is aborted
ext4: return EROFS if device is r/o and journal replay is needed
ext4: fix fencepost in s_first_meta_bg validation
samples/seccomp: fix 64-bit comparison macr
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
@Eric: I've managed to boot the system using your custom built kernel! Not usable really now as the nvidia driver installation is failing but much better... So clearly the code around PINCTRL_AMD seems to be related. -- 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove
Could you please build a test kernel which is: 1) based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667531 2) AND, with including the missing patches of this bug. Thanks, Simon -- 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/1670518 Title: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: Looks like the rebase work missed some prerequisite patches in drivers/pci/host/pci-hyperv.c (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom) commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e Author: Long Li Date: Tue Nov 8 14:04:38 2016 -0800 PCI: hv: Allocate physically contiguous hypercall params buffer hv_do_hypercall() assumes that we pass a segment from a physically contiguous buffer. A buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is set. Use kmalloc() to allocate this buffer. commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614 Author: Tobias Klauser Date: Mon Oct 31 12:04:09 2016 +0100 PCI: hv: Make unnecessarily global IRQ masking functions static Make hv_irq_mask() and hv_irq_unmask() static as they are only used in pci-hyperv.c This fixes a sparse warning. commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3 Author: Dexuan Cui Date: Thu Nov 10 07:19:52 2016 + PCI: hv: Delete the device earlier from hbus->children for hot- remove After we send a PCI_EJECTION_COMPLETE message to the host, the host will immediately send us a PCI_BUS_RELATIONS message with relations->device_count == 0, so pci_devices_present_work(), running on another thread, can find the being-ejected device, mark the hpdev->reported_missing to true, and run list_move_tail()/list_del() for the device -- this races hv_eject_device_work() -> list_del(). Move the list_del() in hv_eject_device_work() to an earlier place, i.e., before we send PCI_EJECTION_COMPLETE, so later the pci_devices_present_work() can't see the device. commit 17978524a636d007e6b929304ae3eb5ea0371019 Author: Dexuan Cui Date: Thu Nov 10 07:18:47 2016 + PCI: hv: Fix hv_pci_remove() for hot-remove 1. We don't really need such a big on-stack buffer when sending the teardown_packet: vmbus_sendpacket() here only uses sizeof(struct pci_message). 2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE to the host, the host will send a RESCIND_CHANNEL message to us and the host won't access the per-channel ringbuffer any longer, so we needn't send PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect the host's completion message of PCI_BUS_D0EXIT, which will never come. 3. We should send PCI_BUS_D0EXIT after hv_send_resources_released(). Signed-off-by: Dexuan Cui Signed-off-by: Bjorn Helgaas Reviewed-by: Jake Oshins Acked-by: K. Y. Srinivasan CC: Haiyang Zhang CC: Vitaly Kuznetsov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670518/+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 1672510] Re: kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el
** Changed in: linux (Ubuntu Zesty) 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/1672510 Title: kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz Error building some of the tests, likely because of generating position independent executables by default: ptrace-gpr.c: In function ‘gpr’: ptrace-gpr.c:30:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-gpr] Error 1 ptrace-tm-gpr.c: In function ‘tm_gpr’: ptrace-tm-gpr.c:34:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-gpr] Error 1 ptrace-tm-spd-gpr.c: In function ‘tm_spd_gpr’: ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-spd-gpr] Error 1 make[1]: Target 'all' not remade because of errors. make: *** [ptrace] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672510/+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 1672536] [NEW] task btrfs:841 blocked for more than 120 seconds.
Public bug reported: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:55] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,09] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,07] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +
[Kernel-packages] [Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic
** No longer affects: linux (Ubuntu Vivid) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672470 Title: ip_rcv_finish() NULL pointer kernel panic Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: In Progress Bug description: The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When the skb leaves the bridge, it removes the fake dst and places a real dst onto it. However, it uses a hook to do this, and when the br_netfilter module is unloading it unregisters that hook. Any skbs that are currently being processed in the bridge by the br_netfilter module, but that leave the bridge after the hook is unregistered (or, during br_netfilter module load, before the hook is registered) will still have the fake dst; when other code then tries to process that dst, it causes a kernel panic because the dst is invalid. Recent upstream discussion: https://www.spinics.net/lists/netdev/msg416912.html Upstream patch (not yet merged into net-next): https://patchwork.ozlabs.org/patch/738275/ example panic report: [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null) [ 214.612199] IP: [< (null)>] (null) [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca procmemro(O) nokeyctl(O) noptrace(O) [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1 [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.13a.0.0713160937 07/13/16 [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 8810392b [ 215.331207] RIP: 0010:[<>] [< (null)>] (null) [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286 [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: [ 215.569836] RDX: RSI: RDI: 881011067100 [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0 [ 215.740629] R10: R11: R12: 881018917dce [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078 [ 215.911432] FS: () GS:88103fec() knlGS: [ 216.008274] CS: 0010 DS: ES: CR0: 80050033 [ 216.077032] CR2: CR3: 001011b9d000 CR4: 001406e0 [ 216.162430] Stack: [ 216.186461] 8157d7f9 881011067100 881018917dce 88101163 [ 216.275407] 81c9be00 88103fec3918 8157e0db [ 216.364352] [ 216.453301] Call Trace: [ 216.482536] [ 216.505533] [] ? ip_rcv_finish+0x99/0x320 [ 216.575442] [] ip_rcv+0x25b/0x370 [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20 [ 216.712965] [] __netif_receive_skb+0x18/0x60 [ 216.783801] [] netif_receive_skb_internal+0x23/0x80 [ 216.861921] [] netif_receive_skb+0x1c/0x70 [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge] [ 217.016091] [] ? ___slab_alloc+0x1d0/0x440 [ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 [br_netfilter] [ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 [br_netfilter] [ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge] [ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 [br_netfilter] [ 217.437891] [] nf_iterate+0x5d/0x70 [ 217.499367] [] nf_hook_slow+0x64/0xc0 [ 217.562928] [] br_handle_frame+0x1b9/0x290 [bridge] [ 217.641048] [] ? br_handle_local_finish+0x80/0x80 [bridge] [ 217.726446] [] __netif_receive_skb_core+0x342/0xa20 [ 217.804566] [] ? tcp4_gro_receive+0x126/0x1d0 [ 217.876445] [] ? inet_gro_receive+0x1c6/0x250 [ 217.948322] [] __netif_receive_skb+0x18/0x60 [ 218.019161] [] netif_receive_skb_internal+0x23/0x80 [ 218.097281] [] napi_gro_receive+0xc3/0x110 [ 218.166051] [] ixgbe_clean_rx_irq+0x52f/0xa70 [ixgbe] [ 218.246255] [] ixgbe_poll+0x438/0x790 [ixgbe] [ 218.318131] [] net_rx_action+0x1ee/0x320 [ 218.384813] [] ? handle_irq_event_percpu+0x167/0x1d0 [ 218.463973] [] __do_softirq+0x101/0x280 [ 218.529608] [] irq_exit+0x8e/0x90 [ 218.589007] [] do_IRQ+0x54/0xd0 [ 218.646323] [] common_interrupt+0x82/0x82 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672470/+subscriptions -- Mailing list: https:/
[Kernel-packages] [Bug 1672486] Re: arm64: Workaround QDF2400 erratum 0065
** Also affects: linux (Ubuntu Zesty) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu Zesty) 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/1672486 Title: arm64: Workaround QDF2400 erratum 0065 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: QDF2400 platforms require an erratum workaround to avoid a memory corruption issue. This was fixed upstream in the following commit: commit 90922a2d03d84de36bf8a9979d62580102f31a92 Author: Shanker Donthineni Date: Tue Mar 7 08:20:38 2017 -0600 irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065 On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt Translation Entry (ITE), but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size. It might cause kernel memory corruption depending on the number of MSI(x) that are configured and the amount of memory that has been allocated for ITEs in its_create_device(). This patch fixes the potential memory corruption by setting the correct ITE size to 16Bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672486/+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 1672504] Re: pinctrl: qcom: add get_direction function
** Also affects: linux (Ubuntu Zesty) Importance: Medium Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu Zesty) 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/1672504 Title: pinctrl: qcom: add get_direction function Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: On QDF2400 systems (ACPI-based), the kernel currently assumes all GPIOs from the qcom/pinctrl driver are configured for input. However, UEFI may have configured them for output. An upstream fix addresses this by adding a get_direction function: commit 8e51533780ba223a3562ff4382c6b6f350c7e9a4 Author: Timur Tabi Date: Fri Feb 10 17:21:00 2017 -0600 pinctrl: qcom: add get_direction function The get_direction callback function allows gpiolib to know the current direction (input vs output) for a given GPIO. This is particularly useful on ACPI systems, where the GPIOs are configured only by firmware (typically UEFI), so the only way to know the initial values to query the hardware directly. Without this function, gpiolib thinks that all GPIOs are configured for input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672504/+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 1672502] Re: arm64 MSI/PCIe passthrough patches break build of certain configs
** Also affects: linux (Ubuntu Zesty) Importance: Low Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu Zesty) 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/1672502 Title: arm64 MSI/PCIe passthrough patches break build of certain configs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: The zesty kernel has a backport of the MSI/PCIe passthrough changes for arm64. This changeset introduced a bug that can cause a build failure with certain configurations. Though it doesn't impact the Ubuntu config, it could creep up again if we change our config. I reproduced it on Ubuntu source b building the s390x image with CONFIG_PCI=n and CONFIG_IRQ_DOMAIN=n. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672502/+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 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install
Installed development kernel 4.11.0-041100rc2-lowlatency overnight as promised - no change in behaviour, buttons still not recognised. Also same behaviour with 4.11.0-041100rc2-generic module that loaded last -- 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/1644919 Title: [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install Status in linux package in Ubuntu: Incomplete Bug description: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE P57 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB0B dmi.board.asset.tag: Default string dmi.board.name: P57 dmi.board.vendor: GIGABYTE dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: P57 dmi.product.version: Default string dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install
Could you please let me know what the next step in faultfinding is? Regards, Andrew F -- 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/1641393 Title: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install Status in linux package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded November 13 2016 from the official site) on the above machine, the Elan touchpad was not detected at all. An external mouse works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install
Installed development module overnight 4.11.0-041100rc2-generic and commented out the above changes in the /etc/default/grub. Working at the moment, but it's intermittent. I did leave the /50-synaptics file with the extra two lines alone, so they loaded. Joseph - I recall an email asking me to comment out the i8042.nomux=1(?) in the kernel. I can't find that - where would I find it? (was not in /proc/cmdline) Regards, Andrew F -- 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/1641393 Title: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install Status in linux package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded November 13 2016 from the official site) on the above machine, the Elan touchpad was not detected at all. An external mouse works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641393/+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 1672521] 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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837215/+files/Lspci.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837216/+files/Lsusb.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837217/+files/ProcCpuinfo.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837221/+files/WifiSyslog.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
Hi Cosmin, thanks a lot for the details. I can see a couple of differences that I need to look into: - Chipset is different B350 vs. X370 - I attempted the fresh 16.04 install from a USB stick instead of a DVD (I've got no optical drive at all, so can't test that) -> IRQ TRAP (same with 16.10 and 17.04 beta) So my next tentative will be to take the drive out from that computer, install in a different one and perform the 16.04 install and move it back to the Ryzen system. That would be similar to your initial state with a working 16.04. One last question (:-), was your existing 16.04 running on a special kernel version before you moved your SSD to your new Ryzen system? 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1672521] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837220/+files/UdevDb.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837213/+files/CurrentDmesg.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837214/+files/JournalErrors.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837219/+files/ProcModules.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837218/+files/ProcInterrupts.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: arm64 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: dmi.product.name: R120-T30 dmi.product.version: 0100 dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672521] Re: ThunderX: soft lockup on 4.8+ kernels
apport information ** Tags added: apport-collected xenial ** Description changed: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Mar 13 19:27 seq + crw-rw 1 root audio 116, 33 Mar 13 19:27 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: arm64 + 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 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: GIGABYTE R120-T30 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=vt220 + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-41-generic N/A + linux-backports-modules-4.8.0-41-generic N/A + linux-firmware1.157.8 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.8.0-41-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/22/2016 + dmi.bios.vendor: GIGABYTE + dmi.bios.version: T22 + dmi.board.asset.tag: 01234567890123456789AB + dmi.board.name: MT30-GS0 + dmi.board.vendor: GIGABYTE + dmi.board.version: 01234567 + dmi.chassis.asset.tag: 01234567890123456789AB + dmi.chassis.type: 17 + dmi.chassis.vendor: GIGABYTE + dmi.chassis.version: 01234567 + dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567: + dmi.product.name: R120-T30 + dmi.product.version: 0100 + dmi.sys.vendor: GIGABYTE ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1672521/+attachment/4837212/+files/CRDA.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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Confirmed Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple wa
Re: [Kernel-packages] [Bug 1672224] Re: Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major chaos/failures
Yes, booting an old kernel gives a good system. On Mar 13, 2017 12:21 PM, "Joseph Salisbury" wrote: > Does the bug go away if you boot back into the prior kernel version? > > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > ** Also affects: linux (Ubuntu Xenial) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu Xenial) >Status: New => Confirmed > > ** Changed in: linux (Ubuntu Xenial) >Importance: Undecided => High > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1672224 > > Title: > Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major > chaos/failures > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Xenial: > Confirmed > > Bug description: > The most obvious issue upon logging in was that there were no network > interfaces save the loopback. > A review of the logs suggested there were many major problems with the > upgrade. > > Interestingly, the system suggested that I delete all other versions > of the kernel immediately after this failed upgrade. This would have > rendered the system nearly unusable. > > This is not the user experience I was thinking of when I chose an LTS > version. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-66-generic 4.4.0-66.87 > ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 > Uname: Linux 4.4.0-63-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: doug 2348 F pulseaudio >/dev/snd/controlC2: doug 2348 F pulseaudio >/dev/snd/controlC0: doug 2348 F pulseaudio > CurrentDesktop: Unity > Date: Sun Mar 12 15:23:41 2017 > EcryptfsInUse: Yes > HibernationDevice: RESUME=UUID=caabec9a-7ba2-451a-91a5-af1bef3bfc38 > InstallationDate: Installed on 2017-01-20 (51 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > IwConfig: >lono wireless extensions. > >enp6s0no wireless extensions. > MachineType: System manufacturer System Product Name > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 VESA VGA > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic > root=UUID=ecd4d068-85e7-40c9-8483-d2dbfaadc20b ro rootflags=subvol=@ > quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.4.0-63-generic N/A >linux-backports-modules-4.4.0-63-generic N/A >linux-firmware1.157.8 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/10/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 0908 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: P8Z77-V LE PLUS > 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.:bvr0908:bd12/10/2013: > svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion: > rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS: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/ > 1672224/+subscriptions > -- 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/1672224 Title: Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major chaos/failures Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The most obvious issue upon logging in was that there were no network interfaces save the loopback. A review of the logs suggested there were many major problems with the upgrade. Interestingly, the system suggested that I delete all other versions of the kernel immediately after this failed upgrade. This would have rendered the system nearly unusable. This is not the user experience I was thinking of when I chose an LTS version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Appo
[Kernel-packages] [Bug 1672521] [NEW] ThunderX: soft lockup on 4.8+ kernels
Public bug reported: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: New Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672521/+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 1672510] [NEW] kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz Error building some of the tests, likely because of generating position independent executables by default: ptrace-gpr.c: In function ‘gpr’: ptrace-gpr.c:30:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-gpr] Error 1 ptrace-tm-gpr.c: In function ‘tm_gpr’: ptrace-tm-gpr.c:34:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-gpr] Error 1 ptrace-tm-spd-gpr.c: In function ‘tm_spd_gpr’: ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-spd-gpr] Error 1 make[1]: Target 'all' not remade because of errors. make: *** [ptrace] Error 2 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Zesty) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Zesty) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- 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/1672510 Title: kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz Error building some of the tests, likely because of generating position independent executables by default: ptrace-gpr.c: In function ‘gpr’: ptrace-gpr.c:30:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-gpr] Error 1 ptrace-tm-gpr.c: In function ‘tm_gpr’: ptrace-tm-gpr.c:34:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-gpr] Error 1 ptrace-tm-spd-gpr.c: In function ‘tm_spd_gpr’: ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by ‘r30’ in ‘asm’ asm __volatile__( ^~~ make[1]: *** [ptrace-tm-spd-gpr] Error 1 make[1]: Target 'all' not remade because of errors. make: *** [ptrace] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672510/+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 1659111] Comment bridged from LTC Bugzilla
--- Comment From thiag...@br.ibm.com 2017-03-13 15:22 EDT--- Small update: The following commit is not actually necessary. It fixes code which is not present in v4.4: e17354961bb5 zram_drv: update for backing dev info changes -- 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/1659111 Title: UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic Status in linux package in Ubuntu: Incomplete Bug description: Attn. Canonical: For your awareness only at this time. == Comment: #0 - LEKSHMI C. PILLAI - 2016-11-22 03:49:38 == Machine INFO KVM HOST: luckyv1 Guest :lucky05 lucky05 crashed while running the I/O stress test for SAN disks. Installed lucky05 and enabled the xmon on that.After that started the RAW disk test on around 50 disks.After 6-7 hours after running,Now machine dropped into xmon. Logs: [25023.224182] Unable to handle kernel paging request for data at address 0x [25023.224257] Faulting instruction address: 0xc0324c60 cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620] pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290 lr: c032831c: writeback_sb_inodes+0x30c/0x590 sp: c000fffc38a0 msr: 80019033 dar: 0 dsisr: 4000 current = 0xc000ff99e470 paca= 0xcfb41c80 softe: 0irq_happened: 0x01 pid = 14736, comm = kworker/u16:8 enter ? for help [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> f 3:mon> th [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> sh [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks: [27384.651220] (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992) [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 (4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0 [27384.651501] rcu_sched kthread starved for 40596 jiffies! g2849830 c2849829 f0x2 s3 ->state=0x0 [27384.651747] INFO: rcu_sched detected stalls on CPUs/tasks: [27384.651905] (detected by 4, t=590354 jiffies, g=2849830, c=2849829, q=1285) [27384.652012] All QSes seen, last rcu_sched kthread activity 590352 (4301738470-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0 [27384.652191] rcu_sched kthread starved for 590352 jiffies! g2849830 c2849829 f0x2 s3 ->state=0x0 [27384.730645] Unable to handle kernel paging request for data at address 0xffd8 [27384.730781] Faulting instruction address: 0xc00e7258 cpu 0x3: Vector: 300 (Data Access) at [c000fffc3000] pc: c00e7258: kthread_data+0x28/0x40 lr: c00de940: wq_worker_sleeping+0x30/0x110 sp: c000fffc3280 msr: 80019033 dar: ffd8 dsisr: 4000 current = 0xc000ff99e470 paca= 0xcfb41c80 softe: 0irq_happened: 0x01 pid = 14736, comm = kworker/u16:8 enter ? for help == Comment: #1 - LEKSHMI C. PILLAI - 2016-11-22 04:05:41 == 3:mon> th [c000fffc32b0] c00de940 wq_worker_sleeping+0x30/0x110 [c000fffc32f0] c0af31bc __schedule+0x6ec/0x990 [c000fffc33c0] c0af34a8 schedule+0x48/0xc0 [c000fffc33f0] c00bd3d0 do_exit+0x760/0xc30 [c000fffc34b0] c0020bf4 die+0x314/0x470 [c000fffc3540] c0050d98 bad_page_fault+0xd8/0x150 [c000fffc35b0] c0008680 handle_page_fault+0x2c/0x30 --- Exception: 300 (Data Access) at c0324c60 locked_inode_to_wb_and_lock_list+0x50/0x290 [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set
** Changed in: makedumpfile (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1670696
Title:
Typo in error msg when no crashkernel memory reservation is set
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Zesty:
In Progress
Status in makedumpfile package in Debian:
Unknown
Bug description:
[Impact]
* There is a typo in ERRMSG of function show_mem_usage affecting
Xenial/Zesty, Debian and makedumpfile upstream.
This should be :
"show_mem_usage: No memory is reserved for crashkernel!"
instead of :
"show_mem_usage: No memory is reserved for crashkenrel!"
The typo is located here in src code :
# filename : makedumpfile.c
-
int show_mem_usage(void)
{
uint64_t vmcoreinfo_addr, vmcoreinfo_len;
struct cycle cycle = {0};
if (!is_crashkernel_mem_reserved()) {
==> ERRMSG("No memory is reserved for crashkenrel!\n");
return FALSE;
}
-
[Test Case]
* Take a system with no crashkernel memory reservation set
* run command : makedumpfile --mem-usage /proc/kcore
* Error message :
show_mem_usage: No memory is reserved for crashkenrel!
[Regression Potential]
* No regression, it is a trivial change with no behavioural change.
[Other Info]
* Upstream:
Patch has been submitted upstream (ML :ke...@lists.infradead.org)
- AFAIK, there is no upstream bug database, so no URL available, ML only.
- Patch will be merge in upstream version 1.6.2 # See comment #4
* Debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+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 1671962] Re: Problems
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1671962 Title: Problems Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have a desktop Mac and I installed Xubuntu. My problem is that I can't modify the brightness. Best regards! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 10 16:42:33 2017 HibernationDevice: RESUME=UUID=d7c318e9-9459-4457-aef4-6f13499ee89c InstallationDate: Installed on 2016-04-27 (317 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Apple Inc. iMac12,2 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=19fd4f5f-4139-42ff-9b13-932fffaea0cb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-10 (212 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM121.88Z.0047.B1F.1201241648 dmi.board.name: Mac-942B59F58194171B dmi.board.vendor: Apple Inc. dmi.board.version: iMac12,2 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B59F58194171B dmi.modalias: dmi:bvnAppleInc.:bvrIM121.88Z.0047.B1F.1201241648:bd01/24/12:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B: dmi.product.name: iMac12,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/1671962/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672470] Re: ip_rcv_finish() NULL pointer kernel panic
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Vivid) Status: New => Confirmed ** Changed in: linux (Ubuntu Trusty) 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/1672470 Title: ip_rcv_finish() NULL pointer kernel panic Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: In Progress Bug description: The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When the skb leaves the bridge, it removes the fake dst and places a real dst onto it. However, it uses a hook to do this, and when the br_netfilter module is unloading it unregisters that hook. Any skbs that are currently being processed in the bridge by the br_netfilter module, but that leave the bridge after the hook is unregistered (or, during br_netfilter module load, before the hook is registered) will still have the fake dst; when other code then tries to process that dst, it causes a kernel panic because the dst is invalid. Recent upstream discussion: https://www.spinics.net/lists/netdev/msg416912.html Upstream patch (not yet merged into net-next): https://patchwork.ozlabs.org/patch/738275/ example panic report: [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null) [ 214.612199] IP: [< (null)>] (null) [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca procmemro(O) nokeyctl(O) noptrace(O) [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1 [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.13a.0.0713160937 07/13/16 [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 8810392b [ 215.331207] RIP: 0010:[<>] [< (null)>] (null) [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286 [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: [ 215.569836] RDX: RSI: RDI: 881011067100 [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0 [ 215.740629] R10: R11: R12: 881018917dce [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078 [ 215.911432] FS: () GS:88103fec() knlGS: [ 216.008274] CS: 0010 DS: ES: CR0: 80050033 [ 216.077032] CR2: CR3: 001011b9d000 CR4: 001406e0 [ 216.162430] Stack: [ 216.186461] 8157d7f9 881011067100 881018917dce 88101163 [ 216.275407] 81c9be00 88103fec3918 8157e0db [ 216.364352] [ 216.453301] Call Trace: [ 216.482536] [ 216.505533] [] ? ip_rcv_finish+0x99/0x320 [ 216.575442] [] ip_rcv+0x25b/0x370 [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20 [ 216.712965] [] __netif_receive_skb+0x18/0x60 [ 216.783801] [] netif_receive_skb_internal+0x23/0x80 [ 216.861921] [] netif_receive_skb+0x1c/0x70 [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge] [ 217.016091] [] ? ___slab_alloc+0x1d0/0x440 [ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 [br_netfilter] [ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 [br_netfilter] [ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge] [ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 [b
[Kernel-packages] [Bug 1671996] Re: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-38-generic is not ready for configuration cann
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1671996 Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-38-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 LTS several problems after updating from previous version 14.xx. Cant get packages installed. For example these lines give nothing on screen, 1) cat /proc/version_signature > version.log 2) sudo lspci -vnvn > lspci-vnvn.log ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-38-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kari 1523 F pulseaudio Date: Sat Mar 4 09:41:34 2017 DuplicateSignature: package:linux-image-extra-4.4.0-38-generic:(not installed) Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... dpkg: error processing package linux-image-extra-4.4.0-38-generic (--configure): package linux-image-extra-4.4.0-38-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=66d27ffa-9c2e-4c7b-ae16-ea787f091715 InstallationDate: Installed on 2016-08-14 (208 days ago) InstallationMedia: Ubuntu 16.04 LTS (Finnish Remix) "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 1951FDG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=75be3895-5a85-4082-806c-c484404bbc41 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 SourcePackage: linux Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETC9WW (2.09 ) dmi.board.name: 1951FDG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETC9WW(2.09):bd12/22/2006:svnLENOVO:pn1951FDG:pvrThinkPadT60:rvnLENOVO:rn1951FDG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1951FDG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671996/+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 1672198] Re: RTL8723b Kernel driver not loading on normal boot.
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Incomplete Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 InstallationDate: Installed on 2016-12-23 (79 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: serena Uname: Linux 4.9.10-040910-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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 1672200] Re: Kernel error on i915 gpu driver
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672200 Title: Kernel error on i915 gpu driver Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: The following error (warning?) shows up in dmesg during every boot: [3.244312] [ cut here ] [3.244397] WARNING: CPU: 0 PID: 170 at /build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2d4/0x5f0 [i915]() [3.244410] WARN_ON(!encoder->crtc) [3.244413] Modules linked in: [3.244419] i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes video [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 4.4.0-66-generic #87-Ubuntu [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006 [3.244477] Workqueue: events_unbound async_run_entry_fn [3.244484] c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 f8d3b99c f5da5d34 [3.244499] c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 f8ceb9a4 f8ceb9a4 [3.244514] 0001 0001 f5da5d50 c10704ce 0009 f5da5d44 f8d46600 [3.244530] Call Trace: [3.244541] [] dump_stack+0x58/0x79 [3.244550] [] warn_slowpath_common+0x87/0xc0 [3.244615] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.244678] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.244687] [] warn_slowpath_fmt+0x3e/0x60 [3.244750] [] intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.244759] [] ? idr_alloc+0xa4/0x120 [3.244823] [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915] [3.244847] [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper] [3.244866] [] ? drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper] [3.244879] [] ? schedule+0x2d/0x80 [3.244898] [] drm_fb_helper_initial_config+0xbc/0x400 [drm_kms_helper] [3.244911] [] ? put_prev_entity+0x33/0xcc0 [3.244919] [] ? pick_next_task_fair+0x501/0x520 [3.244982] [] intel_fbdev_initial_config+0x19/0x20 [i915] [3.244991] [] async_run_entry_fn+0x4e/0x170 [3.245000] [] process_one_work+0x121/0x3f0 [3.245009] [] worker_thread+0x37/0x490 [3.245017] [] ? process_one_work+0x3f0/0x3f0 [3.245025] [] kthread+0xa6/0xc0 [3.245034] [] ret_from_kernel_thread+0x21/0x38 [3.245042] [] ? kthread_create_on_node+0x170/0x170 [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]--- [3.251264] fbcon: inteldrmfb (fb0) is primary device [3.251911] [ cut here ] [3.251933] WARNING: CPU: 0 PID: 170 at /build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]() [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes video [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW 4.4.0-66-generic #87-Ubuntu [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006 [3.251956] Workqueue: events_unbound async_run_entry_fn [3.251962] c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f f85c51f0 f5da5b6c [3.251966] c1070457 c19d054c 00aa f85c51f0 02d3 f85bb98a f85bb98a [3.251970] f67f8800 f07fc400 f5da5b7c c1070562 0009 f5da5ba4 [3.251971] Call Trace: [3.251977] [] dump_stack+0x58/0x79 [3.251981] [] warn_slowpath_common+0x87/0xc0 [3.251994] [] ? drm_atomic_helper_update_lega
[Kernel-packages] [Bug 1672318] Re: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1672318 Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Incomplete Bug description: happened during the post trigger install part ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155 ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39 Uname: Linux 3.13.0-110-generic i686 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: debbie 1478 F pulseaudio Date: Mon Mar 13 09:23:15 2017 DuplicateSignature: package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133 InstallationDate: Installed on 2011-10-11 (1979 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) MachineType: DIXONSXP DIXONSXP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago) dmi.bios.date: 04/12/2007 dmi.bios.vendor: DIXONSXP dmi.bios.version: 1.00.DIX dmi.board.name: DIXONSXP dmi.board.vendor: DIXONSXP dmi.chassis.type: 10 dmi.chassis.vendor: DIXONSXP dmi.modalias: dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr: dmi.product.name: DIXONSXP dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672318/+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 1671917] Re: perf probes on arm64 don't work with 4.10 kernel b/c of register name issue
This is a simple patch for perf and a clean cherry pick from upstream. I'm going ahead and applying it. ** Changed in: linux (Ubuntu Zesty) 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/1671917 Title: perf probes on arm64 don't work with 4.10 kernel b/c of register name issue Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: perf probe doesn't work because the register names in the perf tool are incorrect. This was fixed upstream by https://patchwork.kernel.org/patch/9534823/. perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes' Failed to write event: Invalid argument Error: Failed to add events. Rebuilding perf with the above mentioned change results in: ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes' Added new event: probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with bytes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671917/+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 1672224] Re: Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major chaos/failures
Does the bug go away if you boot back into the prior kernel version? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Tags added: kernel-da-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/1672224 Title: Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major chaos/failures Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The most obvious issue upon logging in was that there were no network interfaces save the loopback. A review of the logs suggested there were many major problems with the upgrade. Interestingly, the system suggested that I delete all other versions of the kernel immediately after this failed upgrade. This would have rendered the system nearly unusable. This is not the user experience I was thinking of when I chose an LTS version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 2348 F pulseaudio /dev/snd/controlC2: doug 2348 F pulseaudio /dev/snd/controlC0: doug 2348 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 12 15:23:41 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=caabec9a-7ba2-451a-91a5-af1bef3bfc38 InstallationDate: Installed on 2017-01-20 (51 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic root=UUID=ecd4d068-85e7-40c9-8483-d2dbfaadc20b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-63-generic N/A linux-backports-modules-4.4.0-63-generic N/A linux-firmware1.157.8 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0908 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LE PLUS 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.:bvr0908:bd12/10/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS: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/1672224/+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 1672502] [NEW] arm64 MSI/PCIe passthrough patches break build of certain configs
Public bug reported: The zesty kernel has a backport of the MSI/PCIe passthrough changes for arm64. This changeset introduced a bug that can cause a build failure with certain configurations. Though it doesn't impact the Ubuntu config, it could creep up again if we change our config. I reproduced it on Ubuntu source b building the s390x image with CONFIG_PCI=n and CONFIG_IRQ_DOMAIN=n. ** Affects: linux (Ubuntu) Importance: Low Assignee: dann frazier (dannf) Status: In Progress -- 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/1672502 Title: arm64 MSI/PCIe passthrough patches break build of certain configs Status in linux package in Ubuntu: In Progress Bug description: The zesty kernel has a backport of the MSI/PCIe passthrough changes for arm64. This changeset introduced a bug that can cause a build failure with certain configurations. Though it doesn't impact the Ubuntu config, it could creep up again if we change our config. I reproduced it on Ubuntu source b building the s390x image with CONFIG_PCI=n and CONFIG_IRQ_DOMAIN=n. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672502/+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 1672504] [NEW] pinctrl: qcom: add get_direction function
Public bug reported: On QDF2400 systems (ACPI-based), the kernel currently assumes all GPIOs from the qcom/pinctrl driver are configured for input. However, UEFI may have configured them for output. An upstream fix addresses this by adding a get_direction function: commit 8e51533780ba223a3562ff4382c6b6f350c7e9a4 Author: Timur Tabi Date: Fri Feb 10 17:21:00 2017 -0600 pinctrl: qcom: add get_direction function The get_direction callback function allows gpiolib to know the current direction (input vs output) for a given GPIO. This is particularly useful on ACPI systems, where the GPIOs are configured only by firmware (typically UEFI), so the only way to know the initial values to query the hardware directly. Without this function, gpiolib thinks that all GPIOs are configured for input. ** Affects: linux (Ubuntu) Importance: Medium Assignee: dann frazier (dannf) Status: In Progress -- 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/1672504 Title: pinctrl: qcom: add get_direction function Status in linux package in Ubuntu: In Progress Bug description: On QDF2400 systems (ACPI-based), the kernel currently assumes all GPIOs from the qcom/pinctrl driver are configured for input. However, UEFI may have configured them for output. An upstream fix addresses this by adding a get_direction function: commit 8e51533780ba223a3562ff4382c6b6f350c7e9a4 Author: Timur Tabi Date: Fri Feb 10 17:21:00 2017 -0600 pinctrl: qcom: add get_direction function The get_direction callback function allows gpiolib to know the current direction (input vs output) for a given GPIO. This is particularly useful on ACPI systems, where the GPIOs are configured only by firmware (typically UEFI), so the only way to know the initial values to query the hardware directly. Without this function, gpiolib thinks that all GPIOs are configured for input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672504/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
@Robert ... sure, let me clarify the events. 1. I had Ubuntu 16.04 LTS for some time already running on my system. 2. I bought AMD Ryzen 1800 + Gigabyte AB350 Gaming 3 and I took the SSD from the old system and pushed it into the new one 3. Everything worked fine, except I had to install NVIDIA drivers (I also bought a better video card) 4. I noticed I couldn`t get CPU temperature, so I tried my luck by upgrading to 16.10 (BAD DECISION) > during OS boot the IRQ VECTOR 07 error is repeated over and over 5. I then downloaded the 17.04 on a disk, and tried to install it > ended up with IRQ VECTOR 07 error during install (so, no go) 6. I tried the Ubuntu 16.04 LTS from a disk (which was the origin of the OS at step 1 ...) --> worked fine 7. I installed Ubuntu 16.04 LTS and here I am .. back at step 3 :) I`ve never installed STUDIO, only DESKTOP as in this : http://releases.ubuntu.com/16.04.2/ubuntu-16.04.2-desktop- amd64.iso?_ga=1.156896511.598999195.1489430754 -- 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
@Maciej : I think you missunderstood ... both Gigabyte (mine) and Asus boards (Huang`s) work fine with 16.04 LTS ... what you need to do .. is ask Huang to try his luck with 16.10 :) or 17.04 So, Huang, can you make 2 DVD`s .. one with 16.10 and another with 17.04 (or 2 bootable flashes) and just "TRY" both of them, without installing ... I wonder if that works for 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1672048] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1672048 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. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: saucy -- 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/1672048 Title: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7. Status in linux package in Ubuntu: Incomplete Bug description: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7. No touchpad entry is found in /proc/bus/input/devices, see attachment. Laptop model: Akoya E6240. Touchpad Model (as obtained after booting Windows8): Synaptics Click Pad ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672048/+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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
"on a disk" I mean on a DVD :) -- 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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1672048] Re: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1672048 Title: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7. Status in linux package in Ubuntu: Incomplete Bug description: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7. No touchpad entry is found in /proc/bus/input/devices, see attachment. Laptop model: Akoya E6240. Touchpad Model (as obtained after booting Windows8): Synaptics Click Pad ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672048/+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 1672486] [NEW] arm64: Workaround QDF2400 erratum 0065
Public bug reported: QDF2400 platforms require an erratum workaround to avoid a memory corruption issue. This was fixed upstream in the following commit: commit 90922a2d03d84de36bf8a9979d62580102f31a92 Author: Shanker Donthineni Date: Tue Mar 7 08:20:38 2017 -0600 irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065 On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt Translation Entry (ITE), but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size. It might cause kernel memory corruption depending on the number of MSI(x) that are configured and the amount of memory that has been allocated for ITEs in its_create_device(). This patch fixes the potential memory corruption by setting the correct ITE size to 16Bytes. ** Affects: linux (Ubuntu) Importance: High Assignee: dann frazier (dannf) Status: In Progress -- 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/1672486 Title: arm64: Workaround QDF2400 erratum 0065 Status in linux package in Ubuntu: In Progress Bug description: QDF2400 platforms require an erratum workaround to avoid a memory corruption issue. This was fixed upstream in the following commit: commit 90922a2d03d84de36bf8a9979d62580102f31a92 Author: Shanker Donthineni Date: Tue Mar 7 08:20:38 2017 -0600 irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065 On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt Translation Entry (ITE), but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size. It might cause kernel memory corruption depending on the number of MSI(x) that are configured and the amount of memory that has been allocated for ITEs in its_create_device(). This patch fixes the potential memory corruption by setting the correct ITE size to 16Bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672486/+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 1659111] Comment bridged from LTC Bugzilla
--- Comment From thiag...@br.ibm.com 2017-03-13 14:27 EDT--- Hello Canonical, Let me provide a status update: To fix this bug it's necessary to fix several issues with lifetime of structures in the block subsystem, as well as a number of related race conditions. A number of patches need to be backported to fix these problems: The "BDI lifetime fix" v3 series?, which was already merged into Linus' tree: f44f1ab5a2dc block: Unhash block device inodes on gendisk destruction dc3b17cc8bf2 block: Use pointer to backing_dev_info from request_queue d03f6cdc1fc4 block: Dynamically allocate and refcount backing_dev_info b1d2dc5659b4 block: Make blk_get_backing_dev_info() safe without open bdev efa7c9f97e3e block: Get rid of blk_get_backing_dev_info() A couple of follow up fixes were merged for commits dc3b17cc8bf and b1d2dc5659b4: e17354961bb5 zram_drv: update for backing dev info changes a5a79d00017c block: Initialize bd_bdi on inode initialization The first 4 patches from the "block: Fix block device shutdown related races" v2 series? were also merged: 4b8c861a7c79 block: Move bdev_unhash_inode() after invalidate_partition() d06e05c026ab block: Unhash also block device inode for the whole device cccd9fb9ec96 block: Revalidate i_bdev reference in bd_aquire() 165a5e22fafb block: Move bdi_unregister() to del_gendisk() A couple of follow up fixes were also merged for commit 165a5e22fafb: b6f8fec4448a block: Allow bdi re-registration df23de55615f bdi: Fix use-after-free in wb_congested_put() Commit df23de55615f depends on the following commit: 5f478e4ea5c5 block: fix double-free in the failure path of cgwb_bdi_init() In addition to the commits mentioned above, we will also need the patches from v4 of the same series, which was posted today: https://marc.info/?l=linux-block&m=148941806220331&w=2 I have a branch with the patches that were already merged upstream backported on top of tag Ubuntu-4.4.0-65.86. Most of the commits didn't have any conflicts, and the ones that did were simple to resolve. I will attach the backported patches to this bug report when all of the patches that we need are accepted upstream. -- ? https://marc.info/?l=linux-block&m=148604743126356&w=2 ? https://marc.info/?l=linux-block&m=148769705431982&w=2 -- 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/1659111 Title: UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic Status in linux package in Ubuntu: Incomplete Bug description: Attn. Canonical: For your awareness only at this time. == Comment: #0 - LEKSHMI C. PILLAI - 2016-11-22 03:49:38 == Machine INFO KVM HOST: luckyv1 Guest :lucky05 lucky05 crashed while running the I/O stress test for SAN disks. Installed lucky05 and enabled the xmon on that.After that started the RAW disk test on around 50 disks.After 6-7 hours after running,Now machine dropped into xmon. Logs: [25023.224182] Unable to handle kernel paging request for data at address 0x [25023.224257] Faulting instruction address: 0xc0324c60 cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620] pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290 lr: c032831c: writeback_sb_inodes+0x30c/0x590 sp: c000fffc38a0 msr: 80019033 dar: 0 dsisr: 4000 current = 0xc000ff99e470 paca= 0xcfb41c80 softe: 0irq_happened: 0x01 pid = 14736, comm = kworker/u16:8 enter ? for help [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> f 3:mon> th [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> sh [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks: [27384.651220] (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992) [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 (4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask
[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.
** 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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Confirmed Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 InstallationDate: Installed on 2016-12-23 (79 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: serena Uname: Linux 4.9.10-040910-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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 1672470] [NEW] ip_rcv_finish() NULL pointer kernel panic
Public bug reported: The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When the skb leaves the bridge, it removes the fake dst and places a real dst onto it. However, it uses a hook to do this, and when the br_netfilter module is unloading it unregisters that hook. Any skbs that are currently being processed in the bridge by the br_netfilter module, but that leave the bridge after the hook is unregistered (or, during br_netfilter module load, before the hook is registered) will still have the fake dst; when other code then tries to process that dst, it causes a kernel panic because the dst is invalid. Recent upstream discussion: https://www.spinics.net/lists/netdev/msg416912.html Upstream patch (not yet merged into net-next): https://patchwork.ozlabs.org/patch/738275/ example panic report: [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null) [ 214.612199] IP: [< (null)>] (null) [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca procmemro(O) nokeyctl(O) noptrace(O) [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1 [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.13a.0.0713160937 07/13/16 [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 8810392b [ 215.331207] RIP: 0010:[<>] [< (null)>] (null) [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286 [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: [ 215.569836] RDX: RSI: RDI: 881011067100 [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0 [ 215.740629] R10: R11: R12: 881018917dce [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078 [ 215.911432] FS: () GS:88103fec() knlGS: [ 216.008274] CS: 0010 DS: ES: CR0: 80050033 [ 216.077032] CR2: CR3: 001011b9d000 CR4: 001406e0 [ 216.162430] Stack: [ 216.186461] 8157d7f9 881011067100 881018917dce 88101163 [ 216.275407] 81c9be00 88103fec3918 8157e0db [ 216.364352] [ 216.453301] Call Trace: [ 216.482536] [ 216.505533] [] ? ip_rcv_finish+0x99/0x320 [ 216.575442] [] ip_rcv+0x25b/0x370 [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20 [ 216.712965] [] __netif_receive_skb+0x18/0x60 [ 216.783801] [] netif_receive_skb_internal+0x23/0x80 [ 216.861921] [] netif_receive_skb+0x1c/0x70 [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge] [ 217.016091] [] ? ___slab_alloc+0x1d0/0x440 [ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 [br_netfilter] [ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 [br_netfilter] [ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge] [ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 [br_netfilter] [ 217.437891] [] nf_iterate+0x5d/0x70 [ 217.499367] [] nf_hook_slow+0x64/0xc0 [ 217.562928] [] br_handle_frame+0x1b9/0x290 [bridge] [ 217.641048] [] ? br_handle_local_finish+0x80/0x80 [bridge] [ 217.726446] [] __netif_receive_skb_core+0x342/0xa20 [ 217.804566] [] ? tcp4_gro_receive+0x126/0x1d0 [ 217.876445] [] ? inet_gro_receive+0x1c6/0x250 [ 217.948322] [] __netif_receive_skb+0x18/0x60 [ 218.019161] [] netif_receive_skb_internal+0x23/0x80 [ 218.097281] [] napi_gro_receive+0xc3/0x110 [ 218.166051] [] ixgbe_clean_rx_irq+0x52f/0xa70 [ixgbe] [ 218.246255] [] ixgbe_poll+0x438/0x790 [ixgbe] [ 218.318131] [] net_rx_action+0x1ee/0x320 [ 218.384813] [] ? handle_irq_event_percpu+0x167/0x1d0 [ 218.463973] [] __do_softirq+0x101/0x280 [ 218.529608] [] irq_exit+0x8e/0x90 [ 218.589007] [] do_IRQ+0x54/0xd0 [ 218.646323] [] common_interrupt+0x82/0x82 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Tags: sts ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Tags added: sts -- 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/1672470 Title: ip_rcv_finish() NULL pointer kernel panic Status in linux package in Ubuntu: In Progress Bug description: The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When
[Kernel-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]
Could this be just a kernel issue? I had Flyme installed on my Pro 5 for a couple a days and I did not reflashed the whole system, just restored it with TWRP and yes, Android Flyme latest stable had suddenly an issue with a noise and distortion when using a Bluetooth. Then I realised that I have not reflashed it ,just restored it. Then I flashed the Flyme update and again restored the image with TWRP and problem with bluetooth has gone. So it might be a worth to look on kernel, files it contains and the configuration. -- 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/1590844 Title: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1672344] Re: 4.4.0-1008.17 - aws failed with kernel security test 152
Thanks for the report. Given that the kernel version is larger than
4.4.0-48, it should be skipping the line that resets the expected value
to 0; it looks like the version comparison is falling back to the string
version when handling the abi portion of the version (likely due to
python-apt not being installed), and because of *that*, it's treating
the ABI version of 1000+ as less than 48.
Realistically, the change in the setting as described in bug 1636461 should
have made it out to all of the 4.4 kernels we ship, so I've gone ahead and
removed that exception path from the test, committed in
https://git.launchpad.net/qa-regression-testing/commit/?id=d67eca192876d31892d50ecd410a2b658a8d871a
. Closing, please re-open if that doesn't address the issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: qa-regression-testing
Status: New => 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/1672344
Title:
4.4.0-1008.17 - aws failed with kernel security test 152
Status in QA Regression Testing:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
test_152_sysctl_disables_apparmor_unpriv_userns failed on
4.4.0-1008.17 - aws
This issue can't be found on 4.4.0-67.88 generic kernel for aws.
There was once a similar bug for this, please refer to bug 1636461
As the kernel version here is bigger than '4.4.0-46', the expected
return value is 0, but the test returned 1 instead.
FAIL: test_152_sysctl_disables_apparmor_unpriv_userns
(__main__.KernelSecurityTest)
unprivileged_userns_apparmor_policy sysctl supported
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1925, in
test_152_sysctl_disables_apparmor_unpriv_userns
self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy',
expected, exists=exists)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1182, in _test_sysctl_value
self.assertEqual(value, expected, report)
AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not
0: 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1672344/+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 1652185] Re: kernel BUG at /build/linux-7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120!
I confirm the same crash bug in Kernel versions: 4.4.0-66-generic 4.4.0-64-generic 4.4.0-21-generic I could not test with latest upstream kernel because I needed ZFS (I looked into building it for latest upstream, but found no reasonable path). I can also confirm the crash is related to a drive with bad sectors. In my case a Seagate 2TB ata-ST2000DM001-1ER164_Z4Z55RQ2 Once I removed that drive, the crashing stopped. If I booted with drive offline, and then added it to a booted system, it did not crash until I imported the ZFS pool. I can try some simple tests with DD to confirm the crash in later or earlier kernels. Since I do not want to break a now working system, any testing would be done booting a USB Flash image with only the failing drive connected to a sata_mv port. -- 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/1652185 Title: kernel BUG at /build/linux- 7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120! Status in linux package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-57-generic linux-image-4.4.0-57-generic: Installed: 4.4.0-57.78 Candidate: 4.4.0-57.78 Version table: *** 4.4.0-57.78 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464076] [ cut here ] Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464173] kernel BUG at /build/linux-7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120! Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464281] invalid opcode: [#1] SMP Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464355] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) gpio_ich ppdev i5000_edac edac_core parport_pc i5k_amb coretemp kvm parport irqbypass lpc_ich serio_raw input_leds 8250_fintek shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm pata_acpi e1000e ptp pps_core sata_mv floppy fjes Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466220] CPU: 0 PID: 198 Comm: scsi_eh_15 Tainted: P O4.4.0-57-generic #78-Ubuntu Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466355] Hardware name: Supermicro X7DB8/X7DB8, BIOS 6.00 12/03/2007 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466452] task: 880034c40cc0 ti: 880034c4c000 task.ti: 880034c4c000 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466564] RIP: 0010:[] [] mv_qc_prep+0x213/0x230 [sata_mv] Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466717] RSP: 0018:880034c4fa30 EFLAGS: 00010006 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466797] RAX: 8800353188c0 RBX: 8800352bdd70 RCX: 0047 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466893] RDX: 8800353188ca RSI: 88012a6af060 RDI: 8800352bdd70 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466993] RBP: 880034c4fa48 R08: R09: 0001 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467092] R10: 0020 R11: R12: 003f Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467191] R13: 880035083c18 R14: 0001 R15: 8800352bdd70 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467291] FS: () GS:88012fc0() knlGS: Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467412] CS: 0010 DS: ES: CR0: 8005003b Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467489] CR2: 7f284278bc00 CR3: cb676000 CR4: 06f0 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467588] Stack: Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467628] 8800352bc000 0001 8800352bde80 880034c4faa0 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467774] 815d9caa 88012a6af098 81e2c360 880034c4fb70 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467920] 000281d1863d 880034c4fbe0 8800352bde80 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] Call Trace: Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] [] ata_qc_issue+0x15a/0x390 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] [] ata_exec_internal_sg+0x302/0x600 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] [] ata_exec_internal+0x69/0xc0 Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] [] ? blk_peek_request+0x4b/0x290 Dec 22 1
[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.
apport information ** Tags added: apport-collected serena ** Description changed: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + CurrentDesktop: X-Cinnamon + DistroRelease: Linux 18.1 + InstallationDate: Installed on 2016-12-23 (79 days ago) + InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + Tags: serena + Uname: Linux 4.9.10-040910-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1672198/+attachment/4837090/+files/JournalErrors.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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Incomplete Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 InstallationDate: Installed on 2016-12-23 (79 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: serena Uname: Linux 4.9.10-040910-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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 1672198] Re: RTL8723b Kernel driver not loading on normal boot.
Because I do not have access to the machine running Ubuntu now i ran apport from my machine which is identical and has the identical problem with RTL8723 just it runs Linux Mint. As you can see I tried various Kernel up to 4.9 and the problem is the same with any kernel. -- 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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Incomplete Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 InstallationDate: Installed on 2016-12-23 (79 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: serena Uname: Linux 4.9.10-040910-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Let me know what other information I could supply. -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
~$ sudo i7z sudo i7z i7z DEBUG: i7z version: svn-r93-(27-MAY-2013) i7z DEBUG: Found Intel Processor i7z DEBUG:Stepping 9 i7z DEBUG:Model e i7z DEBUG:Family 6 i7z DEBUG:Processor Type 0 i7z DEBUG:Extended Model 9 i7z DEBUG: msr = Model Specific Register i7z DEBUG: Unknown processor, not exactly based on Nehalem, Sandy bridge or Ivy Bridge i7z DEBUG: msr device files exist /dev/cpu/*/msr i7z DEBUG: You have write permissions to msr device files -- --[core id]--- Other information - --[0] Processor number 0 --[0] Socket number/Hyperthreaded Sibling number 0,4 --[0] Core id number 0 --[0] Display core in i7z Tool: Yes --[1] Processor number 1 --[1] Socket number/Hyperthreaded Sibling number 0,5 --[1] Core id number 1 --[1] Display core in i7z Tool: Yes --[2] Processor number 2 --[2] Socket number/Hyperthreaded Sibling number 0,6 --[2] Core id number 2 --[2] Display core in i7z Tool: Yes --[3] Processor number 3 --[3] Socket number/Hyperthreaded Sibling number 0,7 --[3] Core id number 3 --[3] Display core in i7z Tool: Yes --[4] Processor number 4 --[4] Socket number/Hyperthreaded Sibling number 0,0 --[4] Core id number 0 --[4] Display core in i7z Tool: No --[5] Processor number 5 --[5] Socket number/Hyperthreaded Sibling number 0,1 --[5] Core id number 1 --[5] Display core in i7z Tool: No --[6] Processor number 6 --[6] Socket number/Hyperthreaded Sibling number 0,2 --[6] Core id number 2 --[6] Display core in i7z Tool: No --[7] Processor number 7 --[7] Socket number/Hyperthreaded Sibling number 0,3 --[7] Core id number 3 --[7] Display core in i7z Tool: No Socket-0 [num of cpus 4 physical 4 logical 8] 0,1,2,3, Socket-1 [num of cpus 0 physical 0 logical 0] GUI has been Turned ON i7z DEBUG: Single Socket Detected i7z DEBUG: In i7z Single_Socket() i7z DEBUG: guessing Nehalem AND THEN Cpu speed from cpuinfo 2903.00Mhz cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating via tsc Linux's inbuilt cpu_khz code emulated now True Frequency (without accounting Turbo) 2903 MHz CPU Multiplier 29x || Bus clock frequency (BCLK) 100.10 MHz Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4] TURBO ENABLED on 4 Cores, Hyper Threading ON Max Frequency without considering Turbo 3003.10 MHz (100.10 x [30]) Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is 39x/37x/36x/35x Real Current Frequency 1557.86 MHz [100.10 x 15.56] (Max of below) Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % Temp VCore Core 1 [0]: 1516.07 (15.15x) 2.8698.5 0 0 39 0.7573 Core 2 [1]: 1557.86 (15.56x) 2.1698.8 0 0 37 0.7573 Core 3 [2]: 1533.17 (15.32x) 2.1598.9 0 0 39 0.7550 Core 4 [3]: 1554.47 (15.53x) 1.5198.2 1 0 38 0.7552 C0 = Processor running without halting C1 = Processor running with halts (States >C0 are power saver modes with cores idling) C3 = Cores running with PLL turned off and core cache turned off C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper than C6 Above values in table are in percentage over the last 1 sec [core-id] refers to core-id number in /proc/cpuinfo 'Garbage Values' message printed when garbage values are read Ctrl+C to exit -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-
[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
Hi Colin,
As you indicated it seems that an actual allocation problem occurred on:
syscall table list zmalloc: Cannot allocate memory (in syscall_table_list() at
syscall.c:291)
>From the code:
/*
* Allocate at least the number of total syscall we have even if some of
* them might not be valid. The count below will make sure to return the
* right size of the events array.
*/
events = zmalloc(syscall_table_nb_entry * sizeof(*events));
if (!events) {
PERROR("syscall table list zmalloc");
ret = -LTTNG_ERR_NOMEM;
goto error;
}
syscall_table_nb_entry is assigned in syscall_init_table.
Could you link the full sessiond log and strace log? Also if possible
determine the value of syscall_table_nb_entry?
Cheers
--
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/1671063
Title:
ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
Status in linux package in Ubuntu:
In Progress
Bug description:
Two test cases failed on this arch:
== lttng smoke test list kernel events ==
PASSED (lttng list --kernel)
Error: Unable to list system calls: Not enough memory
Error: Command error
FAILED (lttng list --kernel --syscall)
FAILED (lttng list --kernel --syscall more output expected)
== lttng smoke test trace open/close system calls ==
...
FAILED (did not trace any open system calls)
Please find attachment for complete log.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-40-generic 4.8.0-40.43
ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
Uname: Linux 4.8.0-40-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Wed Mar 8 06:39:24 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.8.0-40-generic N/A
linux-backports-modules-4.8.0-40-generic N/A
linux-firmware1.161.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671063/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
~$ sudo turbostat cpu0: Guessing tjMax 100 C, Please use -T to specify CPU Avg_MHz Busy% Bzy_MHz TSC_MHz - 1006.6315002904 0 1097.2715002904 4 805.3315012904 1 1338.8514982904 5 936.2115012904 2 1167.7315002904 6 865.7315002904 3 1167.7015002904 7 644.2515002904 CPU Avg_MHz Busy% Bzy_MHz TSC_MHz - 158 10.5215012904 0 174 11.6015012904 4 1057.0215022904 1 178 11.8714992904 5 1288.5315012904 2 191 12.7115012904 6 1459.6515002904 3 205 13.6715012904 7 1379.1115022904 -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1670696] Re: Typo in error msg when no crashkernel memory reservation is set
For the record, I don't think this is worth SRU'ing to a stable release
unless it is bundled with other non-typo fixes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1670696
Title:
Typo in error msg when no crashkernel memory reservation is set
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Zesty:
In Progress
Status in makedumpfile package in Debian:
Unknown
Bug description:
[Impact]
* There is a typo in ERRMSG of function show_mem_usage affecting
Xenial/Zesty, Debian and makedumpfile upstream.
This should be :
"show_mem_usage: No memory is reserved for crashkernel!"
instead of :
"show_mem_usage: No memory is reserved for crashkenrel!"
The typo is located here in src code :
# filename : makedumpfile.c
-
int show_mem_usage(void)
{
uint64_t vmcoreinfo_addr, vmcoreinfo_len;
struct cycle cycle = {0};
if (!is_crashkernel_mem_reserved()) {
==> ERRMSG("No memory is reserved for crashkenrel!\n");
return FALSE;
}
-
[Test Case]
* Take a system with no crashkernel memory reservation set
* run command : makedumpfile --mem-usage /proc/kcore
* Error message :
show_mem_usage: No memory is reserved for crashkenrel!
[Regression Potential]
* No regression, it is a trivial change with no behavioural change.
[Other Info]
* Upstream:
Patch has been submitted upstream (ML :ke...@lists.infradead.org)
- AFAIK, there is no upstream bug database, so no URL available, ML only.
- Patch will be merge in upstream version 1.6.2 # See comment #4
* Debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Installed: intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd6 -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
~$ dmesg |grep idle [0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 7645519600211568 ns [0.00] clocksource: hpet: mask: 0x max_cycles: 0x, max_idle_ns: 79635855245 ns [0.044934] process: using mwait in idle threads [0.153005] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.162345] cpuidle: using governor ladder [0.178334] cpuidle: using governor menu [0.343661] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [0.899900] intel_idle: does not run on family 6 model 158 [0.901622] ACPI: acpi_idle registered with cpuidle [1.894828] clocksource: tsc: mask: 0x max_cycles: 0x29dc020bb13, max_idle_ns: 440795273180 ns -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
~$ sudo powertop (Idle Stats tab) Package | Core|CPU 0 CPU 4 POLL0.0%| POLL0.0%| POLL0.0%0.0 ms 0.0% 0.0 ms C1 0.8%| C1 0.3%| C1 0.3%0.2 ms 0.4% 0.6 ms C2 12.7%| C2 7.2%| C2 10.4%1.6 ms 4.0% 4.1 ms C3 81.7%| C3 89.4%| C3 84.6%6.6 ms 94.0% 8.9 ms | Core|CPU 1 CPU 5 | POLL0.0%| POLL0.0%0.0 ms 0.0% 0.0 ms | C1 1.7%| C1 3.3%0.9 ms 0.1% 0.2 ms | C2 15.7%| C2 26.0%1.8 ms 5.4% 2.0 ms | C3 74.0%| C3 65.5%4.0 ms 82.4% 25.2 ms | Core|CPU 2 CPU 6 | POLL0.0%| POLL0.0%0.0 ms 0.0% 0.0 ms | C1 0.7%| C1 1.1%0.2 ms 0.2% 0.2 ms | C2 15.0%| C2 17.2%2.3 ms 12.7% 1.1 ms | C3 81.0%| C3 78.7%5.4 ms 83.2% 7.9 ms | Core|CPU 3 CPU 7 | POLL0.0%| POLL0.0%0.0 ms 0.0% 0.0 ms | C1 0.4%| C1 0.8%0.2 ms 0.1% 0.1 ms | C2 12.6%| C2 23.6%1.3 ms 1.7% 1.6 ms | C3 81.8%| C3 69.1%4.7 ms 94.5% 9.4 ms -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
cat /sys/module/intel_idle/parameters/max_cstate ~$ cat /sys/module/intel_idle/parameters/max_cstate 9 -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1672439] [NEW] No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Public bug reported: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Confirmed Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1670696] Re: Typo in error msg when no crashkernel memory reservation is set
** Also affects: makedumpfile (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1670696
Title:
Typo in error msg when no crashkernel memory reservation is set
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Zesty:
In Progress
Status in makedumpfile package in Debian:
Unknown
Bug description:
[Impact]
* There is a typo in ERRMSG of function show_mem_usage affecting
Xenial/Zesty, Debian and makedumpfile upstream.
This should be :
"show_mem_usage: No memory is reserved for crashkernel!"
instead of :
"show_mem_usage: No memory is reserved for crashkenrel!"
The typo is located here in src code :
# filename : makedumpfile.c
-
int show_mem_usage(void)
{
uint64_t vmcoreinfo_addr, vmcoreinfo_len;
struct cycle cycle = {0};
if (!is_crashkernel_mem_reserved()) {
==> ERRMSG("No memory is reserved for crashkenrel!\n");
return FALSE;
}
-
[Test Case]
* Take a system with no crashkernel memory reservation set
* run command : makedumpfile --mem-usage /proc/kcore
* Error message :
show_mem_usage: No memory is reserved for crashkenrel!
[Regression Potential]
* No regression, it is a trivial change with no behavioural change.
[Other Info]
* Upstream:
Patch has been submitted upstream (ML :ke...@lists.infradead.org)
- AFAIK, there is no upstream bug database, so no URL available, ML only.
- Patch will be merge in upstream version 1.6.2 # See comment #4
* Debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+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 1671113] gonzo (i386) - tests ran: 7, failed: 0
tests ran: 7, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-13_14-59-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671113 Title: linux: 4.4.0-67.88 -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 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: New 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 4.4.0-67.88 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 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/1671113/+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 1670544] Re: [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel
Please include the stable release updates released this weekend (v4.10.2). The following Hyper-V commits were included: hyperv.h : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv: vmbus: Fix a rescind handling bug channel.c : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv: vmbus: Fix a rescind handling bug channel.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() channel_mgmt.c : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv: vmbus: Fix a rescind handling bug channel_mgmt.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() connection.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() hv.c : commit f791a7b4a7ae3a008a8af887b5a3f36ad1ac0574 : hv: don't reset hv_context.tsc_page on crash hv.c : commit aa2765857f7411a960778afc1ed34cb57dc43f08 : hv: allocate synic pages for all present CPUs hv.c : commit a34da99e9468a3990a8ca91bb9e502af61f95535 : hv: init percpu_list in hv_synic_alloc() hv.c : commit 6ffc4b85358f6b7d252420cfa5862312cf5f83d8 : hv: change clockevents unbind tactics hv_fcopy.c : commit 48dc52df9155443289f8bbf52f25a4214961ebee : Drivers: hv: util: Fcopy: Fix a rescind processing issue hv_kvp.c : commit f38bcff3986238898806512863b0e9d675de45ee : Drivers: hv: util: kvp: Fix a rescind processing issue hv_snapshot.c : commit 93919359467c6ce2f0f0ca4ad0f517b2d9bb03cf : Drivers: hv: util: Backup: Fix a rescind processing issue hyperv_vmbus.h : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() ring_buffer.c : commit 42b0681b7fe98556c1e4288e534368cc0bf607f9 : Drivers: hv: vmbus: Prevent sending data on a rescinded channel storvsc_drv.c : commit 99b3ba253c8b7bf8635fc68b5371a8225371f47c : scsi: storvsc: use tagged SRB requests if supported by the device storvsc_drv.c : commit e5fbe2328cc5c7211e4338b76f9004214b5bb663 : scsi: storvsc: properly set residual data length on errors storvsc_drv.c : commit 0aeb049529f3573dd35a549f846e5f623899d480 : scsi: storvsc: properly handle SRB_ERROR when sense message is present pci-hyperv.c : commit 91f5bce789d9083f1e24bc09b00c8c781c015835 : PCI: hv: Fix wslot_to_devfn() to fix warnings on device removal -- 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/1670544 Title: [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Bug description: Catching up with upstream 4.10 Hyper-V, files: arch/x86/kernel/cpu/mshyperv.c arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h include/linux/hyperv.h drivers/hv/channel.c drivers/hv/channel_mgmt.c drivers/hv/connection.c drivers/hv/hv_balloon.c drivers/hv/hv.c drivers/hv/hv_fcopy.c drivers/hv/hv_kvp.c drivers/hv/hv_snapshot.c drivers/hv/hv_util.c drivers/hv/hv_utils_transport.c drivers/hv/hv_utils_transport.h drivers/hv/hyperv_vmbus.h drivers/hv/ring_buffer.c drivers/hv/vmbus_drv.c tools/hv/hv_fcopy_daemon.c tools/hv/hv_get_dhcp_info.sh tools/hv/hv_get_dns_info.sh tools/hv/hv_kvp_daemon.c tools/hv/hv_set_ifconfig.sh tools/hv/hv_vss_daemon.c tools/hv/lsvmbus drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/hyperv_net.h drivers/net/hyperv/netvsc.c drivers/net/hyperv/netvsc_drv.c drivers/net/hyperv/rndis_filter.c drivers/scsi/storvsc_drv.c drivers/hid/hid-hyperv.c drivers/pci/host/pci-hyperv.c drivers/video/fbdev/hyperv_fb.c drivers/uio/uio_hv_generic.c Here is the delta from 4.9 to 4.10: mshyperv.c : commit a5a1d1c2914b5316924c7893eb683a5420ebd3be : clocksource: Use a plain u64 instead of cycle_t hyperv.h : commit 433e19cf33d34bb6751c874a9c00980552fe508c : Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read() hyperv.h : commit f45be72c8ec0b85263d1fe1e6c681d8c87e198e6 : hyperv: Fix spelling of HV_UNKOWN hyperv.h : commit fc76936d3ea5720a6e0948a08381b803a68deb28 : vmbus: add support for dynamic device id's hyperv.h : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: hv: vmbus: On write cleanup the logic to interrupt the host hyperv.h : commit fa32ff6576623616c1751562edaed8c164ca5199 : Drivers: hv: ring_buffer: count on wrap around mappings in get_next_pkt_raw() (v2) channel.c : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: hv: vmbus: On write cleanup the logic to interrupt the host channel.c : commit 3372592a140db69fd63837e81f048ab4abf8111e : Drivers: hv: vmbus:
[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang
I was experimenting similar behaviour using kernel 4.6.0 x86_64 (linux mint + cinnamon). After upgrading to 4.8.0-040800-generic x86_64 seems fine now. Regards Luis F. Heckler -- 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/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Fix Released Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+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 1672198] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1672198 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. ** Changed in: linux (Ubuntu) Status: New => 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/1672198 Title: RTL8723b Kernel driver not loading on normal boot. Status in linux package in Ubuntu: Incomplete Bug description: I use a very low and laptop with a built in rtl8723b wifi card. I always used the driver from lwfinger on github and that one worked well. But now Ubuntu comes with a driver for this card but that does not work on normal boot. Strange thing is this driver is initialised after resume from suspend. So i blacklisted the kernel module with: echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf and used the lwfinger driver from github again. So with rtl8xxu driver wifi card does not work on normal boot but does work when recovering from suspend to ram. Thank you. Bye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672198/+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
