[Kernel-packages] [Bug 1661741] Re: [Dell Inc. Latitude E5470] suspend/resume failure
So, I have a Dell Lattitude E7470 that had the very same problem. Running Linux Mint 18.1 with kernel linux-image-4.4.0-78-generic and BIOS 1.13.4 I installed kernel linux-image-4.11.0-041100-generic and still the problem is there. However, after I upgraded to BIOS 1.15.4, I can suspend well with 4.11 kernel but NOT with 4.4.0 (which works sometimes and sometimes it does not). Hope that helps. I ahve already suspended 5 times with the new BIOS and kernel 4.11 and all good. finger crossed. See we are talking about different models and BIOS, but Jonathan may be right that there is something nasty wrt BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661741 Title: [Dell Inc. Latitude E5470] suspend/resume failure Status in linux package in Ubuntu: Confirmed Bug description: To generate the crash: 1) Suspend the system (e.g. choose suspend from the top menu). 2) At any point, unplug the cord (the bug happens if I unplug at any point after suspend, even if I then replug before I resume) 3) Try to resume (pressing power button). Computer reboots. What should happen: Regular resume from suspend. (If I leave the computer plugged in, resume works fine.) I have performed the tests at https://wiki.ubuntu.com/DebuggingKernelSuspend and included the results. Note that the computer never crashes during any of the tests except when /sys/power/pm_test is 'none'. This appears the same/similar to #bug #1645758 but I dont't know how to add to the apport info to that bug instead of filing my own. ProblemType: KernelOops DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ganc 2892 F pulseaudio Date: Thu Dec 22 07:09:27 2016 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5470:1.11.4 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=a7e5c256-744c-41e6-823b-befb5f5c63f6 InstallationDate: Installed on 2017-01-31 (-39 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 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 0bda:5686 Realtek Semiconductor Corp. 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. Latitude E5470 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=1eb743a3-00e0-430e-be35-9748390e53f3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux Title: [Dell Inc. Latitude E5470] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.4:bd12/22/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661741/+subscriptions -- Mailing list: https://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 1695175] [NEW] My Touchpad Not Working
Public bug reported: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. UpgradeStatus: No upgrade log present (probably fresh install) https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695177 ** Affects: linux-lts-vivid (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/1695175 Title: My Touchpad Not Working Status in linux-lts-vivid package in Ubuntu: New Bug description: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. UpgradeStatus: No upgrade log present (probably fresh install) https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695177 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695175/+subscriptions -- Mailing list: https://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 1695175] Re: My Touchpad Not Working
When putting the command `sudo lspci -vnvn > lspci-vnvn.log` It gives another error `pcilib: sysfs_read_vpd: read failed: Connection timed out` ** Package changed: linux (Ubuntu) => linux-lts-vivid (Ubuntu) ** Description changed: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. + + + problemType: Bug + DistroRelease: Ubuntu 14.04 + Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: boot/vmlinuz-3.19.0-25-generic] + ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 + Uname: Linux 3.19.0-25-generic x86_64 + ApportVersion: 2.14.1-0ubuntu3.23 + Architecture: amd64 + CurrentDesktop: Unity + Date: Fri Jun 2 11:59:56 2017 + InstallationDate: Installed on 2017-04-15 (47 days ago) + InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + SourcePackage: linux-lts-vivid + UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. - - problemType: Bug - DistroRelease: Ubuntu 14.04 - Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: boot/vmlinuz-3.19.0-25-generic] - ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 - Uname: Linux 3.19.0-25-generic x86_64 - ApportVersion: 2.14.1-0ubuntu3.23 - Architecture: amd64 - CurrentDesktop: Unity - Date: Fri Jun 2 11:59:56 2017 - InstallationDate: Installed on 2017-04-15 (47 days ago) - InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) - SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. UpgradeStatus: No upgrade log present (probably fresh install) + + https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695177 -- 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/1695175 Title: My Touchpad Not Working Status in linux-lts-vivid package in Ubuntu: New Bug description: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. UpgradeStatus: No upgrade log present (probably fresh install) https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695177 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695175/+subscriptions -- Mailing list: https://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 1695177] [NEW] touchpad not working, ubunt hangs after sometime on playing videos and using heavy software like netbeans, eclipse, etc
Public bug reported: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: boot/vmlinuz-3.19.0-25-generic] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 2 11:59:56 2017 InstallationDate: Installed on 2017-04-15 (47 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1695177 Title: touchpad not working, ubunt hangs after sometime on playing videos and using heavy software like netbeans, eclipse, etc Status in linux-lts-vivid package in Ubuntu: New Bug description: My Touchpad Not Working and Ubuntu get hang after sometime if i play videos on firefox or vlc media player. I am using Asus X541U Laptop. I came across different site and tried different approaches. putting `xinput` in my terminal doesn't show any bus for touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: boot/vmlinuz-3.19.0-25-generic] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 2 11:59:56 2017 InstallationDate: Installed on 2017-04-15 (47 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1695177/+subscriptions -- Mailing list: https://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 1688081] Re: USb-Ethernet ASIX A88772 stops working after kernel 4.10
Okay, let's do a bisection. Please try Linux 4.9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.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/1688081 Title: USb-Ethernet ASIX A88772 stops working after kernel 4.10 Status in linux package in Ubuntu: Confirmed Bug description: I have an USB-Ethernet dongle ASIX AX88772 USB 2.0 Ethernet, which uses the asix.ko module. I just updated from Ubuntu 16.04 to 16.10 then 17.04. When I updated to 17.04 it just stopped initializing the dongle; in ethtool and mii-tool it shows no link detected, although it is connected and works in dual-booted Windows. I ruled out networkmanager idiosyncrasies of "managed" and "not managed" because I configured it both ways and tried also with ifupdown and directly with ifconfig up and dhclient. And then I changed the model to another ethernet USB adapter and it worked. This is the dmesg entry for the ASIX adapter: [ 31.137223] usb 1-6: New USB device found, idVendor=0b95, idProduct=772a [ 31.137225] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.137226] usb 1-6: Product: AX88x72A [ 31.137227] usb 1-6: Manufacturer: ASIX Elec. Corp. [ 31.137228] usb 1-6: SerialNumber: 02 Model no: KY-AX88772ALF on the side of the device. I am currently reporting this bug without the adapter connected, because I would have no network. So if you need additional data from it just say what you need, I am using Ubuntu 17.04 64 bits. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USUÁRIO PID ACESSO COMANDO /dev/snd/controlC0: patola20818 F pulseaudio /dev/snd/controlC1: patola20818 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=43970c80-83be-4fe7-95d3-ff85da5efe72 InstallationDate: Installed on 2012-11-16 (1629 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: enx00e04d680249 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/raizvg-rootlv ro quiet splash crashkernel=384M-:128M ehci_hcd.ignore_OC=1 usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-05-03 (0 days ago) UserGroups: adm autopilot cdrom daemon dialout dip disk input lpadmin plugdev sambashare sudo tty _MarkForUpload: True dmi.bios.date: 06/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/12/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688081/+subscriptions -- Mailing list: https://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 1678590] Re: Dell Inspiron on kernel 4.10 : battery detected only after AC power adapter event
** Description changed: + [Impact] + Battery events does not work on Dell Inspiron 7537. + + [Test Case] + Boot the machine, no battery detected. + Add a quirk for Inspiron 7537 can make battery detection work. + + [Regression Potential] + None. It only applies to one specific laptop, Dell Inspiron 7537. + Hi, I already reported the bug here: http://www.spinics.net/lists/linux-acpi/msg73101.html When I boot a Dell 15" serie 7000 with or without it AC power adapter no battery is detected: acpi -i -b -a Adapter 0: off-line As soon as I plug or unplug the AC adapter, the battery is detected: acpi -i -b -a Battery 0: Charging, 62%, 01:13:00 until charged Battery 0: design capacity 3950 mAh, last full capacity 3850 mAh = 97% Adapter 0: on-line cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic root=UUID=42930a1e-fbdc- 4cd8-a1d2-caf2bd33de1b ro acpi_osi=Linux quiet splash vt.handoff=7 - I've tried with and without acpi_osi=Linux but it makes no difference. Attached : dmesg and dsdt in http://www.spinics.net/lists/linux-acpi/msg73101.html I think that acpi_osi=Linux used to do the trick but it does not work on vmlinuz-4.10.0-13-generic Xavier - --- + --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0p: xavier 1473 F...m pulseaudio - /dev/snd/controlC1: xavier 1473 F pulseaudio - /dev/snd/controlC0: xavier 1473 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: xavier 1473 F...m pulseaudio + /dev/snd/controlC1: xavier 1473 F pulseaudio + /dev/snd/controlC0: xavier 1473 F pulseaudio DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=31a2d0a3-34b9-467d-8c4d-f226cc825604 InstallationDate: Installed on 2017-03-28 (5 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic root=UUID=42930a1e-fbdc-4cd8-a1d2-caf2bd33de1b ro acpi_osi=Linux quiet splash ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 RelatedPackageVersions: - linux-restricted-modules-4.10.0-13-generic N/A - linux-backports-modules-4.10.0-13-generic N/A - linux-firmware 1.164 + linux-restricted-modules-4.10.0-13-generic N/A + linux-backports-modules-4.10.0-13-generic N/A + linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/04/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 03HR9V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd10/04/2016:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn03HR9V:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. -- 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/1678590 Title: Dell Inspiron on kernel 4.10 : battery detected only after AC power adapter event Status in linux package in Ubuntu: In Progress Bug description: [Impact] Battery events does not work on Dell Inspiron 7537. [Test Case] Boot the machine, no battery detected. Add a quirk for Inspiron 7537 can make battery detection work. [Regression Potential] None. It only applies to one specific laptop, Dell Inspiron 7537. Hi, I already reported the bug here: http://www.spinics.net/lists/linux-acpi/msg73101.html When I boot a Dell 15" serie 7000 with or without it AC power adapter no battery is detected: acpi -i -b -a Adapter 0: off-line As soon as I plug or unplug the AC adapter, the battery is detected: acpi -i -b -a Battery 0: Charging, 62%, 01:13:00 until charged Battery 0: design capacity 3950 mAh, last full capacity 3850 mAh = 97% Adapter 0: on-line cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic root=UUID=42930a1e-fbdc- 4cd8-a1d2-caf2bd33de1b ro acpi_osi=Linux quiet splash vt.handoff=7 I've tried with and without acpi_osi=Linux but it makes no difference. Attached : dmesg and dsdt in http://www.spinics.net/lists/linux-acpi/msg73101.html I think that acpi_osi=Linux used to do the trick but it does not work on vmlinuz-4.10.0-13-generic Xavier --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: xavier 1473 F...m pulseaudio /dev/snd/controlC1: xavier 1473 F p
[Kernel-packages] [Bug 1686592] Re: APST quirk needed for Intel NVMe
** Description changed: + [Impact] + Intel NVMe failed to work after some disk I/O. + + [Test Case] + Use the system for a while. Any disk I/O may make Intel NVMe failed to operate. + + [Regression Potential] + None. It only applies to limited Intel NVMe devices. + Two users reports issue on Intel NVMe [1] (comment #34, #35). File a new bug to let the original bug report stays on Dell & Samsung combination. [1] https://bugs.launchpad.net/bugs/1678184 -- 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/1686592 Title: APST quirk needed for Intel NVMe Status in linux package in Ubuntu: Triaged Bug description: [Impact] Intel NVMe failed to work after some disk I/O. [Test Case] Use the system for a while. Any disk I/O may make Intel NVMe failed to operate. [Regression Potential] None. It only applies to limited Intel NVMe devices. Two users reports issue on Intel NVMe [1] (comment #34, #35). File a new bug to let the original bug report stays on Dell & Samsung combination. [1] https://bugs.launchpad.net/bugs/1678184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.
As suggested by kai.heng.feng, I installed the 4.12.0-041200rc2 kernel. If I connect my WD My Passport drive into an Plugable 7-port, external USB 3.0 hub, it is not recognized. 'sudo lsusb -v' causes the drive to be recognized and I can mount it. If I disconnect the drive, wait a few seconds, and connect it back to the same port in the external USB 3.0 hub, it is not recognized. If I connect the WD My Passport drive to a MOTHERBOARD USB 3.0 port, it is recognized and I can mount it. Disconnecting and reconnecting the drive to a MOTHERBOARD USB 3.0 port, it is again recognized. The difference is using the external USB 3.0 hub port or the motherboard USB 3.0 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/1693842 Title: USB 3.0 Disk Drive Not Recognized. Status in linux package in Ubuntu: Confirmed Bug description: WD My Passport 2T USB 3.0 Disk Drive. External Plugable 7 port USB 3.0 hub. When I connect the WD drive to the external USB 3.0 hub it is not recognized. The drive led blinks one time and it is not in dmesg or in the output of lsusb. > sudo lsusb -v causes the drive led to blink several times and it is recognized. With Autosuspend good for this device, long access applications like dump fail. After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes and then dump asks for operator intervention. Looking at dmesg the drive (initially sdf) was disconnected and reconnected as sdg. Bad Autosuspend for USB device xHCI Host Controller [usb6] seems to correct this behavior but not the initial connection problem. Some discussion and testing in bug 1242321. If I connect the drive to a USB 3.0 port on the motherboard, it is recognized. There is no problem with an Plugable 7-port USB 2.0 hub. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tomdean3698 F pulseaudio /dev/snd/controlC0: tomdean3698 F pulseaudio Date: Fri May 26 09:05:20 2017 HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a InstallationDate: Installed on 2016-05-15 (375 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.8 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693842/+subscriptions -- Mailing list: https://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 1686592] Re: APST quirk needed for Intel NVMe
Hmm, does 2.2.1 help? -- 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/1686592 Title: APST quirk needed for Intel NVMe Status in linux package in Ubuntu: Triaged Bug description: Two users reports issue on Intel NVMe [1] (comment #34, #35). File a new bug to let the original bug report stays on Dell & Samsung combination. [1] https://bugs.launchpad.net/bugs/1678184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686592/+subscriptions -- Mailing list: https://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 1694596] Re: LiteOn NVMe issue
** Summary changed: - LiteOn NVMe APST issue + LiteOn NVMe issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694596 Title: LiteOn NVMe issue Status in linux package in Ubuntu: Confirmed Bug description: Originally reported at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/79 The user uses "nvme_core.default_ps_max_latency_us=6000" but the issue still happens. $ sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x14a4 ssvid : 0x1b4b sn : TW0XVRV7LOH006AJ09F1 mn : CX2-8B256-Q11 NVMe LITEON 256GB fr : 48811QD rab : 0 ieee : 002303 cmic : 0 mdts : 5 cntlid : 1 ver : 10200 rtd3r : f4240 rtd3e : f4240 oaes : 0 oacs : 0x1f acl : 3 aerl : 3 frmw : 0x14 lpa : 0x2 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 358 cctemp : 368 mtfa : 50 hmpre : 0 hmmin : 0 tnvmcap : 256060514304 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0 vwc : 0x1 awun : 255 awupf : 7 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:4.00W operational enlat:5 exlat:5 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:2.10W operational enlat:5 exlat:5 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.1000W non-operational enlat:5000 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0100W non-operational enlat:5 exlat:10 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- Mailing list: https://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 1694186] Re: Touchpad / TrackPoint no longer work in Lubuntu 17.04
My educated guess is that it works on linux kernel 4.4, correct? Use this kernel to verify: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.70/linux-image-4.4.70-040470-generic_4.4.70-040470.201705251131_amd64.deb -- 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/1694186 Title: Touchpad / TrackPoint no longer work in Lubuntu 17.04 Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad and TrackPoint on my Lenovo R61i worked great for years with various flavors of Ubuntu and Lubuntu. Stopped working intermittently for a couple of days, now doesn't work at all. An attached USB mouse works fine. I ran cat /proc/bus/input/devices and do not see my Synaptics touchpad listed. --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1227 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=c2cce062-dc9d-400e-aff2-013d3d44aa9a InstallationDate: Installed on 2017-01-11 (138 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 8932A17 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=1e5e0659-a832-4cfe-a4f9-1b35878aacc5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (39 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7OETC4WW (2.24 ) dmi.board.name: 8932A17 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:bvr7OETC4WW(2.24):bd04/09/2010:svnLENOVO:pn8932A17:pvrThinkPadR61:rvnLENOVO:rn8932A17:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8932A17 dmi.product.version: ThinkPad R61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694186/+subscriptions -- Mailing list: https://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 Gigabyte AM4 motherboards (AMD Ryzen)
I remember someone mentioned there's no such issue on 4.4 kernel? Anyway, you can use Zesty's kernel in Xenial. Install package "linux-generic-hwe-16.04-edge" will do. -- 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 Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found. Original bug report: 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/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 1693618] Re: Microcode SW error detected.
Take a look at LP: #1694547. Probably same issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1693618 Title: Microcode SW error detected. Status in linux-firmware package in Ubuntu: Incomplete Bug description: In dmesg logs I see [81251.363118] iwlwifi :04:00.0: regular scan timed out [81251.363235] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. [81251.363241] iwlwifi :04:00.0: CSR values: [81251.363244] iwlwifi :04:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [81251.363250] iwlwifi :04:00.0:CSR_HW_IF_CONFIG_REG: 0X00c89008 [81251.363256] iwlwifi :04:00.0: CSR_INT_COALESCING: 0X0040 [81251.363261] iwlwifi :04:00.0: CSR_INT: 0X [81251.363266] iwlwifi :04:00.0:CSR_INT_MASK: 0X [81251.363271] iwlwifi :04:00.0: CSR_FH_INT_STATUS: 0X [81251.363276] iwlwifi :04:00.0: CSR_GPIO_IN: 0X0019 [81251.363281] iwlwifi :04:00.0: CSR_RESET: 0X [81251.363286] iwlwifi :04:00.0:CSR_GP_CNTRL: 0X08040005 [81251.363292] iwlwifi :04:00.0: CSR_HW_REV: 0X0201 [81251.363296] iwlwifi :04:00.0: CSR_EEPROM_REG: 0Xd5d5 [81251.363302] iwlwifi :04:00.0: CSR_EEPROM_GP: 0Xd5d5 [81251.363306] iwlwifi :04:00.0: CSR_OTP_GP_REG: 0Xd5d5 [81251.363311] iwlwifi :04:00.0: CSR_GIO_REG: 0X001f0044 [81251.363316] iwlwifi :04:00.0:CSR_GP_UCODE_REG: 0X [81251.363321] iwlwifi :04:00.0: CSR_GP_DRIVER_REG: 0X [81251.363326] iwlwifi :04:00.0: CSR_UCODE_DRV_GP1: 0X [81251.363331] iwlwifi :04:00.0: CSR_UCODE_DRV_GP2: 0X [81251.363336] iwlwifi :04:00.0: CSR_LED_REG: 0X0060 [81251.363341] iwlwifi :04:00.0:CSR_DRAM_INT_TBL_REG: 0X8884993d [81251.363346] iwlwifi :04:00.0:CSR_GIO_CHICKEN_BITS: 0X07800200 [81251.363351] iwlwifi :04:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 [81251.363356] iwlwifi :04:00.0: CSR_MONITOR_STATUS_REG: 0Xc03803c0 [81251.363361] iwlwifi :04:00.0: CSR_HW_REV_WA_REG: 0X0001001a [81251.363366] iwlwifi :04:00.0:CSR_DBG_HPET_MEM_REG: 0X0010 [81251.363369] iwlwifi :04:00.0: FH register values: [81251.363384] iwlwifi :04:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X848c7800 [81251.363398] iwlwifi :04:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0848c080 [81251.363413] iwlwifi :04:00.0: FH_RSCSR_CHNL0_WPTR: 0X00f0 [81251.363427] iwlwifi :04:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801054 [81251.363442] iwlwifi :04:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [81251.363456] iwlwifi :04:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0303 [81251.363471] iwlwifi :04:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [81251.363486] iwlwifi :04:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff [81251.363500] iwlwifi :04:00.0: FH_TSSR_TX_ERROR_REG: 0X [81251.363612] iwlwifi :04:00.0: Start IWL Error Log Dump: [81251.363615] iwlwifi :04:00.0: Status: 0x, count: 6 [81251.363618] iwlwifi :04:00.0: Loaded firmware version: 21.302800.0 [81251.363622] iwlwifi :04:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [81251.363624] iwlwifi :04:00.0: 0x06F4 | trm_hw_status0 [81251.363627] iwlwifi :04:00.0: 0x | trm_hw_status1 [81251.363630] iwlwifi :04:00.0: 0x0BD8 | branchlink2 [81251.363632] iwlwifi :04:00.0: 0x00026AC4 | interruptlink1 [81251.363635] iwlwifi :04:00.0: 0x00026AC4 | interruptlink2 [81251.363637] iwlwifi :04:00.0: 0x | data1 [81251.363640] iwlwifi :04:00.0: 0x0080 | data2 [81251.363642] iwlwifi :04:00.0: 0x0783 | data3 [81251.363645] iwlwifi :04:00.0: 0x7800010C | beacon time [81251.363647] iwlwifi :04:00.0: 0xF129DEEA | tsf low [81251.363650] iwlwifi :04:00.0: 0x0077 | tsf hi [81251.363653] iwlwifi :04:00.0: 0x | time gp1 [81251.363655] iwlwifi :04:00.0: 0xEA60BCC9 | time gp2 [81251.363658] iwlwifi :04:00.0: 0x | uCode revision type [81251.363660] iwlwifi :04:00.0: 0x0015 | uCode version major [81251.363663] iwlwifi :04:00.0: 0x00049ED0 | uCode version minor [81251.363665] iwlwifi :04:00.0: 0x0201 | hw version [81251.363668] iwlwifi :04:00.0: 0x00C89008 | board version [81251.363671] iwlwifi :04:00.0: 0x09270400 | hcmd [81251.363673] iwlwifi :04:00.0: 0x80022000 | isr0 [81251.363676] iwlwifi 0
[Kernel-packages] [Bug 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]
Thanks iMac (imac-netstatz). I just installed the drivers from the github repo on 17.04 and it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1595765 Title: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Status in rtl8812au package in Ubuntu: Confirmed Bug description: error update for kernel 4.7 RC 3 ProblemType: Package DistroRelease: elementary 0.4 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu] Uname: Linux 4.6.2-040602-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.7.0-040700rc3-generic Date: Thu Jun 23 22:03:59 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function) InstallationDate: Installed on 2016-06-14 (9 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613) PackageVersion: 6.30.223.248+bdcom-0ubuntu8 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+subscriptions -- Mailing list: https://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 1661741] Re: [Dell Inc. Latitude E5470] suspend/resume failure
I will try when I get a chance but I am busy for at least a few days and this is my main computer so I can't afford to muck around with it too carelessly. -- 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/1661741 Title: [Dell Inc. Latitude E5470] suspend/resume failure Status in linux package in Ubuntu: Confirmed Bug description: To generate the crash: 1) Suspend the system (e.g. choose suspend from the top menu). 2) At any point, unplug the cord (the bug happens if I unplug at any point after suspend, even if I then replug before I resume) 3) Try to resume (pressing power button). Computer reboots. What should happen: Regular resume from suspend. (If I leave the computer plugged in, resume works fine.) I have performed the tests at https://wiki.ubuntu.com/DebuggingKernelSuspend and included the results. Note that the computer never crashes during any of the tests except when /sys/power/pm_test is 'none'. This appears the same/similar to #bug #1645758 but I dont't know how to add to the apport info to that bug instead of filing my own. ProblemType: KernelOops DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ganc 2892 F pulseaudio Date: Thu Dec 22 07:09:27 2016 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5470:1.11.4 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=a7e5c256-744c-41e6-823b-befb5f5c63f6 InstallationDate: Installed on 2017-01-31 (-39 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 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 0bda:5686 Realtek Semiconductor Corp. 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. Latitude E5470 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=1eb743a3-00e0-430e-be35-9748390e53f3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux Title: [Dell Inc. Latitude E5470] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.4:bd12/22/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661741/+subscriptions -- Mailing list: https://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 1695079] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1690013 *** https://bugs.launchpad.net/bugs/1690013 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1690013, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1690013 bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk ** Information type changed from Private to Public -- 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/1695079 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() Status in bluez package in Ubuntu: New Bug description: found this pending crash report after login ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24~16.04.1-lowlatency 4.10.15 Uname: Linux 4.10.0-22-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 1 21:16:46 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd ExecutableTimestamp: 1456846426 InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-lowlatency root=/dev/mapper/vgcrypt0-root ro ip=192.168.33.4::192.168.33.253 quiet nvidia_drm.modeset=1 crashkernel=384M-:128M irqpoll RetraceOutdatedPackages: no debug symbol package found for liblzma5 Signal: 11 SourcePackage: bluez StacktraceTop: malloc_consolidate (av=av@entry=0x7f558b1c6b20 ) at malloc.c:4167 _int_malloc (av=av@entry=0x7f558b1c6b20 , bytes=bytes@entry=8192) at malloc.c:3448 __libc_calloc (n=, elem_size=) at malloc.c:3234 __GI___open_memstream (bufloc=bufloc@entry=0x7ffc798b0bb0, sizeloc=sizeloc@entry=0x7ffc798b0bb8) at memstream.c:83 __GI___vsyslog_chk (pri=30, pri@entry=6, flag=flag@entry=1, fmt=fmt@entry=0x5560910fd518 "Endpoint unregistered: sender=%s path=%s", ap=ap@entry=0x7ffc798b0c80) at ../misc/syslog.c:167 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78T-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:19:15:4E:47:D7 ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN RX bytes:3488668 acl:62 sco:68335 events:93 errors:0 TX bytes:1625 acl:56 sco:0 commands:59 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1695079/+subscriptions -- Mailing list: https://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 Gigabyte AM4 motherboards (AMD Ryzen)
Will the fix get backported or become available on Xenial? (16.04) -- 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 Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found. Original bug report: 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/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 Gigabyte AM4 motherboards (AMD Ryzen)
Yay! -- 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 Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found. Original bug report: 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/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 1695100] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1695100 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/1695100 Title: Package changes for linux-joule Status in linux package in Ubuntu: Incomplete Bug description: Small package changes for linux-joule as suggested by Andy. Update copyright, fix Vcs-Git and packages descriptions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695100/+subscriptions -- Mailing list: https://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 1695100] [NEW] Package changes for linux-joule
Public bug reported: Small package changes for linux-joule as suggested by Andy. Update copyright, fix Vcs-Git and packages descriptions. ** 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/1695100 Title: Package changes for linux-joule Status in linux package in Ubuntu: New Bug description: Small package changes for linux-joule as suggested by Andy. Update copyright, fix Vcs-Git and packages descriptions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695100/+subscriptions -- Mailing list: https://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 1695093] Re: arm64: unsupported RELA relocation: 275 loading libceph module
This also impacts the scsi_debug module. Test Case: find /lib/modules/$(uname -r) -type f -name '*.ko' | while read mod; do if readelf -r $mod | grep -q 00010113; then echo $mod; fi; done For hwe-x, this matches scsi_debug. For hwe-y & hwe-z, it matches scsi_debug and libceph. ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Zesty) Status: New => Confirmed ** Summary changed: - arm64: unsupported RELA relocation: 275 loading libceph module + arm64: "unsupported RELA relocation: 275" loading certain modules -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695093 Title: arm64: "unsupported RELA relocation: 275" loading certain modules Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: Confirmed Bug description: With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695093/+subscriptions -- Mailing list: https://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 1695093] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1695093 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/1695093 Title: arm64: unsupported RELA relocation: 275 loading libceph module Status in linux package in Ubuntu: Incomplete Bug description: With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695093/+subscriptions -- Mailing list: https://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 1695093] [NEW] arm64: unsupported RELA relocation: 275 loading libceph module
Public bug reported: With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. ** 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/1695093 Title: arm64: unsupported RELA relocation: 275 loading libceph module Status in linux package in Ubuntu: New Bug description: With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695093/+subscriptions -- Mailing list: https://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 1694186] Re: Touchpad / TrackPoint no longer work in Lubuntu 17.04
OK, spoke too soon. After the last reboot, Trackpad and TouchPoint no longer work. I did manage to get into the GRUB Menu and start the v4.12 kernel, but I couldn't get it to boot. 4.12 recovery doesn't work either. Back to square one. The intermittent nature is making me suspect a hardware 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/1694186 Title: Touchpad / TrackPoint no longer work in Lubuntu 17.04 Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad and TrackPoint on my Lenovo R61i worked great for years with various flavors of Ubuntu and Lubuntu. Stopped working intermittently for a couple of days, now doesn't work at all. An attached USB mouse works fine. I ran cat /proc/bus/input/devices and do not see my Synaptics touchpad listed. --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1227 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=c2cce062-dc9d-400e-aff2-013d3d44aa9a InstallationDate: Installed on 2017-01-11 (138 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 8932A17 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=1e5e0659-a832-4cfe-a4f9-1b35878aacc5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (39 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7OETC4WW (2.24 ) dmi.board.name: 8932A17 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:bvr7OETC4WW(2.24):bd04/09/2010:svnLENOVO:pn8932A17:pvrThinkPadR61:rvnLENOVO:rn8932A17:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8932A17 dmi.product.version: ThinkPad R61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694186/+subscriptions -- Mailing list: https://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 1689980] Re: AACRAID for power9 platform
Diffstat from the requested backports: drivers/scsi/aacraid/aachba.c | 17 +++--- drivers/scsi/aacraid/aacraid.h | 22 ++-- drivers/scsi/aacraid/commctrl.c | 15 +++--- drivers/scsi/aacraid/comminit.c | 18 ++- drivers/scsi/aacraid/commsup.c | 78 +-- drivers/scsi/aacraid/linit.c| 232 --- drivers/scsi/aacraid/src.c | 136 +++--- 7 files changed, 298 insertions(+), 220 deletions(-) So that's fairly substantial. I skimmed the patches and most of them look pretty safe, just a handful that are somewhat concerning. It's likely we can take these if/when the backport has been thoroughly tested. Is this hardware commonly used on platforms other than Power 9? If so it would be good to see some testing on those platforms, if possible. -- 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/1689980 Title: AACRAID for power9 platform Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: Hello team, It seems Microsemi team has requested to backport few AACRAID driver patches for Power 9 platform for 17.04 and 16.04.3 kernel. Hi Narinder, We have submitted a handful of critical fixes for the AACRAID driver on to the kernel.org, targeting 4.11. These patches are bug fixes and our customer IBM is expecting these patches to go into the 16.04.3 release, for to use with the Power9 platforms. Can you please let me know if these patches will be backported by your kernel team on to the upcoming 16.04.3? Do you also have a schedule in place for 16.04.3 release? Thanks, Gana Below are the patch details. Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc fixes This patchset primarily focuses on tweaking and hardening the controller reset support for both ARC and HBA1000 devices. Now the driver can only reset the controller thru eh reset. Included a srb memory fix and pci dma allocation fix. Changes in V2: - Corrected heading and description for srb memory patch and removed stray comment. - Removed incorrect up function call and cleared fib wait flag after call to down interruptible in the ioctl return on ctrl reset patch. - Added review acknowledgements by David Carroll thank you Dave for finding the above issues in the above 2 patches. Raghava Aditya Renukunta (19): [SCSI] aacraid: Remove __GFP_DMA for raw srb memory [SCSI] aacraid: Fix DMAR issues with iommu=pt [SCSI] aacraid: Added 32 and 64 queue depth for arc natives [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks [SCSI] aacraid: Remove reset support from check_health [SCSI] aacraid: Change wait time for fib completion [SCSI] aacraid: Log count info of scsi cmds before reset [SCSI] aacraid: Print ctrl status before eh reset [SCSI] aacraid: Using single reset mask for IOP reset [SCSI] aacraid: Rework IOP reset [SCSI] aacraid: Add periodic checks to see IOP reset status [SCSI] aacraid: Rework SOFT reset code [SCSI] aacraid: Rework aac_src_restart [SCSI] aacraid: Use correct function to get ctrl health [SCSI] aacraid: Make sure ioctl returns on controller reset [SCSI] aacraid: Enable ctrl reset for both hba and arc [SCSI] aacraid: Add reset debugging statements [SCSI] aacraid: Remove reference to Series-9 [SCSI] aacraid: Update driver version to 50834 drivers/scsi/aacraid/aachba.c | 17 ++- drivers/scsi/aacraid/aacraid.h | 22 +++- drivers/scsi/aacraid/commctrl.c | 15 ++- drivers/scsi/aacraid/comminit.c | 18 +--- drivers/scsi/aacraid/commsup.c | 78 +++--- drivers/scsi/aacraid/linit.c| 232 drivers/scsi/aacraid/src.c | 136 +-- 7 files changed, 298 insertions(+), 220 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689980/+subscriptions -- Mailing list: https://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 1688259] Re: kernel-wedge fails in artful due to leftover squashfs-modules d-i files
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1688164] Re: arm64: Add CNTFRQ_EL0 handler
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1688132] Re: Support IPMI system interface on Cavium ThunderX
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1688114] Re: arm64/ACPI support for SBSA watchdog
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1677319] Re: Support low-pin-count devices on Hisilicon SoCs
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1688485] Re: Zesty update to 4.10.13 stable release
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1687045] Re: Zesty update to 4.10.12 stable release
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1688499] Re: Zesty update to 4.10.14 stable release
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1690155] Re: Fix NVLINK2 TCE route
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1689886] Re: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1689661] Re: No PMU support for ACPI-based arm64 systems
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1689856] Re: perf: qcom: Add L3 cache PMU driver
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1689258] Re: Zesty update to 4.10.15 stable release
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1689818] Re: tty: pl011: fix earlycon work-around for QDF2400 erratum 44
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1691146] Re: linux: 4.10.0-22.24 -proposed tracker
This bug was fixed in the package linux - 4.10.0-22.24 --- linux (4.10.0-22.24) zesty; urgency=low * linux: 4.10.0-22.24 -proposed tracker (LP: #1691146) * Fix NVLINK2 TCE route (LP: #1690155) - powerpc/powernv: Fix TCE kill on NVLink2 * CVE-2017-0605 - tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() * perf: qcom: Add L3 cache PMU driver (LP: #1689856) - [Config] CONFIG_QCOM_L3_PMU=y - perf: qcom: Add L3 cache PMU driver * No PMU support for ACPI-based arm64 systems (LP: #1689661) - drivers/perf: arm_pmu: rework per-cpu allocation - drivers/perf: arm_pmu: manage interrupts per-cpu - drivers/perf: arm_pmu: split irq request from enable - drivers/perf: arm_pmu: remove pointless PMU disabling - drivers/perf: arm_pmu: define armpmu_init_fn - drivers/perf: arm_pmu: fold init into alloc - drivers/perf: arm_pmu: factor out pmu registration - drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() - drivers/perf: arm_pmu: handle no platform_device - drivers/perf: arm_pmu: rename irq request/free functions - drivers/perf: arm_pmu: split cpu-local irq request/free - drivers/perf: arm_pmu: move irq request/free into probe - drivers/perf: arm_pmu: split out platform device probe logic - arm64: add function to get a cpu's MADT GICC table - [Config] CONFIG_ARM_PMU_ACPI=y - drivers/perf: arm_pmu: add ACPI framework - arm64: pmuv3: handle !PMUv3 when probing - arm64: pmuv3: use arm_pmu ACPI framework * [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin (LP: #1689886) - ipmi: Fix kernel panic at ipmi_ssif_thread() * tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (LP: #1689818) - tty: pl011: fix earlycon work-around for QDF2400 erratum 44 - tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 * kernel-wedge fails in artful due to leftover squashfs-modules d-i files (LP: #1688259) - Remove squashfs-modules files from d-i - [Config] as squashfs-modules is builtin kernel-image must Provides: it * arm64/ACPI support for SBSA watchdog (LP: #1688114) - clocksource: arm_arch_timer: clean up printk usage - clocksource: arm_arch_timer: rename type macros - clocksource: arm_arch_timer: rename the PPI enum - clocksource: arm_arch_timer: move enums and defines to header file - clocksource: arm_arch_timer: add a new enum for spi type - clocksource: arm_arch_timer: rework PPI selection - clocksource: arm_arch_timer: split dt-only rate handling - clocksource: arm_arch_timer: refactor arch_timer_needs_probing - clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call - clocksource: arm_arch_timer: add structs to describe MMIO timer - clocksource: arm_arch_timer: split MMIO timer probing. - [Config] CONFIG_ACPI_GTDT=y - acpi/arm64: Add GTDT table parse driver - clocksource: arm_arch_timer: simplify ACPI support code. - acpi/arm64: Add memory-mapped timer support in GTDT driver - clocksource: arm_arch_timer: add GTDT support for memory-mapped timer - acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver * kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 (LP: #1674838) - Revert "mm/ksm: handle protnone saved writes when making page write protect" - Revert "mm, ksm: convert write_protect_page() to use page_vma_mapped_walk()" - Revert "mm: introduce page_vma_mapped_walk()" - mm/ksm: handle protnone saved writes when making page write protect * arm64: Add CNTFRQ_EL0 handler (LP: #1688164) - arm64: Add CNTFRQ_EL0 trap handler * Support IPMI system interface on Cavium ThunderX (LP: #1688132) - i2c: thunderx: Enable HWMON class probing * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Zesty update to 4.10.15 stable release (LP: #1689258) - timerfd: Protect the might cancel mechanism proper - Handle mismatched open calls - hwmon: (it87) Avoid registering the same chip on both SIO addresses - dm ioctl: prevent stack leak in dm ioctl call - Linux 4.10.15 * Zesty update to 4.10.14 stable release (LP: #1688499) - ping: implement
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
** Also affects: linux (Ubuntu Artful) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu Artful) Status: Confirmed => 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found. Original bug report: 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/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 1693962] Re: linux: 4.11.0-5.10 -proposed tracker
** Tags removed: block-proposed block-proposed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+subscriptions -- Mailing list: https://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 1692548] Re: Marvell MacchiatoBin crashes in fintek_8250_probe()
** Changed in: linux (Ubuntu) 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/1692548 Title: Marvell MacchiatoBin crashes in fintek_8250_probe() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: In Progress Bug description: [Impact] The Marvell MacchiatoBin community board fails to boot with Ubuntu 17.04 due to a crash in the Fintek 8250 driver. [Test Case] Boot Ubuntu 17.04 on a Marvell MacchiatoBin board in UEFI/ACPI mode, check for crash. [Regression Risk] Fix looks straightforward to me - it avoids probing a PIO-only driver if the port is non-PIO, thus avoiding a crash on platforms where native PIO is unsupported. The fix is upstream and CC'd for stable, so there should be upstream support for any regressions it were to cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692548/+subscriptions -- Mailing list: https://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 1694506] Re: arm-smmu arm-smmu.2.auto: Unhandled context fault
** Changed in: linux (Ubuntu) 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/1694506 Title: arm-smmu arm-smmu.2.auto: Unhandled context fault Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: In Progress Bug description: [Impact] When booting hwe-z on a Cavium ThunderX system in ACPI mode, the on-board NICs don't come up, and the console emits messages like: [ 78.986867] arm-smmu arm-smmu.2.auto: Unhandled context fault: fsr=0x402, iova=0x1f60e8d000, fsynr=0x40090, cb=4 [ 78.997030] arm-smmu arm-smmu.2.auto: Unhandled context fault: fsr=0x402, iova=0x1f4bbdd000, fsynr=0x50090, cb=5 [ 79.185826] arm-smmu arm-smmu.2.auto: Unhandled context fault: fsr=0x402, iova=0x1f60e8e000, fsynr=0x40090, cb=4 [ 79.195990] arm-smmu arm-smmu.2.auto: Unhandled context fault: fsr=0x402, iova=0x1f4bbde000, fsynr=0x50090, cb=5 [Test Case] dmesg | grep "Unhandled context fault" Onboard NICs work (can ssh into it). [Regression Risk] The upstream fix changes are restricted to the NIC driver for this SoC, so regression risk can be mitigated by direct testing. Non-ACPI mode was also tested to make sure we're not breaking DT-based platforms while fixing this for ACPI-based platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694506/+subscriptions -- Mailing list: https://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 1693504] Re: extend-diff-ignore should use exact matches
** Also affects: linux (Ubuntu Artful) Importance: Undecided Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Trusty) 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: Undecided Status: New ** Changed in: linux (Ubuntu Artful) 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/1693504 Title: extend-diff-ignore should use exact matches Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: gen-auto-reconstruct script adds extend-diff-ignore options to debian/source/options. These options, however, are regular expressions, and match any part of a file path. This may cause some files to be excluded from source when they are not an exact match. Using beggining and end of string metacharacters fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693504/+subscriptions -- Mailing list: https://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 1692580] Re: ATS fix: Fix opal_npu_destroy_context call
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu Zesty) Status: New => 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/1692580 Title: ATS fix: Fix opal_npu_destroy_context call Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: ATS patches, just included in zesty-next, needs another patch to fix a bug: http://patchwork.ozlabs.org/patch/764857/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692580/+subscriptions -- Mailing list: https://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 1689886] Re: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin
Verified ubuntu@null-8cfdf006971f:~$ dmesg | head [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 UTC 2017 (Ubuntu 4.10.0-22.24-generic 4.10.15) [0.00] Boot CPU: AArch64 Processor [510f8000] [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: EFI v2.50 by American Megatrends [0.00] efi: ACPI 2.0=0x93f SMBIOS 3.0=0xe41fd18 ESRT=0xd822098 RNG=0x58df598 [0.00] esrt: Reserving ESRT space from 0x0d822098 to 0x0d822170. [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x093F 24 (v02 QCOM ) [0.00] ACPI: XSDT 0x093E 7C (v01 QCOM QDF2400 0113) ubuntu@null-8cfdf006971f:~$ ipmitool fru read 0 fru0.bin Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory ubuntu@null-8cfdf006971f:~$ sudo ipmitool fru read 0 fru0.bin [sudo] password for ubuntu: Fru Size : 1024 bytes Done ubuntu@null-8cfdf006971f:~$ sudo ipmitool fru read 1 fru1.bin Fru Size : 256 bytes Done ubuntu@null-8cfdf006971f:~$ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : B81014010010 Chassis Serial: 715FJ0SA Board Mfg Date: Tue Apr 11 02:47:00 2017 Board Mfg : WIWYNN Board Product : QDF2400 Customer Reference Board Board Serial : B5501401D00271200026J0LA Board Part Number : B81.01410.0009 Product Manufacturer : WIWYNN Product Name : QDF2400 Reference Evaluation Platform Product Part Number : CV90-LA115-P901 Product Version : EVT Product Serial: B81014010010715FJ0SA Product Asset Tag : ubuntu@null-8cfdf006971f:~$ sudo ipmitool fru print 1 Board Mfg Date: Mon Feb 20 10:01:00 2017 Board Mfg : WIWYNN Board Product : REP-1 PCIe riser P950 Board Serial : B5501406D00170200146J0LA Board Part Number : B81.01410.0012 Board Extra : Rev A ubuntu@null-8cfdf006971f:~$ ** Tags removed: verification-needed-zesty ** Tags added: verification-done -- 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/1689886 Title: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Product Serial : Product Asset Tag : ubuntu@ubuntu:~/FRU$ ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin Fru Size : 1024 bytes Size to Write : 256 bytes [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual address 0025 [ 1815.419668] pgd = 219ca2168000 [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, *pmd= [ 1815.431225] Internal error: Oops: 9604 [#1] SMP [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci usb_common pinctrl_qdf2xxx [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic #5~pdaw1.0+bandera.9-Ubuntu [ 1815.480789] Hardware name: Default string Default string/Default string, BIOS 5.12 12/12/2012 [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: edf1a782 [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif] [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif] [ 1815.508046] pc : [] lr : [] pstate: 00400145 [ 1815.515424] sp : edf1a7823de0 [ 1815.518723] x29: edf1a7823de0 x28: [ 1815.524018] x27: x26: [ 1815.529313] x25: x24: [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000 [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00 [ 1815.545198] x19: edeeb9dbb800 x18: 0014 [ 1815.550494] x17: x16: [ 1815.555789] x15: x14: [ 1815.561084] x13: x12:
[Kernel-packages] [Bug 1693618] Re: Microcode SW error detected.
on kernel 4.12.0-041200rc3-generic #201705282131 the problem exist: [ 8987.607601] iwlwifi :04:00.0: regular scan timed out [ 8987.607724] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. [ 8987.607841] iwlwifi :04:00.0: Start IWL Error Log Dump: [ 8987.607846] iwlwifi :04:00.0: Status: 0x, count: 6 [ 8987.607849] iwlwifi :04:00.0: Loaded firmware version: 21.302800.0 [ 8987.607853] iwlwifi :04:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 8987.607857] iwlwifi :04:00.0: 0x02B0 | trm_hw_status0 [ 8987.607860] iwlwifi :04:00.0: 0x | trm_hw_status1 [ 8987.607862] iwlwifi :04:00.0: 0x0BD8 | branchlink2 [ 8987.607866] iwlwifi :04:00.0: 0x00026AC4 | interruptlink1 [ 8987.607869] iwlwifi :04:00.0: 0x00026AC4 | interruptlink2 [ 8987.607871] iwlwifi :04:00.0: 0x | data1 [ 8987.607874] iwlwifi :04:00.0: 0x0080 | data2 [ 8987.607877] iwlwifi :04:00.0: 0x0783 | data3 [ 8987.607880] iwlwifi :04:00.0: 0x674164A9 | beacon time [ 8987.607883] iwlwifi :04:00.0: 0xE3A27B5E | tsf low [ 8987.607886] iwlwifi :04:00.0: 0x003D | tsf hi [ 8987.607889] iwlwifi :04:00.0: 0x | time gp1 [ 8987.607892] iwlwifi :04:00.0: 0x1722E819 | time gp2 [ 8987.607895] iwlwifi :04:00.0: 0x | uCode revision type [ 8987.607898] iwlwifi :04:00.0: 0x0015 | uCode version major [ 8987.607901] iwlwifi :04:00.0: 0x00049ED0 | uCode version minor [ 8987.607904] iwlwifi :04:00.0: 0x0201 | hw version [ 8987.607907] iwlwifi :04:00.0: 0x00C89008 | board version [ 8987.607910] iwlwifi :04:00.0: 0x09D00400 | hcmd [ 8987.607913] iwlwifi :04:00.0: 0x00022000 | isr0 [ 8987.607916] iwlwifi :04:00.0: 0x0080 | isr1 [ 8987.607919] iwlwifi :04:00.0: 0x0800180A | isr2 [ 8987.607922] iwlwifi :04:00.0: 0x00417CC0 | isr3 [ 8987.607925] iwlwifi :04:00.0: 0x | isr4 [ 8987.607928] iwlwifi :04:00.0: 0x0110 | last cmd Id [ 8987.607930] iwlwifi :04:00.0: 0x | wait_event [ 8987.607933] iwlwifi :04:00.0: 0x0148 | l2p_control [ 8987.607936] iwlwifi :04:00.0: 0x00010020 | l2p_duration [ 8987.607939] iwlwifi :04:00.0: 0x003F | l2p_mhvalid [ 8987.607942] iwlwifi :04:00.0: 0x001A | l2p_addr_match [ 8987.607945] iwlwifi :04:00.0: 0x000F | lmpm_pmg_sel [ 8987.607948] iwlwifi :04:00.0: 0x09031905 | timestamp [ 8987.607951] iwlwifi :04:00.0: 0x0034F808 | flow_handler [ 8987.608004] iwlwifi :04:00.0: 0x | ADVANCED_SYSASSERT [ 8987.608007] iwlwifi :04:00.0: 0x | umac branchlink1 [ 8987.608010] iwlwifi :04:00.0: 0x | umac branchlink2 [ 8987.608013] iwlwifi :04:00.0: 0x | umac interruptlink1 [ 8987.608016] iwlwifi :04:00.0: 0x | umac interruptlink2 [ 8987.608018] iwlwifi :04:00.0: 0x | umac data1 [ 8987.608021] iwlwifi :04:00.0: 0x | umac data2 [ 8987.608024] iwlwifi :04:00.0: 0x | umac data3 [ 8987.608027] iwlwifi :04:00.0: 0x | umac major [ 8987.608030] iwlwifi :04:00.0: 0x | umac minor [ 8987.608033] iwlwifi :04:00.0: 0x | frame pointer [ 8987.608036] iwlwifi :04:00.0: 0x | stack pointer [ 8987.608038] iwlwifi :04:00.0: 0x | last host cmd [ 8987.608041] iwlwifi :04:00.0: 0x | isr status reg dmesg in attachment ** Attachment added: "dmesg output kernel 4.12.0-041200rc3-generic" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1693618/+attachment/4887399/+files/intel-041200rc3.dmesg.log ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1693618 Title: Microcode SW error detected. Status in linux-firmware package in Ubuntu: Incomplete Bug description: In dmesg logs I see [81251.363118] iwlwifi :04:00.0: regular scan timed out [81251.363235] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. [81251.363241] iwlwifi :04:00.0: CSR values: [81251.363244] iwlwifi :04:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [81251.363250] iwlwifi :04:00.0:CSR_HW_IF_CONFIG_REG: 0X00c89008 [81251.363256] iwlwifi :04:00.0: CSR_INT_COALESCING: 0X0040 [81251.363261] iwlwifi :04:00.0: CSR_INT: 0X [81251.363266] iwlwifi :04:00.0:CSR_INT_MASK: 0X [81251.363271] iwlwifi :04:00.0: CSR_FH_INT_STATUS: 0X [81251.363276] iwlwifi :04:00.0: CSR_GPIO_IN: 0X0019 [81251.363281] iwlwifi :04:00.0: CSR_RESET: 0X [81251.363286] iwlwifi :04:00.0:CSR_GP_CNTRL: 0X08040005 [81251.363292] iwlwifi :04:00.0: CSR_HW_REV: 0X
[Kernel-packages] [Bug 1694528] Re: Problem with updating the kernel
Thanks for your help. I can't reproduce the error but system seems to run stable now. So I think its not a bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694528 Title: Problem with updating the kernel Status in linux package in Ubuntu: Invalid Bug description: Problem with updating the kernel. Don't know more.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: server 1951 F pulseaudio Date: Tue May 30 22:13:37 2017 HibernationDevice: RESUME=UUID=1efbcfb0-fbc4-491e-855f-880f35b9cf0e InstallationDate: Installed on 2014-03-14 (1173 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ZOTAC ZBOX-ID18 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=f02620f1-1774-4d68-a289-93fd71e97ca5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B211P009 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID18 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 10 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB211P009:bd12/20/2013:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA: dmi.product.name: ZBOX-ID18 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694528/+subscriptions -- Mailing list: https://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 1688017] Re: Connection to bluetooth headsets fails
Hi ! Have you tried to install pulseaudio-module-bluetooth ? -- 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/1688017 Title: Connection to bluetooth headsets fails Status in bluez package in Ubuntu: New Bug description: Hi, since upgrading to 17.04 I can't connect to bluetooth headsets anymore. Headsets are found and listed as devices, but when trying to connect, there's an error blueman.bluez.errors.DBusFailedError: Protocol not available... syslog says: May 3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] May 3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating services: Operation already in progress (114) May 3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0 May 3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] Here someone else reports the same observation: http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/ ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 3 17:12:51 2017 InstallationDate: Installed on 2016-04-22 (376 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) InterestingModules: bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash noplymouth nomodeset text SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago) dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150-NUC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:BB:58:C1:E9:FA ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:18751 acl:51 sco:0 events:1345 errors:0 TX bytes:27309 acl:48 sco:0 commands:1243 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688017/+subscriptions -- Mailing list: https://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 1694837] Re: linux-aws needs modules: drm, drm_kms_helper
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1694837 Title: linux-aws needs modules: drm, drm_kms_helper Status in linux-aws package in Ubuntu: Fix Committed Bug description: The modules drm.ko and drm_kms_helper.ko are needed to support future projects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1694837/+subscriptions -- Mailing list: https://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 1620089] Re: REGRESSION: Laptop hangs during second time it suspends
So I upgraded my Bios to version F.83. And upgraded to Zest (17.04). And now the bug is gone. In a bit of thoughtlessness on my side I did not test in between those two upgrades, so I cannot point at a single change that solved the bug for me. Anyway, now you know. This bug can be closed for my part. -- 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/1620089 Title: REGRESSION: Laptop hangs during second time it suspends Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu 15.10 I had a problem with the suspend functionality on my laptop. The second time it suspends it would hang, and a hard reset was necessary to resolve the problem. After the update to 16.04, the problem was resolved (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216) I updated my laptop using the xenial-updates repository. After the upgrade to linux 4.4.0-31, the suspend issue returned. I have also tried later updates (4.4.0-34 and 4.4.0-36), but the issue is also present in those versions. I therefore still use 4.4.0-28. I tried bisecting, but after a few iterations it messed up my boot partition, and after repairing that, I no longer took the time to finish the bisection. (see https://launchpad.net/ubuntu/+source/linux/4.4.0-31.50 for changelog) I have a short bit (but not complete work) of the git bisect log: $ git bisect log # bad: [2a1e175b928aefed1fd3c90c98e845f764fa8684] UBUNTU: Ubuntu-4.4.0-31.50 # good: [a6409cad137621e2b43d9f49c757fbc996539e85] UBUNTU: Ubuntu-4.4.0-28.47 git bisect start 'Ubuntu-4.4.0-31.50' 'Ubuntu-4.4.0-28.47' # bad: [44d66d94ed3e6e2434b06af7180a441cbf2b9f83] UBUNTU: Ubuntu-4.4.0-29.48 git bisect bad 44d66d94ed3e6e2434b06af7180a441cbf2b9f83 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan9230 F pulseaudio Date: Sun Sep 4 19:42:54 2016 HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272 InstallationDate: Installed on 2016-02-03 (214 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:57eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro nogpumanager quiet splash pci=noaer PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.160 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A4 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP == Regression details == Discovered in version: 4.4.0-29 Last known good version: 4.4.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620089/+subscriptions -- Mailing list: https://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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
** Tags added: ubuntu-16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd want to use less than that, but more than 512 MB given the evidence observed. Hope this helps == Comment: #28 - Mauro Sergio Martins Rodrigues - 2017-01-13 10:12:28
[Kernel-packages] [Bug 1691814] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1691814 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1691814 Title: linux xenial derivatives fail to build Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Fix Committed Status in linux-lts-xenial package in Ubuntu: Fix Committed Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Fix Committed Bug description: After recent changes to prevent derivative packages from building *-tools-common, derivatives fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691814/+subscriptions -- Mailing list: https://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 1690183] Re: linux-aws/linux-gke incorrectly producing an empty linux-*-source package-*
Confirmed that linux-aws (4.4.0-1018.27) and linux-gke (4.4.0-1014.14), which are currently in -proposed, are not producing the linux-*-source packages anymore. ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1690183 Title: linux-aws/linux-gke incorrectly producing an empty linux-*-source package-* Status in linux-aws package in Ubuntu: Confirmed Status in linux-gke package in Ubuntu: Confirmed Status in linux-aws source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: Fix Committed Bug description: We are building a shipping a basically empty package which claimed to be the source package for this kernel. As this linux-source-NNN packages are intended as input to things like usermode linux, and that should be using the one from the primary package. We should drop this empty and missleading package. We are explicitly turning off the contents of the source package: debian.*/rules.d/amd64.mk: do_source_package = false But this only suppresses the contents of the package. We also have to remove it from the control file to get rid of it completely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1690183/+subscriptions -- Mailing list: https://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 1691814] Re: linux xenial derivatives fail to build
Confirmed that all derivatives from xenial kernel 4.4.0-79.100 were built successfully. ** 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/1691814 Title: linux xenial derivatives fail to build Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Fix Committed Status in linux-lts-xenial package in Ubuntu: Fix Committed Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Fix Committed Bug description: After recent changes to prevent derivative packages from building *-tools-common, derivatives fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691814/+subscriptions -- Mailing list: https://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 1694583] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1694583 Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Software updater fails to install OS updates. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/2679/fd/17: Stale file handle Cannot stat file /proc/2679/fd/19: Stale file handle USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2567 F pulseaudio CasperVersion: 1.380 Date: Tue May 30 22:01:51 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude E6430 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi 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~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-21-generic (not installed) 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: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.asset.tag: 497888 dmi.board.name: 09YC31 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 497888 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/20/2013:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn09YC31:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694583/+subscriptions -- Mailing list: https://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 1694590] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1694590 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 17.04 Release: 17.04 N: Unable to locate package pkgname I got error message when I started Ubuntu and then software Centre to continue removing program that wasn't removed before I shut down, it also can't remove it now, it was the replace of chromium web browser , there are new version of it , when I found that it's not at Ubuntu software centre , also no update or upgrade by apt-get for it , so I downloaded it from google site and installed it, but to remove the old one after that it gave an error and don't able to remove it The old version of Ubuntu software centre was better than this one for me. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bassem 1637 F pulseaudio Date: Wed May 31 06:00:05 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=b0fc9d2b-1da6-4661-9c12-a9938ce8de27 InstallationDate: Installed on 2017-05-01 (30 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Inspiron 5551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=fa105b6f-dfdd-449f-aac1-a673bf9b6d57 ro quiet splash intel_idle.max_cstate=1 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 N/A SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) 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/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0WT4NH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/13/2015:svnDellInc.:pnInspiron5551:pvrA03:rvnDellInc.:rn0WT4NH:rvrA00:cvnDellInc.:ct8:cvrA03: dmi.product.name: Inspiron 5551 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694590/+subscriptions -- Mailing list: https://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 1694860] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1694860 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Encountered error on installing OS update. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2011 F pulseaudio /dev/snd/controlC1: michael2011 F pulseaudio Date: Wed May 31 19:23:59 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=5113d727-1176-41e5-a79a-fde6519cc6f3 InstallationDate: Installed on 2016-12-08 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite P55t-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=09e39bab-239d-409f-bd53-1958a90cc772 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 N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 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: 11/04/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd11/04/2013:svnTOSHIBA:pnSatelliteP55t-A:pvrPSPMJU-07002J:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P55t-A dmi.product.version: PSPMJU-07002J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694860/+subscriptions -- Mailing list: https://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 1694766] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (cu
** Tags removed: need-duplicate-check -- 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/1694766 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: during update process, computer locked up. I had to reboot in order to continue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruce 1777 F...m pulseaudio /dev/snd/controlC0: bruce 1777 F pulseaudio Date: Wed May 31 13:15:15 2017 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-31-generic (--configure): package linux-image-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=87a40016-a151-4089-999c-c7c639f32fe5 InstallationDate: Installed on 2017-01-29 (122 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP 260-a010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=93e49f9c-7112-445f-8204-493c743ad44a 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 N/A SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: CNV63305CD dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV63305CD dmi.chassis.type: 1 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.10:bd06/13/2016:svnHP:pn260-a010:pvr:rvnHP:rn821D:rvr00:cvnHP:ct1:cvr: dmi.product.name: 260-a010 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694766/+subscriptions -- Mailing list: https://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 1694996] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1694996 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Update stops about half way through and never finishes. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1836 F pulseaudio Date: Wed May 31 11:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1532:0043 Razer USA, Ltd Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=52878891-7f1a-4352-b0e1-754c5cf639ec 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 N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 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: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.213:bd10/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL552VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694996/+subscriptions -- Mailing list: https://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 1689365] Re: ibmvscsis: Do not send aborted task response
** Tags added: ubuntu-17.04 -- 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/1689365 Title: ibmvscsis: Do not send aborted task response Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: ---Problem Description--- ibmvscsis: Do not send aborted task response The driver is sending a response to the actual scsi op that was aborted by an abort task TM, while LIO is sending a response to the abort task TM. ibmvscsis_tgt does not send the response to the client until release_cmd time. The reason for this was because if we did it at queue_status time, then the client would be free to reuse the tag for that command, but we're still using the tag until the command is released at release_cmd time, so we chose to delay sending the response until then. That then caused this issue, because release_cmd is always called, even if queue_status is not. SCSI spec says that the initiator that sends the abort task TM NEVER gets a response to the aborted op and with the current code it will send a response. Thus this fix will remove that response if the CMD_T_ABORTED && !CMD_T_TAS. Another case with a small timing window is the case where if LIO sends a TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort cmd before the release_cmd for the (attemped) aborted cmd, then we need to ensure that we send the response for the (attempted) abort cmd to the client before we send the response for the TMR Abort cmd. [PATCH v3] ibmvscsis: Do not send aborted task response https://www.spinics.net/lists/stable/msg170418.html This patch also requires a patch that was accepted upstream which is: target: Fix unknown fabric callback queue-full errors https://patchwork.kernel.org/patch/9405013/ ---uname output--- Latest Yakkety master branch Machine Type = P8 ---Steps to Reproduce--- Send abort ops over and over and you will hit it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions -- Mailing list: https://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 1649513] Re: [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory tests in kernel 4.8.0-17-generic
** Tags added: ubuntu-16.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649513 Title: [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory tests in kernel 4.8.0-17-generic Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Issue: -- NMI Watchdog Bug and soft lockup occurs when htx memory test is run in ubuntu 16.10. Environment: -- Arch : ppc64le Platform : Ubuntu KVM Guest Host : ubuntu 16.10 [4.8.0-17 -kernel ] Guest : ubuntu 16.10 [4.8.0-17 - Kernel] Steps To Reproduce: --- 1 - Install a Ubuntu KVM Guest and install htx package in the guest got from the link, http://ausgsa.ibm.com/projects/h/htx/public_html/htxonly/htxubuntu-413.deb 2 - Run the Htx mdt.mem 3 - The system Hits soft lockup Issue as below: dmesg o/p: [60287.590335] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 1141s! [hxemem64:23468] [60287.590572] Modules linked in: vmx_crypto ip_tables x_tables autofs4 ibmvscsi crc32c_vpmsum [60287.590585] CPU: 3 PID: 23468 Comm: hxemem64 Tainted: G L 4.8.0-17-generic #19-Ubuntu [60287.590587] task: c012a0971e00 task.stack: c012a2d4 [60287.590589] NIP: c0015004 LR: c0015004 CTR: c0165e90 [60287.590591] REGS: c012a2d439a0 TRAP: 0901 Tainted: G L (4.8.0-17-generic) [60287.590592] MSR: 80009033 CR: 48004244 XER: [60287.590603] CFAR: c0165890 SOFTE: 1 GPR00: c0165f9c c012a2d43c20 c14e5e00 0900 GPR04: 0008 000100e4d61a GPR08: 0006 000100e4d619 c012bfee3130 GPR12: 3fffae6cdc70 3fffae436900 [60287.590627] NIP [c0015004] arch_local_irq_restore+0x74/0x90 [60287.590630] LR [c0015004] arch_local_irq_restore+0x74/0x90 [60287.590631] Call Trace: [60287.590634] [c012a2d43c20] [c012bfeccd80] 0xc012bfeccd80 (unreliable) [60287.590639] [c012a2d43c40] [c0165f9c] run_timer_softirq+0x10c/0x230 [60287.590644] [c012a2d43ce0] [c0b94adc] __do_softirq+0x18c/0x3fc [60287.590648] [c012a2d43de0] [c00d5828] irq_exit+0xc8/0x100 [60287.590653] [c012a2d43e00] [c0024810] timer_interrupt+0xa0/0xe0 [60287.590657] [c012a2d43e30] [c0002814] decrementer_common+0x114/0x180 [60287.590659] Instruction dump: [60287.590662] 994d023a 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 e8010010 [60287.590670] 7c0803a6 4e800020 6042 4bfed259 <6000> 4be4 6042 e92d0020 [63127.581494] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 339s! [hxemem64:23467] [63127.629682] Modules linked in: vmx_crypto ip_tables x_tables autofs4 ibmvscsi crc32c_vpmsum [63127.629699] CPU: 2 PID: 23467 Comm: hxemem64 Tainted: G L 4.8.0-17-generic #19-Ubuntu [63127.629701] task: c012a0965800 task.stack: c012a2d58000 [63127.629703] NIP: 10011e60 LR: 1000ec6c CTR: 00f33196 [63127.629706] REGS: c012a2d5bea0 TRAP: 0901 Tainted: G L (4.8.0-17-generic) [63127.629707] MSR: 8001d033 CR: 42004482 XER: [63127.629719] CFAR: 10011e68 SOFTE: 1 GPR00: 1000e854 3fffadc2e540 10047f00 000d GPR04: 0200 3ff5a800 5a5a5a5a5a5a5a5a 3ff5b0667348 GPR08: 1006c8e0 1006ca04 f001 GPR12: 3fffae6cdc70 3fffadc36900 [63127.629740] NIP [10011e60] 0x10011e60 [63127.629742] LR [1000ec6c] 0x1000ec6c [63127.629743] Call Trace: == Comment: #3 - Santhosh G - 2016-09-28 02:17:29 == Memory Info : root@ubuntu:~# cat /proc/meminfo MemTotal: 78539776 kB MemFree:72219392 kB MemAvailable: 77217088 kB Buffers: 212544 kB Cached: 5249088 kB SwapCached:0 kB Active: 1440832 kB Inactive:4107264 kB Active(anon): 93888 kB Inactive(anon): 8640 kB Active(file):1346944 kB Inactive(file): 4098624 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 3443648 kB SwapFree:3443648 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 87296 kB Mapped:30400 kB Shmem: 16128 kB Slab: 381440 kB SReclaimable: 295872 kB SUnreclaim:85568 kB KernelStack:2176 kB PageTables: 2048 kB NFS_Unstable: 0 kB
[Kernel-packages] [Bug 1658733] guest console output of dump attempt
Default Comment by Bridge ** Attachment added: "guest console output of dump attempt" https://bugs.launchpad.net/bugs/1658733/+attachment/4887384/+files/dotg9-kdump.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd want to use less than tha
[Kernel-packages] [Bug 1658733] libvirt XML for multipath guest dotg9
Default Comment by Bridge ** Attachment added: "libvirt XML for multipath guest dotg9" https://bugs.launchpad.net/bugs/1658733/+attachment/4887389/+files/dotg9.xml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd want to use less than that, but
[Kernel-packages] [Bug 1658733] Adds "noirqdistrib" parameter to kdump command line
--- Comment on attachment From maur...@br.ibm.com 2017-01-23 12:10 EDT--- This patch fixes the issue. The noirqdistrib is a necessary parameter for ppc64 platform as stated in kdump docs https://www.kernel.org/doc//Documentation/kdump/kdump.txt With this fix crash kernel uses the correct irq server for the case where only one cpu is online. ** Attachment added: "Adds "noirqdistrib" parameter to kdump command line" https://bugs.launchpad.net/bugs/1658733/+attachment/4887390/+files/add_noirqdistrib_param_for_ppc64.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theo
[Kernel-packages] [Bug 1658733] host sosreport
Default Comment by Bridge ** Attachment added: "host sosreport" https://bugs.launchpad.net/bugs/1658733/+attachment/4887385/+files/sosreport-dotkvm.149956-20161214172157.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd want to use less
[Kernel-packages] [Bug 1658733] sosreport from Ubuntu guest dotg9
Default Comment by Bridge ** Attachment added: "sosreport from Ubuntu guest dotg9" https://bugs.launchpad.net/bugs/1658733/+attachment/4887386/+files/sosreport-dotg9.149956-20161215094027.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd w
[Kernel-packages] [Bug 1658733] kdump kernel console msgs with bug 146907 workaround
Default Comment by Bridge ** Attachment added: "kdump kernel console msgs with bug 146907 workaround" https://bugs.launchpad.net/bugs/1658733/+attachment/4887388/+files/dotg9-kdump-bz146907-workaround.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviou
[Kernel-packages] [Bug 1676678] Re: ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress tests
** Tags added: ubuntu-17.04 -- 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/1676678 Title: ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress tests Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: ---Problem Description--- After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM guest dotg6 crashed, produced a kdump, and rebooted. ---uname output--- Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) Stack trace output: [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1] [ 1909.621870] SMP NR_CPUS=2048 [ 1909.621871] NUMA [ 1909.621925] pSeries [ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 4.10.0-13-generic #15-Ubuntu [ 1909.622536] task: c00042a64200 task.stack: c0003423c000 [ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: c0609d00 [ 1909.622737] REGS: c0003423f7f0 TRAP: 0380 Not tainted (4.10.0-13-generic) [ 1909.622850] MSR: 8280b033 [ 1909.622860] CR: 24002428 XER: 2000 [ 1909.623016] CFAR: c061a238 SOFTE: 1 [ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc c00170fd5000 [ 1909.623016] GPR04: 7530 [ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 d16a2ef8 [ 1909.623016] GPR12: c0609d00 c1b81200 0008 0001 [ 1909.623016] GPR16: 46f05f80 [ 1909.623016] GPR20: 46f061f8 46f05f58 c0017fd4a808 [ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 d16a1648 [ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 0058 [ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 [virtio_scsi] [ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 [virtio_scsi] [ 1909.624235] Call Trace: [ 1909.624278] [c0003423fa70] [d16a14a0] __virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable) [ 1909.624445] [c0003423fac0] [d16a1678] virtscsi_cpu_online+0x30/0x70 [virtio_scsi] [ 1909.624746] [c0003423fae0] [c00db73c] cpuhp_invoke_callback+0x3ec/0x5a0 [ 1909.624887] [c0003423fb50] [c00dba88] cpuhp_down_callbacks+0x78/0xf0 [ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0 [ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0 [ 1909.625330] [c0003423fc40] [c074b834] cpu_subsys_offline+0x24/0x40 [ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130 [ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0 [ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60 [ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0 [ 1909.625984] [c0003423fd20] [c03f98bc] kernfs_fop_write+0x17c/0x250 [ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70 [ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240 [ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110 [ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0 [ 1909.626624] Instruction dump: [ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 e9290010 [ 1909.626835] 2fa9 7d234b78 419e002c e9290020 e9290058 2fa9 7d2c4b78 [ 1909.627003] ---[ end trace ecc8a323beb021a2 ]--- crash> bt PID: 27704 TASK: c00042a64200 CPU: 2 COMMAND: "ppc64_cpu" #0 [c0003423f630] crash_kexec at c01a04c4 #1 [c0003423f670] oops_end at c0024da8 #2 [c0003423f6f0] bad_page_fault at c00627b0 #3 [c0003423f760] slb_miss_bad_addr at c0026828 #4 [c0003423f780] bad_addr_slb at c0008acc Data SLB Access [380] exception frame: R0: d16a14a0R1: c0003423fa70R2: d16ab8cc R3: c00170fd5000R4: R5: R6: R7: 7530R8: c146c700 R9: 757465736d642f6eR10: c146dbe0R11: d0
[Kernel-packages] [Bug 1658733] loglevel 8 kdump console log
Default Comment by Bridge ** Attachment added: "loglevel 8 kdump console log" https://bugs.launchpad.net/bugs/1658733/+attachment/4887387/+files/dotg9-kdump-loglevel8.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/ kdump and Ubuntu, I usually set the crashkernel allocated size right away to 4GB to avoid problems. Since this is a smaller sized guest, obviously we'd want to use less than t
[Kernel-packages] [Bug 1677685] Re: [SRU Zesty] Target: Configfs Crashes and kernel crash fixes
** Tags added: ubuntu-17.04 -- 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/1677685 Title: [SRU Zesty] Target: Configfs Crashes and kernel crash fixes Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A number of patches that need to be backported for target subsystem. target: Don't BUG_ON during NodeACL dynamic -> explicit conversion https://patchwork.kernel.org/patch/9560085/ target: Use correct SCSI status during EXTENDED_COPY exception https://patchwork.kernel.org/patch/9560083/ target: Fix early transport_generic_handle_tmr abort scenario https://patchwork.kernel.org/patch/9560077/ target: Fix multi-session dynamic se_node_acl double free OOPs https://patchwork.kernel.org/patch/9560081/ target: Fix COMPARE_AND_WRITE ref leak for non GOOD status https://patchwork.kernel.org/patch/9560065/ target: Fix NULL dereference during LUN lookup + active I/O shutdown https://patchwork.kernel.org/patch/9587799/ target: Avoid mappedlun symlink creation during lun shutdown https://lkml.org/lkml/2017/3/30/180 Contact Information = Bryant G. Ly/b...@us.ibm.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1677685/+subscriptions -- Mailing list: https://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 1566400] Re: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array.
** Tags added: ubuntu-16.04 -- 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/1566400 Title: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: State: Open by: nauahmed on 17 March 2016 16:09:48 Hi, While using MaxView Storage Manager on Ubuntu 16.04 from https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=7bb2d98d-64aa-437d-863e-db67dc1f50db https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W6ee916ce65bf_4973_a6c3_a0f025d8acc6/page/PMC%20Adapter%20Series%207%20and%20Series%208%20Code%20Deliveries PostGA_2.zip https://w3-connections.ibm.com/files/form/anonymous/api/library/c5f8d539 -710e-4e26-9d2f-5073644c8c67/document/f9b22e38-4b5e-46ab-94ca- f5cb80b9e13d/media/PostGA_2.zip with Expand/Migrate Logical Drive option in web GUI menu. whole array is lost. Steps: 1> INITIALIZE ALL disks # arcconf task start 1 device all INITIALIZE noprompt Controllers found: 1 Initializing Channel 0, Device 9. Initializing Channel 0, Device 12. Initializing Channel 0, Device 13. Initializing Channel 0, Device 14. 4 device(s) initialized. Command completed successfully. 2> Login to Web gui of MSM.. clink on controller --> create logical device ---> custom mode -->RAID 1 Mirroring; 2 drives required; redundant ---> select minimum two drives ---> next ---> finish. 3> Click on new logical raid1 device, click expand/migrate logical device RAID1 Select a RAID level and click 'Next' to continue Select raid Level RAID Members Set Attributes Summary RAID 1 Mirroring,2 drives required, redundant RAID 5 Striping with parity,3 or more drives required, redundant Simple Volume A single drive segment,not redundant Select RAID5, add additional drive, next, Finish, Existing RAID 1 logical device is lost.. there is no migration <-- ALL data lost... root@p7pran04:~# uname -a Linux p7pran04 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@p7pran04:~# arcconf getversion Controllers found: 1 Controller #1 == Firmware : 7.8-0 (32968) Staged Firmware: 7.8-0 (32968) BIOS : 7.8-0 (32968) Driver : 1.2-1 (41010) Boot Flash : 7.8-1 (32968) CPLD (Load version/ Flash version) : 5/ 10 SEEPROM (Load version/ Flash version) : 1/ 1 root@p7pran04:~# modinfo aacraid filename: /lib/modules/4.4.0-12-generic/kernel/drivers/scsi/aacraid/aacraid.ko version:1.2-1[41010]-ms license:GPL description:Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver author: Red Hat Inc and Adaptec srcversion: FE59F41215F9D0437EA29CE alias: pci:v9005d028Fsv*sd*bc*sc*i* alias: pci:v9005d028Dsv*sd*bc*sc*i* alias: pci:v9005d028Csv*sd*bc*sc*i* alias: pci:v9005d028Bsv*sd*bc*sc*i* alias: pci:v9005d0288sv*sd*bc*sc*i* alias: pci:v9005d0286sv*sd*bc*sc*i* alias: pci:v9005d0285sv*sd*bc*sc*i* alias: pci:v9005d0285sv17AAsd*bc*sc*i* alias: pci:v9005d0285sv1028sd*bc*sc*i* alias: pci:v1011d0046sv103Csd10C2bc*sc*i* alias: pci:v1011d0046sv9005sd1364bc*sc*i* alias: pci:v1011d0046sv9005sd0364bc*sc*i* alias: pci:v1011d0046sv9005sd0365bc*sc*i* alias: pci:v9005d0285sv1028sd0287bc*sc*i* alias: pci:v9005d0286sv9005sd02A2bc*sc*i* alias: pci:v9005d0285sv9005sd029Abc*sc*i* alias: pci:v9005d0285sv9005sd0299bc*sc*i* alias: pci:v9005d0285sv9005sd0298bc*sc*i* alias: pci:v9005d0286sv1014sd9540bc*sc*i* alias: pci:v9005d0286sv1014sd9580bc*sc*i* alias: pci:v9005d0285sv1014sd0312bc*sc*i* alias: pci:v9005d0285sv1014sd02F2bc*sc*i* alias: pci:v9005d0285sv9005sd0297bc*sc*i* alias: pci:v9005d0285sv9005sd0296bc*sc*i* alias: pci:v9005d0285sv103Csd3227bc*sc*i* alias: pci:v9005d0285sv9005sd0294bc*sc*i* alias: pci:v9005d0285sv9005sd0293bc*sc*i* alias:
[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA
** Tags added: ubuntu-16.04 -- 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/1692538 Title: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - BRYANT G. LY - 2017-05-22 08:40:16 == ---Problem Description--- - Issue 1: ibmveth doesn't support largesend and checksum offload features when configured as "Trunk". Driver has explicit checks to prevent enabling these offloads. - Issue 2: SYN packet drops seen at destination VM. When the packet originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux Bridge) and delivered to outbound Trunk ibmveth. At this point the outbound ibmveth transmit routine will not set "no checksum" and "checksum good" bits in transmit buffer descriptor, as it does so only when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets delivered to destination VM, TCP layer receives the packet with checksum value of 0 and with no checksum related flags in ip_summed field. This leads to packet drops. So, TCP connections never goes through fine. - Issue 3: First packet of a TCP connection will be dropped, if there is no OVS flow cached in datapath. OVS while trying to identify the flow, computes the checksum. The computed checksum will be invalid at the receiving end, as ibmveth transmit routine zeroes out the pseudo checksum value in the packet. This leads to packet drop. - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. When Physical NIC has GRO enabled and when OVS bridges these packets, OVS vport send code will end up calling dev_queue_xmit, which in turn calls validate_xmit_skb. In validate_xmit_skb routine, the larger packets will get segmented into MSS sized segments, if SKB has a frag_list and if the driver to which they are delivered to doesn't support NETIF_F_FRAGLIST feature. Contact Information = Bryant G. Ly/b...@us.ibm.com ---uname output--- 4.8.0-51.54 Machine Type = p8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Increases performance greatly The patch has been accepted upstream: https://patchwork.ozlabs.org/patch/764533/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692538/+subscriptions -- Mailing list: https://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 1692580] Re: ATS fix: Fix opal_npu_destroy_context call
** Tags added: ubuntu-16.04 -- 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/1692580 Title: ATS fix: Fix opal_npu_destroy_context call Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ATS patches, just included in zesty-next, needs another patch to fix a bug: http://patchwork.ozlabs.org/patch/764857/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692580/+subscriptions -- Mailing list: https://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 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84
** Tags added: ubuntu-16.04 -- 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/1693369 Title: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: This is a request to add the following upstream commit to both Ubuntu 16.04.1 and 16.04.2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae Without this patch, the symlink in sysfs which binds a SAS device to an enclosure slot does not get created. This makes disk hotplug near impossible on large JBOD disk drawers. You should be able to do: ls /sys/block/sdb/device/ | grep enclosure and see something like: enclosure_device:1 If you cd to this directory, you can then access the SES controls for that slot to flash the LED to assist in locating the disk to replace a failed disk. Currently with 16.04.1 and 16.04.2, these symlinks are not getting created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1693369/+subscriptions -- Mailing list: https://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 1692789] Re: Ubuntu 16.04.03: Update aacraid driver to latest level for hardware enablement
** Tags added: ubuntu-16.04 -- 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/1692789 Title: Ubuntu 16.04.03: Update aacraid driver to latest level for hardware enablement Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Brian J. King - 2017-05-22 16:54:15 == This is a request to update the aacraid driver to the latest level in order to support the onboard PM8069 SATA RAID controller on Power systems. The full list of required git commits will be attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692789/+subscriptions -- Mailing list: https://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 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.
** Tags added: ubuntu-17.04 -- 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/1694485 Title: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SUDEESH JOHN - 2017-03-18 13:55:03 == ---Problem Description--- call trace while injecting error to the CAPI card. " WARNING: CPU: 31 PID: 491 at /build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 cxl_adapter_context_unlock+0x68/0x90 [cxl] " ---uname output--- Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8247-21L ---Steps to Reproduce--- 1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes 2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image 3. echo 0x8000 > /sys/kernel/debug/powerpc/PCI/err_injct_outbound ---The complete call trace --- Mar 18 14:39:09 freak kernel: [ 289.675421] [ cut here ] Mar 18 14:39:09 freak kernel: [ 289.675431] WARNING: CPU: 5 PID: 491 at /build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 cxl_adapter_context_unlock+0x68/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675432] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php Mar 18 14:39:09 freak kernel: [ 289.675490] CPU: 5 PID: 491 Comm: eehd Not tainted 4.10.0-13-generic #15-Ubuntu Mar 18 14:39:09 freak kernel: [ 289.675492] task: c003bfbfde00 task.stack: c003bfc5c000 Mar 18 14:39:09 freak kernel: [ 289.675493] NIP: d5cc0ca0 LR: d5cc0c9c CTR: c0605aa0 Mar 18 14:39:09 freak kernel: [ 289.675495] REGS: c003bfc5f6a0 TRAP: 0700 Not tainted (4.10.0-13-generic) Mar 18 14:39:09 freak kernel: [ 289.675496] MSR: 9282b033 Mar 18 14:39:09 freak kernel: [ 289.675504] CR: 28008282 XER: 2000 Mar 18 14:39:09 freak kernel: [ 289.675504] CFAR: c0b568dc SOFTE: 1 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR00: d5cc0c9c c003bfc5f920 d5cf2d88 002f Mar 18 14:39:09 freak kernel: [ 289.675504] GPR04: 0001 03fd 63206576 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR08: c15dc700 0001 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR12: 8800 cfb82d00 c0108c88 c003c51f9f00 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR16: Mar 18 14:39:09 freak kernel: [ 289.675504] GPR20: c0d53990 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR24: c0d53968 c14a4330 c003ab8fa800 c003bd2c20c0 Mar 18 14:39:09 freak kernel: [ 289.675504] GPR28: c003c5051098 c003ab8fa800 Mar 18 14:39:09 freak kernel: [ 289.675535] NIP [d5cc0ca0] cxl_adapter_context_unlock+0x68/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675540] LR [d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675541] Call Trace: Mar 18 14:39:09 freak kernel: [ 289.675547] [c003bfc5f920] [d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable) Mar 18 14:39:09 freak kernel: [ 289.675556] [c003bfc5f980] [d5cd022c] cxl_configure_adapter+0x954/0x990 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675563] [c003bfc5fa30] [d5cd02c0] cxl_pci_slot_reset+0x58/0x240 [cxl] Mar 18 14:39:09 freak kernel: [ 289.675568] [c003bfc5fae0] [c003b0d4] eeh_report_reset+0x154/0x190 Mar 18 14:39:09 freak kernel: [ 289.675571] [c003bfc5fb20] [c0039428] eeh_pe_dev_traverse+0x98/0x170 Mar 18 14:39:09 freak kernel: [ 289.675574] [c003bfc5fbb0] [c003b81c] eeh_handle_normal_event+0x3ec/0x540 Mar 18 14:39:09 freak kernel: [ 289.675577] [c003bfc5fc60] [c
[Kernel-packages] [Bug 1685899] Re: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation
** Tags added: ubuntu-17.04 -- 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/1685899 Title: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Bug description: Issue: JFS related call traces and system enters xmon when rebooted after installation Steps to reproduce: - 1 - Install Ubuntu 17.04 the system with - prepboot - /root [JFS filesystem] - swap space 2 -After installation when rebooted it gives out call traces like as below: [3.895246] Unable to handle kernel paging request for data at address 0x [3.895278] Faulting instruction address: 0xd4c5df1c [3.895284] Oops: Kernel access of bad area, sig: 11 [#1] [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA [3.895290] pSeries [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi crc32c_vpmsum [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic #16-Ubuntu [3.895304] task: c00381d3c800 task.stack: c00381fd [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: c01279d0 [3.895310] REGS: c00381fd3500 TRAP: 0300 Not tainted (4.9.0-15-generic) [3.895313] MSR: 8280b033 [ 3.895322] CR: 48008804 XER: 0001 [3.895324] CFAR: c0008a60 DAR: DSISR: 4000 SOFTE: 1 GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 GPR08: 00180e97 d4c6a608 GPR12: c01279d0 cfb90e00 GPR16: GPR20: GPR24: 1000 d4c72b38 GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs] [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs] [3.895374] Call Trace: [3.895378] [c00381fd3780] [d4c5de6c] __get_metapage+0x154/0x6f0 [jfs] (unreliable) [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs] [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs] [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 [jfs] [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240 [3.895402] [c00381fd3b00] [c032e8a8] walk_component+0x2d8/0x3f0 [3.895406] [c00381fd3b70] [c032eb94] link_path_walk+0x1d4/0x600 [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480 [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160 [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380 [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0 [3.895424] Instruction dump: [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 41820460 [3.895433] ebdd0030 41920034 e91d0008 e93f0038 811e 80e70090 39080001 [3.895441] ---[ end trace c2aa9ba09ea05eac ]--- [3.895443] [4.088560] systemd-journald[925]: Received request to flush runtime journal from PID 1 [4.362062] crypto_register_alg 'aes' = 0 [4.362112] crypto_register_alg 'cbc(aes)' = 0 [4.362150] crypto_register_alg 'ctr(aes)' = 0 [4.362191] crypto_register_alg 'xts(aes)' = 0 [4.366949] pseries_rng: Registering IBM pSeries RNG driver When I first connected to the LPAR, it was unresponsive so I restarted it from the HMC and surprisingly it came up to the login prompt and I logged into the shell. I proceeded to install the matching linux- image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the installation of the matching dbgsym wasn't as helpful as I wanted it to be. objdump, crash tool, or addr2line wouldn't give me the source line correspond to the NIP address. I then restarted the LPAR with xmon enabled and it would drop to xmon immediately after attempting to remount / and at the same location as before at __get_metapage+0x204/0x6f0 [jfs] and again with a dereference of 0x0 as the cause of the data exception 0xd649df54 <__get_metapage+508>:ld r8,8(r29) 0xd649df58 <__get_metapage+512>:ld r9,56(r31) 0xd649df5c <__get_metapage+516>:ld r7,0(r8) <-- r8 = 0x0 Just to see if this was consistent, I rebooted the system
[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken
** Tags added: ubuntu-17.04
--
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/1691045
Title:
PowerPC: Pstore dump for powerpc is broken
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to
/fs/pstore/dmesg*
(Entry doesn't gets created at all)
Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com
---uname output---
Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = lpar
Write to nvram failed
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Checked kdump kernel is loaded.
2. Triggered system crash
# echo c > /proc/sysrq-trigger
3. /sys/fs/pstore/dmesg* doesn't gets created
This issue can be reproduced after commit c950fd6f201
c950fd6f201 - pstore: Split pstore fragile flags
It introduces PSTORE_FLAGS_DMESG, which is not set for PowerPC.
Please include below commit 041939c1ec5 as this fixes this issue.
commit 041939c1ec54208b42f5cd819209173d52a29d34
Author: Ankit Kumar
Date: Thu Apr 27 17:03:13 2017 +0530
pstore: Fix flags to enable dumps on powerpc
After commit c950fd6f201a kernel registers pstore write based on flag set.
Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not
set for
powerpc architecture. On panic, kernel doesn't write message to
/fs/pstore/dmesg*(Entry doesn't gets created at all).
This patch enables pstore write for powerpc architecture by setting
PSTORE_FLAGS_DMESG flag.
Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
Cc: sta...@vger.kernel.org # v4.9+
Signed-off-by: Ankit Kumar
Signed-off-by: Kees Cook
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691045/+subscriptions
--
Mailing list: https://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 1690225] Re: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE
** Tags added: ubuntu-16.04 -- 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/1690225 Title: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-05-11 15:30:52 == The PR_DUMPABLE flag causes the pid related paths of the proc file system to be owned by ROOT. The implementation of pthread_set/getname_np however needs access to /proc//task//comm. If PR_DUMPABLE is false this implementation is locked out. This patch installs a special permission function for the file "comm" that grants read and write access to all threads of the same group regardless of the ownership of the inode. For all other threads the function falls back to the generic inode permission check. Nvidia-docker issue on ppc64le: 1b3044e39a89cb1d4d5313da477e8dfea2b5232d This is fixed by commit 1b3044e39a89cb1d4d5313da477e8dfea2b5232d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690225/+subscriptions -- Mailing list: https://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 1694596] Re: LiteOn NVMe APST issue
My NVMe drive failed again yesterday. I no longer think the errors are due to the APST support. I'm starting to think it's either something in the Linux kernel 4.8.0-53 upgrade or simply a problem with the drive hardware or firmware. The time-line of the errors is shown below. Note that I never defined the "default_ps_max_latency_us" parameter to 6000. I only set it to a value of zero. Parameter "nvme_core.default_ps_max_latency_us" is not defined: 2017-04-04 Upgraded to 4.8.0-46.49 2017-04-24 Upgraded to 4.8.0-49.52 ← Adds NVMe APST support (LP: #1664602) 2017-05-01 Upgraded to 4.8.0-51.54 2017-05-16 Upgraded to 4.8.0-52.55 2017-05-25 Upgraded to 4.8.0-53.56 ← Errors on NVMe drive Parameter "nvme_core.default_ps_max_latency_us" is set to zero: 2017-05-29 Linux 4.8.0-53.56 (APST disabled) ← Running OK 2017-05-30 Linux 4.8.0-53.56 (APST disabled) ← Running OK 2017-05-31 Linux 4.8.0-53.56 (APST disabled) ← Errors on NVMe drive At this point, I switched from the Hardware Enablement (HWE) stack back to the original General Availability (GA) stack for the Linux kernel and X server on Ubuntu 16.04. 2017-05-31 Linux 4.4.0-78.90 (GA) ← Running OK so far 2017-06-01 Linux 4.4.0-78.90 (GA) ← Running OK so far I hope this change will help determine whether the errors are due to the drive itself or something in the Linux 4.8 upgrade. I guess we should close this bug report, or at least rename it. Thank you, John -- 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/1694596 Title: LiteOn NVMe APST issue Status in linux package in Ubuntu: Confirmed Bug description: Originally reported at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/79 The user uses "nvme_core.default_ps_max_latency_us=6000" but the issue still happens. $ sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x14a4 ssvid : 0x1b4b sn : TW0XVRV7LOH006AJ09F1 mn : CX2-8B256-Q11 NVMe LITEON 256GB fr : 48811QD rab : 0 ieee : 002303 cmic : 0 mdts : 5 cntlid : 1 ver : 10200 rtd3r : f4240 rtd3e : f4240 oaes : 0 oacs : 0x1f acl : 3 aerl : 3 frmw : 0x14 lpa : 0x2 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 358 cctemp : 368 mtfa : 50 hmpre : 0 hmmin : 0 tnvmcap : 256060514304 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0 vwc : 0x1 awun : 255 awupf : 7 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:4.00W operational enlat:5 exlat:5 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:2.10W operational enlat:5 exlat:5 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.1000W non-operational enlat:5000 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0100W non-operational enlat:5 exlat:10 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694596/+subscriptions -- Mailing list: https://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 1689360] Re: TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly calculating base_command_size
** Tags added: ubuntu-17.04
--
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/1689360
Title:
TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
calculating base_command_size
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
---Problem Description---
If there has BIDI data, its first iov[] will overwrite the last
iov[] for se_cmd->t_data_sg.
---uname output---
Latest Yakkety master branch
Machine Type = P8
---Steps to Reproduce---
Just have a system do workload using tcmu.
Stack trace output:
I have seen this in my environment:
(gdb) print *((tcmulib_cmd->iovec)+0)
$7 = {iov_base = 0x3fff7c3d, iov_len = 8192}
(gdb) print *((tcmulib_cmd->iovec)+1)
$3 = {iov_base = 0x3fff7c3da000, iov_len = 4096}
(gdb) print *((tcmulib_cmd->iovec)+2)
$4 = {iov_base = 0x3fff7c3dc000, iov_len = 16384}
(gdb) print *((tcmulib_cmd->iovec)+3)
$5 = {iov_base = 0x3fff7c3f7000, iov_len = 12288}
(gdb) print *((tcmulib_cmd->iovec)+4)
$6 = {iov_base = 0x1306e853c0028, iov_len = 128} <--- bad pointer and length
cmu: Fix wrongly calculating of the base_command_size
https://patchwork.kernel.org/patch/9687657/
tcmu: Fix possible overwrite of t_data_sg's last iov[]
https://patchwork.kernel.org/patch/9687565/
tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI
case
https://patchwork.kernel.org/patch/9655423/
This patch should also be a part of these fixes. WITH BIDI op fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689360/+subscriptions
--
Mailing list: https://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 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le
** Tags added: ubuntu-17.04 -- 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/1676884 Title: kdump-tools uses the wrong crashkernel command line parameter in ppc64le Status in The Ubuntu-power-systems project: New Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - Thiago Jung Bauermann - 2017-03-24 11:44:39 == ---Problem Description--- kdump-tools uses the wrong crashkernel command line parameter in ppc64le: u1704le?? grep crashkernel /boot/grub/grub.cfg linux /boot/vmlinux-4.10.0-13-generic root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro crashkernel=384M-:128M 128M of reserved memory is too small for ppc64le. That happens because /etc/default/grub.d/kdump-tools.cfg links to the wrong file: u1704le?? ls -l /etc/default/grub.d/ total 8.0K lrwxrwxrwx 1 root root 39 Mar 24 13:34 kdump-tools.cfg -> /etc/default/grub.d/kdump-tools.default -rw-r--r-- 1 root root 80 Jan 5 08:07 kdump-tools.default -rw-r--r-- 1 root root 137 Jan 5 08:07 kdump-tools..ppc64el u1704le?? As can be seen, it should be pointing to kdump-tools..ppc64el but isn't. Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right. Possibly just a cosmetic issue, but it would be nice if that was fixed. Contact Information = thiag...@br.ibm.com ---uname output--- Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 8286-42A. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- sudo apt intall kdump-tools Select 'Yes' when asked whether kdump should be enabled. Userspace tool common name: kdump The userspace tool has the following bit modes: 64 bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for thiag...@br.ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676884/+subscriptions -- Mailing list: https://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 1681909] Re: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.
** Tags added: ubuntu-17.04 -- 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/1681909 Title: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: New Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some errors in syslog ; auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question 114.15.239:/home/ubuntu/test IN SOA: failed-auxiliary Mar 7 04:57:44 lt
[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.
** Tags added: ubuntu-17.04 -- 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/1680349 Title: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 == ---Problem Description--- Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Machine hangs. ---Steps to Reproduce--- 1. Configure kdump. 2. Install stress-ng # apt-get install stress-ng 3. Run stress-ng # stress-ng - a 0 Logs: root@ltc-firep3:~# kdump-config load Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K * loaded kdump kernel root@ltc-firep3:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.10.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-firep3:~# stress-ng -a 0 stress-ng: info: [3900] defaulting to a 86400 second run per stressor stress-ng: info: [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 mlock, 1 60 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 1 60 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie stress-ng: info: [3900] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [3900] cache allocate: default cache size: 2048K stress-ng: info: [3907] stress-ng-atomic: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [3955] stress-ng-exec: running as root, won't run test. stress-ng: info: [3999] stress-ng-icache: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4040] stress-ng-lockbus: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4313] stress-ng-numa: system has 2 of a maximum 256 memory NUMA nodes stress-ng: info: [4455] stress-ng-rdrand: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: fail: [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 (Invalid argument) stress-ng: fail: [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed, errno=127 (Key has expired) stress-ng: fail: [4017]
[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c
** Tags added: ubuntu-17.04
--
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/1678745
Title:
Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Lata Kuntal - 2017-03-30 09:44:23 ==
Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running
few hours of regression test it dropped at xmon.
Console logs :
root@guskvm:~# virsh console gusg8 --force
Connected to domain gusg8
Escape character is ^]
1:mon> r
R00 = d288edf4 R16 = 024200ca
R01 = c000378cb1f0 R17 =
R02 = d2936080 R18 = 0020
R03 = 0001 R19 = c002734d1800
R04 = c000378cb190 R20 =
R05 = R21 =
R06 = 3c00d03fe056 R22 = c0027e26ccf0
R07 = R23 =
R08 = c48492d0 R24 =
R09 = 3c00d03fe056 R25 =
R10 = 3c00d03fe062 R26 = 00024df4cd49
R11 = d28fa360 R27 =
R12 = R28 = d28ac7b0
R13 = cfb80900 R29 = c4849000
R14 = R30 =
R15 = c137ad08 R31 =
pc = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
lr = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
msr = 80010280b033 cr = 82428424
ctr = c05e4950 xer = 2000 trap = 300
dar = 3c00d03fe062 dsisr = 4000
1:mon> t
[c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
[c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
[c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
[c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
[c000378cb430] c0276db8 shrink_node+0x158/0x3f0
[c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
[c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
[c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
[c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
[c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
[c000378cb920] c02a0770 do_wp_page+0x210/0xb20
[c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
[c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
[c000378cbb10] c0008948 handle_page_fault+0x10/0x30
--- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
[c000378cbe30] c0009844 ret_from_fork+0x4/0x54
--- Exception: c00 (System Call) at 3fffa2b5bf44
1:mon> d
||
1:mon> c
cpus stopped: 0x0-0x3
1:mon>
Kernel host build
=
root@guskvm:~# uname -r
4.10.0-13-generic
root@guskvm:~#
== Comment: #1 - Luciano Chavez - 2017-03-30 10:42:15 ==
At first glance, based on the following assembly from around the failure
point:
d288edd4 38c1 li r6,1
d288edd8 7f8802a6 mflrr28
d288eddc 78a70020 clrldi r7,r5,32
d288ede0 7c7d1b78 mr r29,r3
d288ede4 7c852378 mr r5,r4
d288ede8 386302c8 addir3,r3,712
d288edec 38810020 addir4,r1,32
d288edf0 4806b571 bl d28fa360#
exit_xfs_fs+0x180c/0xfd44 [xfs]
d288edf4 e8410018 ld r2,24(r1)
d288edf8 2f83 cmpwi cr7,r3,0
d288edfc 409d0104 ble cr7,d288ef00#
xfs_perag_get_tag+0x160/0x170 [xfs]
d288ee00 7c0004ac sync
d288ee04 e9210020 ld r9,32(r1)
d288ee08 3949000c addir10,r9,12
d288ee0c 7fc05028 lwarx r30,0,r10
d288ee10 33de0001 addic r30,r30,1
d288ee14 7fc0512d stwcx. r30,0,r10
I believe the crash in fs_perag_get_tag() is after we come back from
the radix_tree_gang_lookup_tag() call and are attempting the
atomic_inc_return() and struct xfs_perag*pag is R09 =
3c00d03fe056 which is invalid.
85 rcu_read_lock();
86 found = radix_tree_gang_lookup_tag(&mp->m_perag_tree,
87 (void **)&pag, first, 1, tag);
[Kernel-packages] [Bug 1685792] Re: Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu 17.04)
** Tags added: ubuntu-17.04
--
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/1685792
Title:
Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu
17.04)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
== Comment: #0 - Ranjal G. Shenoy - 2017-04-20 08:29:13
==
Power9 DD1 has a hardware issue due to which in core whose all threads are
offlined , when any of the CPUs are onlined, they come online with an incorrect
PACA thereby resulting in a crash.
The following fixes sent upstream need to applied to the 17.04 kernel
to get CPU-Hotplug working correctly on a Power9 DD1 system.
1) powerpc/linux.git next, commit a7cd88da9704 ("powernv: Move CPU-
Offline idle state invocation from smp.c to idle.c").
2) powerpc/linux.git next, the commit 900612315788
("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-
Hotplug").
3) powerpc/linux.git, commit f3b3f28493d932 ("powerpc/powernv/idle:
Don't override default/deepest directly in kernel").
4) powerpc/linux.git next, commit 17ed4c8f81da ("powerpc/powernv:
Recover correct PACA on wakeup from a stop on P9 DD1").
These patches have been backported onto the 17.04 Kernel tagged
Ubuntu-4.10.0-19.21.
== Comment: #1 - Ranjal G. Shenoy - 2017-04-20
08:29:54 ==
== Comment: #2 - Ranjal G. Shenoy - 2017-04-20 08:30:37
==
== Comment: #3 - Ranjal G. Shenoy - 2017-04-20 08:31:15
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1685792/+subscriptions
--
Mailing list: https://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 1689980] Re: AACRAID for power9 platform
** Tags added: ubuntu-17.04 -- 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/1689980 Title: AACRAID for power9 platform Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: Hello team, It seems Microsemi team has requested to backport few AACRAID driver patches for Power 9 platform for 17.04 and 16.04.3 kernel. Hi Narinder, We have submitted a handful of critical fixes for the AACRAID driver on to the kernel.org, targeting 4.11. These patches are bug fixes and our customer IBM is expecting these patches to go into the 16.04.3 release, for to use with the Power9 platforms. Can you please let me know if these patches will be backported by your kernel team on to the upcoming 16.04.3? Do you also have a schedule in place for 16.04.3 release? Thanks, Gana Below are the patch details. Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc fixes This patchset primarily focuses on tweaking and hardening the controller reset support for both ARC and HBA1000 devices. Now the driver can only reset the controller thru eh reset. Included a srb memory fix and pci dma allocation fix. Changes in V2: - Corrected heading and description for srb memory patch and removed stray comment. - Removed incorrect up function call and cleared fib wait flag after call to down interruptible in the ioctl return on ctrl reset patch. - Added review acknowledgements by David Carroll thank you Dave for finding the above issues in the above 2 patches. Raghava Aditya Renukunta (19): [SCSI] aacraid: Remove __GFP_DMA for raw srb memory [SCSI] aacraid: Fix DMAR issues with iommu=pt [SCSI] aacraid: Added 32 and 64 queue depth for arc natives [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks [SCSI] aacraid: Remove reset support from check_health [SCSI] aacraid: Change wait time for fib completion [SCSI] aacraid: Log count info of scsi cmds before reset [SCSI] aacraid: Print ctrl status before eh reset [SCSI] aacraid: Using single reset mask for IOP reset [SCSI] aacraid: Rework IOP reset [SCSI] aacraid: Add periodic checks to see IOP reset status [SCSI] aacraid: Rework SOFT reset code [SCSI] aacraid: Rework aac_src_restart [SCSI] aacraid: Use correct function to get ctrl health [SCSI] aacraid: Make sure ioctl returns on controller reset [SCSI] aacraid: Enable ctrl reset for both hba and arc [SCSI] aacraid: Add reset debugging statements [SCSI] aacraid: Remove reference to Series-9 [SCSI] aacraid: Update driver version to 50834 drivers/scsi/aacraid/aachba.c | 17 ++- drivers/scsi/aacraid/aacraid.h | 22 +++- drivers/scsi/aacraid/commctrl.c | 15 ++- drivers/scsi/aacraid/comminit.c | 18 +--- drivers/scsi/aacraid/commsup.c | 78 +++--- drivers/scsi/aacraid/linit.c| 232 drivers/scsi/aacraid/src.c | 136 +-- 7 files changed, 298 insertions(+), 220 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689980/+subscriptions -- Mailing list: https://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 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces
** Tags added: ubuntu-17.04 -- 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/1664545 Title: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces Status in The Ubuntu-power-systems project: New Status in makedumpfile package in Ubuntu: New Bug description: In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on guest while kdump process console got hung having call traces Reproducible Step: 1- Install Ubuntu17.04 as kvm guest on ubuntu kvm host 2- configure kdump 3- trigger kdump Expected Result : Kdump should capture Actual Result : Kdump console hung having continuous call traces LOG: [0.488534] Freeing unused kernel memory: 4416K (c8e8 - c92d) [0.488725] This architecture does not have kernel memory protection. Loading, please wait... starting version 232 [0.501616] random: udevadm: uninitialized urandom read (16 bytes read) [0.501830] random: udevadm: uninitialized urandom read (16 bytes read) [0.501981] random: udevadm: uninitialized urandom read (16 bytes read) [0.502162] random: udevadm: uninitialized urandom read (16 bytes read) [0.502254] random: udevadm: uninitialized urandom read (16 bytes read) [0.502433] random: udevadm: uninitialized urandom read (16 bytes read) [0.503188] random: udevadm: uninitialized urandom read (16 bytes read) [0.503270] random: udevadm: uninitialized urandom read (16 bytes read) [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes read) [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds. [ 242.663514] Not tainted 4.9.0-15-generic #16-Ubuntu [ 242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663755] systemd-udevd D0 151145 0x00040002 [ 242.663795] Call Trace: [ 242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0 [ 242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990 [ 242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0 [ 242.664179] [c0001fe4ee40] [c8b1de54] schedule_timeout+0x274/0x470 [ 242.664334] [c0001fe4ef30] [c8b19010] io_schedule_timeout+0xd0/0x160 [ 242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90 [ 242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170 [ 242.664754] [c0001fe4f000] [c824b238] wait_on_page_bit+0x98/0xb0 [ 242.664847] [c0001fe4f060] [c824d60c] do_read_cache_page+0x21c/0x4e0 [ 242.665008] [c0001fe4f0d0] [c859be78] read_dev_sector+0xb8/0x140 [ 242.665126] [c0001fe4f100] [c85a5d88] read_lba.isra.0+0x148/0x250 [ 242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830 [ 242.665363] [c0001fe4f2e0] [c859e768] check_partition+0x158/0x2d0 [ 242.665469] [c0001fe4f360] [c859c760] rescan_partitions+0xe0/0x390 [ 242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490 [ 242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0 [ 242.665784] [c0001fe4f550] [c8599538] device_add_disk+0x4a8/0x500 [ 242.665894] [c0001fe4f600] [d0511cc8] virtblk_probe+0x560/0x928 [virtio_blk] [ 242.665983] [c0001fe4f6c0] [c8687700] virtio_dev_probe+0x1d0/0x350 [ 242.666050] [c0001fe4f700] [c8716f30] driver_probe_device+0x240/0x540 [ 242.666116] [c0001fe4f790] [c871738c] __driver_attach+0x15c/0x160 [ 242.666174] [c0001fe4f810] [c87138ec] bus_for_each_dev+0x8c/0xf0 [ 242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50 [ 242.666289] [c0001fe4f880] [c8715a78] bus_add_driver+0x238/0x380 [ 242.666345] [c0001fe4f910] [c871829c] driver_register+0x9c/0x180 [ 242.666403] [c0001fe4f980] [c8686abc] register_virtio_driver+0x4c/0x60 [ 242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 [virtio_blk] [ 242.666527] [c0001fe4fa10] [c800dde8] do_one_initcall+0x68/0x1d0 [ 242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244 [ 242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0 [ 242.666701] [c0001fe4fd30] [c8184c60] SyS_finit_module+0xf0/0x170 [ 242.666759] [c0001fe4fe30] [c800bd84] system_call+0x38/0xe0 [ 363.701100
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
** Tags added: ubuntu-16.04 -- 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/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://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 1667245] Re: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR
** Tags added: ubuntu-17.04 -- 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/1667245 Title: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- After a memory DLPAR removal, kdump doesn't work: Starting Kernel crash dump capture service... [ 67.714593] kdump-tools[3850]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete Copying data : [ 2.1 %] -/usr/sbin/kdump-config: line 639: 3897 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 72.314140] kdump-tools[3850]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad address [ 73.704152] kdump-tools[3850]: * kdump-tools: failed to save vmcore in /var/crash/201702230005 [ 73.823643] kdump-tools[3850]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201702230005/dmesg.201702230005 [ 73.973813] kdump-tools[3850]: The kernel version is not supported. [ 73.974078] kdump-tools[3850]: The makedumpfile operation may be incomplete. [ 73.983506] kdump-tools[3850]: The dmesg log is saved to /var/crash/201702230005/dmesg.201702230005. [ 73.983752] kdump-tools[3850]: makedumpfile Completed. [ 73.983998] kdump-tools[3850]: * kdump-tools: saved dmesg content in /var/crash/201702230005 [ 74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600 [ 74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No such file or directory [ 74.233782] kdump-tools[3850]: Rebooting. [ 86.629777] reboot: Restarting system The kdump service should be restarted after the memory DLPAR operation. C ---uname output--- Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. do a memory DLPAR removal operation 3. trigger kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1667245/+subscriptions -- Mailing list: https://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 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac
The fix was included on Zesty kernel 4.10.0-22.24, the netboot installer is loading 4.10.0-19, which is probably the GA kernel. I'm trying to find some sort of daily netboot build so it can be tested with the latest 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/1677297 Title: [Zesty] d-i: replace msm_emac with qcom_emac Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Committed Bug description: [Impact] We landed a patch to support msm_emac module in initrd for amberwing platforms. But the upstream driver has since been renamed to qcom_emac. This module is needed in d-i's initrd so that these nics can be used to d-i install the system. The driver already exists in the zesty kernel under drivers/net/ethernet/qualcomm/emac/ Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add qcom_emac to initrd, and change the module name to qcom_emac. [Test Case] D-I install zesty on amberwing platform and notice that DI does not recognize the onboard two port nic. [Regression Potential] At present this driver applies only to amberwing systems, any regression will be isolated to amberwing platforms. The over all risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+subscriptions -- Mailing list: https://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 1690094] Re: linux <3.18: netlink notification is missing when an interface is modified
My tests are ok, thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690094 Title: linux <3.18: netlink notification is missing when an interface is modified Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690094/+subscriptions -- Mailing list: https://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 1694996] 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/1694996 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Update stops about half way through and never finishes. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1836 F pulseaudio Date: Wed May 31 11:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1532:0043 Razer USA, Ltd Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=52878891-7f1a-4352-b0e1-754c5cf639ec 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 N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 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: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.213:bd10/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL552VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694996/+subscriptions -- Mailing list: https://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 lekshmi.cpil...@in.ibm.com 2017-05-31 23:49 EDT--- Hi I am running tets for 10 days.No issues with the kernel root@lucky05:/Blast# uname -r 4.4.0-78-generic root@lucky05:/Blast# Its working fine Thanks Lekshmi -- 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: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: 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]
