[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M
Tested again with a fresh install of Ubuntu 18.04. Linux kernel version 4.15.0-20 The boot freeze is still here, it happens just after giving my password, exactly when clicking on "login" (Gnome Desktop environment). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M Status in linux package in Ubuntu: Incomplete Bug description: When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX 950M" and a "Intel HD Graphics 530" graphic card, the boot process freezes. The cause is that the current Linux kernel does not include FOSS drivers for "Nvidia Geforce GTX 950M". The solution to avoid that freeze is to add the "nomodeset" grub boot parameter or to install the proprietary Nvidia driver. My concern is that you have to be aware of that circumvent when installing Ubuntu OS for the first time. I think that it would be more logical that the Linux kernel uses the low performance graphic card "Intel HD Graphics 530" by default, without trying to use "Nvidia Geforce GTX 950M" which is not natively supported. That would avoid the bad experience of boot freeze at first meeting. Computer : Model = Asus N752VX-GC164T Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: user 1861 F...m pulseaudio /dev/snd/controlC0: user 1861 F pulseaudio DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-13 (92 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0461:4d22 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N752VX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=5b9acdb6-aa5b-4801-8cd6-40621a2028d4 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 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.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: artful Uname: Linux 4.13.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N752VX.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N752VX 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.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N752VX 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/1764286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Is there reason to believe that bluez (the bluetoothd process) is involved here? If the problem is low-level bluetooth then the correct package to log that against is 'linux'. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in bluez package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
No USN needed. ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767857] 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/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu- system-x86: black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Boot the same system with kernel 4.4.0-119 and qemu- system-x86 works fine running a Windows 10 VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic i686 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 29 15:58:25 2018 InstallationDate: Installed on 2014-04-29 (1460 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 394 2 0.0 [kvm-irqfd-clean] MachineType: Dell Inc. Inspiron 518 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash nmi_watchdog=0 SourcePackage: qemu UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago) dmi.bios.date: 03/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0K068D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 518 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
Also a per qemu thread view is often useful, you might also add $ pidstat -t -p Further since this is reported as kernel update regression I'll flag it as that for now. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu- system-x86: black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Boot the same system with kernel 4.4.0-119 and qemu- system-x86 works fine running a Windows 10 VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic i686 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 29 15:58:25 2018 InstallationDate: Installed on 2014-04-29 (1460 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 394 2 0.0 [kvm-irqfd-clean] MachineType: Dell Inc. Inspiron 518 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash nmi_watchdog=0 SourcePackage: qemu UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago) dmi.bios.date: 03/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0K068D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 518 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Also reported on Solus [https://dev.solus-project.com/T5224], Manjaro [https://forum.manjaro.org/t/high-cpu-usage-on-kernel-4-14-and-4-15 -from-systemd-udevd-which-seems-to-be-the-synaptic-touchpad- driver/35972] and Gentoo (on the Manjaro page). -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in bluez package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
A quick workaround is rmmod btusb before suspend and insert btusb after resume. To do this, you can put a executable script of any name in /lib/systemd/system-sleep/. Example: #!/bin/sh if [ "$1" = "pre" ]; then systemctl stop bluetooth && rmmod btusb elif [ "$1" = "post" ]; then modprobe btusb && systemctl start bluetooth fi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
** Description changed: + ===SRU Justification=== + [Impact] + When TBT ICM firmware is not running properly, it may crash the kernel. + + [Fix] + Protect against cases when ICM is not set. + + [Test] + User confirmed the additional patch works. + + [Regression Potential] + Low. It adds a simple logic to avoid NULL dereference. + + ===Original Bug Report=== + Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina - May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on - May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on + May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on + May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 - May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 + May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 Ma
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
** Bug watch added: Linux Kernel Bug Tracker #199035 https://bugzilla.kernel.org/show_bug.cgi?id=199035 ** Also affects: kernel via https://bugzilla.kernel.org/show_bug.cgi?id=199035 Importance: Unknown Status: Unknown ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=199035 Importance: Unknown Status: Unknown ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in bluez package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] /var/log/syslog boslcp3 host
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:51 EDT--- Attached /var/log/syslog file from boslcp3 host ** Attachment added: "/var/log/syslog boslcp3 host" https://bugs.launchpad.net/bugs/1762844/+attachment/5132697/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c000
[Kernel-packages] [Bug 1762844] /var/log/syslog1.file boslcp3
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:53 EDT--- Attached /var/log/syslog.1 file from boslcp3 host ** Attachment added: "/var/log/syslog1.file boslcp3" https://bugs.launchpad.net/bugs/1762844/+attachment/5132698/+files/syslog.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0]
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
I can reproduce it only on AC mode. Still can reproduce it after disable tlp. kernel: 4.4.0-100 BIOS: 1.2.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets.
[Kernel-packages] [Bug 1326761] Re: Tevii S471 DVB-S2 card hangs on firmware upload
The quickest way to find it is to do a kernel bisection [0]. [0] https://wiki.ubuntu.com/Kernel/KernelBisection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326761 Title: Tevii S471 DVB-S2 card hangs on firmware upload Status in linux package in Ubuntu: Confirmed Bug description: I have fresh installed Ubuntu Trusty Tahr (Server) with kernel 3.13.0-29. Firmware file dvb-fe-ds3000.fw is putted into /lib/firmware On a system cold start I see in syslog: Jun 5 16:00:54 MMC kernel: [9.601460] cx23885 driver version 0.0.3 loaded Jun 5 16:00:54 MMC kernel: [9.601881] CORE cx23885[0]: subsystem: d471:9022, board: TeVii S471 [card=35,autodetected] Jun 5 16:00:54 MMC kernel: [9.750010] cx23885_dvb_register() allocating 1 frontend(s) Jun 5 16:00:54 MMC kernel: [9.758499] cx23885[0]: cx23885 based dvb card Jun 5 16:00:54 MMC kernel: [9.879035] DVB: registering new adapter (cx23885[0]) Jun 5 16:00:54 MMC kernel: [9.879047] cx23885 :01:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)... Jun 5 16:00:54 MMC kernel: [9.894578] cx23885_dev_checkrevision() Hardware revision = 0xa5 Jun 5 16:00:54 MMC kernel: [9.894595] cx23885[0]/0: found at :01:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xfe80 But if I try to scan channels by scan or tvheadend I see this repeated lines: Jun 5 16:01:04 MMC kernel: [ 20.051633] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... Jun 5 16:01:04 MMC kernel: [ 20.052608] ds3000_firmware_ondemand: Waiting for firmware upload(2)... Card works under Debian linux kernel image from unstable repo (linux- image-3.14.1) manjur@MMC:~$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 manjur@MMC:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 3.13.0.29.35 Candidate: 3.13.0.29.35 Version table: *** 3.13.0.29.35 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.13.0.27.33 0 500 http://kz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 3.13.0.24.28 0 500 http://kz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.52 ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Jun 5 17:31:07 2014 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=e93b9d23-aced-4d3c-bb1e-07346406d8de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: E350M1/USB3 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.60:bd05/21/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnE350M1/USB3: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] sol console log
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04 EDT--- ** Attachment added: "sol console log" https://bugs.launchpad.net/bugs/1762844/+attachment/5132668/+files/boslcp3.0421.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c00
[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 EDT--- Attached consolel logs for step(3) & step(4) ** Attachment added: "boslcp3 crashed_used X from xmon prompt" https://bugs.launchpad.net/bugs/1762844/+attachment/5132672/+files/boslcp3_usedX_xmonprompt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/
[Kernel-packages] [Bug 1762844] boslcp3g3 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g3 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132670/+files/boslcp3g3.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3g4 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 EDT--- ** Attachment added: "boslcp3g4 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132671/+files/boslcp3g4.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3g1 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g1 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132669/+files/boslcp3g1.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3 host console tee logs
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:22 EDT--- Attached boslcp3 host console tee logs ** Attachment added: "boslcp3 host console tee logs" https://bugs.launchpad.net/bugs/1762844/+attachment/5132677/+files/boslcp3-host-may1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9
[Kernel-packages] [Bug 1762844] dmesg log thus far, for May 1 run.
--- Comment (attachment only) From dougm...@us.ibm.com 2018-05-02 14:28 EDT--- ** Attachment added: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/bugs/1762844/+attachment/5132694/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[Kernel-packages] [Bug 1762844] boslcp3g4 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 EDT--- ** Attachment added: "boslcp3g4 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132689/+files/boslcp3g4.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3 host console tee logs
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:22 EDT--- Attached boslcp3 host console tee logs ** Attachment added: "boslcp3 host console tee logs" https://bugs.launchpad.net/bugs/1762844/+attachment/5132695/+files/boslcp3-host-may1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9
[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 EDT--- Attached boslcp3 host console logs for step (5) ** Attachment added: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/bugs/1762844/+attachment/5132691/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c
[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k
--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 EDT--- ** Attachment added: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/bugs/1762844/+attachment/5132692/+files/qla2xxx-10.00.00.04-k.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_
[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 EDT--- Attached consolel logs for step(3) & step(4) ** Attachment added: "boslcp3 crashed_used X from xmon prompt" https://bugs.launchpad.net/bugs/1762844/+attachment/5132690/+files/boslcp3_usedX_xmonprompt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/
[Kernel-packages] [Bug 1762844] dmesg log_boslcp3_latest for may1 run
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:49 EDT--- Attached latest dmesg log for boslcp3 - may1st run ** Attachment added: "dmesg log_boslcp3_latest for may1 run" https://bugs.launchpad.net/bugs/1762844/+attachment/5132696/+files/dmesg_boslcp3_may3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build
--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 EDT--- Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build (in this case, a patched skiroot's kernel -- zImage.epapr), per Dwip's request. Hopefully this might help others in the future. (In reply to comment #203) > The skiroot kernel build is available at: > > http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage. > epapr_4.15.14-openpower1.bz166588c132 ** Attachment added: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/bugs/1762844/+attachment/5132693/+files/file_166588.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a
[Kernel-packages] [Bug 1762844] boslcp3g3 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g3 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132688/+files/boslcp3g3.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 EDT--- Attached boslcp3 host console logs for step (5) ** Attachment added: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/bugs/1762844/+attachment/5132673/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c
[Kernel-packages] [Bug 1762844] console log
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-20 20:08 EDT--- ** Attachment added: "console log" https://bugs.launchpad.net/bugs/1762844/+attachment/5132667/+files/boslcp3.0420.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000200
[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build
--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 EDT--- Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build (in this case, a patched skiroot's kernel -- zImage.epapr), per Dwip's request. Hopefully this might help others in the future. (In reply to comment #203) > The skiroot kernel build is available at: > > http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage. > epapr_4.15.14-openpower1.bz166588c132 ** Attachment added: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/bugs/1762844/+attachment/5132675/+files/file_166588.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a
[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k
--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 EDT--- ** Attachment added: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/bugs/1762844/+attachment/5132674/+files/qla2xxx-10.00.00.04-k.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_
[Kernel-packages] [Bug 1762844] dmesg log thus far, for May 1 run.
--- Comment (attachment only) From dougm...@us.ibm.com 2018-05-02 14:28 EDT--- ** Attachment added: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/bugs/1762844/+attachment/5132676/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[Kernel-packages] [Bug 1762844] boslcp3 host console logs_4.15.0-15 kernel
Default Comment by Bridge ** Attachment added: "boslcp3 host console logs_4.15.0-15 kernel" https://bugs.launchpad.net/bugs/1762844/+attachment/5132659/+files/boslcp3_hostconsolelogs_4.15.0-15kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000200e0b20
[Kernel-packages] [Bug 1762844] dmesg output 0418
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-18 12:01 EDT--- ** Attachment added: "dmesg output 0418" https://bugs.launchpad.net/bugs/1762844/+attachment/5132666/+files/dmesg.201804181042 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[Kernel-packages] [Bug 1762844] boslcp3_crash_aprl13
--- Comment (attachment only) From indira.pr...@in.ibm.com 2018-04-13 03:24 EDT--- ** Attachment added: "boslcp3_crash_aprl13" https://bugs.launchpad.net/bugs/1762844/+attachment/5132663/+files/boslcp3_crash_aprl13.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+
[Kernel-packages] [Bug 1762844] Second attempt of host reboot_boslcp3
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-12 11:13 EDT--- Attached boslcp3 host console logs during 2nd attempt of reboot ** Attachment added: "Second attempt of host reboot_boslcp3" https://bugs.launchpad.net/bugs/1762844/+attachment/5132661/+files/Secong_attempt_of_reboot_boslcp3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c000
[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 EDT--- Attached dl logs from xmon pormpt _boslcp3 ** Attachment added: "dmesg logs from xmon prompt_boslcp3" https://bugs.launchpad.net/bugs/1762844/+attachment/5132665/+files/dmesg_xmon_boslcp3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c00
[Kernel-packages] [Bug 1762844] First attempt of host reboot_boslcp3
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-12 11:12 EDT--- Attached boslcp3 host console logs during 1st attempt of host reboot ** Attachment added: "First attempt of host reboot_boslcp3" https://bugs.launchpad.net/bugs/1762844/+attachment/5132660/+files/first_attempt_of_host_reboot_boslcp3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c
[Kernel-packages] [Bug 1762844] Host console log
--- Comment on attachment From chngu...@us.ibm.com 2018-04-13 17:17 EDT--- The full log of the Host during couple reboot, start test on guest then system drop into xmon. ** Attachment added: "Host console log" https://bugs.launchpad.net/bugs/1762844/+attachment/5132664/+files/boslcp3.0413.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __all
[Kernel-packages] [Bug 1762844] boslcp3 host crash console logs
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-12 14:25 EDT--- Attached boslcp3 host crash console logs ** Attachment added: "boslcp3 host crash console logs" https://bugs.launchpad.net/bugs/1762844/+attachment/5132662/+files/host_crash_boslcp3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0
[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
--- Comment From indira.pr...@in.ibm.com 2018-05-02 23:21 EDT--- Attached host boslcp3 host console tee logs. ** Tags added: bugnameltc-166588 severity-critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000200e0b20fa30] c0b247cc sock_alloc_send
[Kernel-packages] [Bug 1763271] Re: [8086:3e92] display becomes blank after S3
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1763271 Title: [8086:3e92] display becomes blank after S3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: [Impact] The display becomes black after S3 with the following error messages. dmesg: [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at link rate = 54, lane count = 4 Xorg.0.log: [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, tried resetting the current mode. You may be left with a black screen if this fails... [Fix] Looks like link training fallback fails sometimes with eDP, we need this commit to fix the issue. commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad) Author: Manasi Navare Date: Thu Oct 12 12:13:38 2017 -0700 drm/i915/edp: Do not do link training fallback or prune modes on EDP [Regression Potential] Should be low. To avoid conflicts, we introduce 4 commits, I'll try explaining them below a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP This is the fix commit and the behavior only changes when DP is eDP, it does nothing if DP is eDP. Should be fine to not do link training fallback and not emit Hotplug Uevent to userspace to start modeset, since its eDP, the display is fixed. 1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp 7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp Above 2 commits do function name renaming only. dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available. Change the prototype of function "intel_panel_init()" and adding one extra argument, should have small impact on the display. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1763271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs
I read an article here https://serverfault.com/questions/616485/e1000e- reset-adapter-unexpectedly-detected-hardware-unit- hang?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa which stated some people had had success preventing this by disabling hardware offloading with ethtool -K eth0 gso off gro off tso off. With the 4.15.0-21-lowlatency #22-Ubuntu SMP PREEMPT Tue May 1 15:47:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux kernel on the i7-6850 machine which has been the most problematic, I did this and have not had a hang since. Obviously this comes with a performance penalty so is undesirable as a permanent fix but hoping this might help narrow the cause. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766377 Title: Ethernet E1000 Controller Hangs Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic hanging of the LAN connection. This is happening on an Asus X99-DELUX motherboard, controller specifications: Intel® I218V, 1 x Gigabit LAN Controller(s) Intel® I211-AT, 1 x Gigabit LAN Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) appliance Support Teaming Technology ASUS Turbo LAN Utility The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM. This machine has a number of Qemu/KVM virtual guests and is using a software bridge to share the interface. This did not happen with 17.10 and 4.13.0 kernel. It is happening on multiple machines here. Here are the messages from dmesg: 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d0880> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d1040> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly [1016202.413701] bridge0: port 1(eno1) entered disabled state [1016202.413732] bridge0: topology change detected, propagating [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [1016206.666708] bridge0: port 1(eno1) entered blocking state [1016206.666712] bridge0: port 1(eno1) entered listening state [1016216.750911] bridge0: port 1(eno1) entered learning state [1016232.110291] bridge0: port 1(eno1) entered forwarding state [1016232.110294] bridge0: topology change detected, sending tcn bpdu [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for regulatory database [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [1017834.414792] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [1017834.414794] cfg80211: failed to load regulatory.db If there is any other information I can provide to aid in resolution, please contact me, nan...@eskimo.com. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with e
[Kernel-packages] [Bug 1763644] Re: Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware
This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
---
linux-snapdragon (4.4.0-1090.95) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1090.95 -proposed tracker (LP: #1763689)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
[ Ubuntu: 4.4.0-121.145 ]
* linux: 4.4.0-121.145 -proposed tracker (LP: #1763687)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config] arm64: disable BPF_JIT_ALWAYS_ON
linux-snapdragon (4.4.0-1089.94) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1089.94 -proposed tracker (LP: #1761448)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel)
- Revert "x86/mm: Only set IBPB when the new thread cannot ptrace current
thread"
- x86/speculation: Use Indirect Branch Prediction Barrier in context switch
* DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please
install libelf-dev, libelf-devel or elfutils-libelf-devel (LP: #1760876)
- [Packaging] include the retpoline extractor in the headers
* retpoline hints: primary infrastructure and initial hints (LP: #1758856)
- [Packaging] retpoline-extract: flag *0xNNN(%reg) branches
- x86/speculation, objtool: Annotate indirect calls/jumps for objtool
- x86/speculation, objtool: Annotate indirect calls/jumps for objtool on
32bit
- x86/paravirt, objtool: Annotate indirect calls
- x86/asm: Stop depending on ptrace.h in alternative.h
- [Packaging] retpoline -- add safe usage hint support
- [Packaging] retpoline-check -- only report additions
- [Packaging] retpoline -- widen indirect call/jmp detection
- [Packaging] retpoline -- elide %rip relative indirections
- [Packaging] retpoline -- clear hint information from packages
- SAUCE: modpost: add discard to non-allocatable whitelist
- KVM: x86: Make indirect calls in emulator speculation safe
- KVM: VMX: Make indirect call speculation safe
- x86/boot, objtool: Annotate indirect jump in secondary_startup_64()
- SAUCE: early/late -- annotate indirect calls in early/late initialisation
code
- SAUCE: vga_set_mode -- avoid jump tables
- [Config] retpoline -- switch to new format
- [Packaging] final-checks -- remove check for empty retpoline files
* Xenial update to 4.4.117 stable release (LP: #1756860)
- IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH
ports
- PM / devfreq: Propagate error from devfreq_add_device()
- s390: fix handling of -1 in set{,fs}[gu]id16 syscalls
- ARM: dts: STi: Add gpio polarity for "hdmi,hpd-gpio" property
- arm: spear600: Add missing interrupt-parent of rtc
- arm: spear13xx: Fix dmas cells
- arm: spear13xx: Fix spics gpio controller's warning
- ALSA: seq: Fix regression by incorrect ioctl_mutex usages
- KVM/x86: Reduce retpoline performance impact in slot_handle_level_range(),
by always inlining iterator helper methods
- x86/cpu: Change type of x86_cache_size variable to unsigned int
- drm/radeon: adjust tested variable
- rtc-opal: Fix handling of firmware error codes, prevent busy loops
- ext4: save error to disk in __ext4_grp_locked_error()
- ext4: correct documentation for grpid mount option
- mm: hide a #warning for COMPILE_TEST
- video: fbdev: atmel_lcdfb: fix display-timings lookup
- console/dummy: leave .con_font_get set to NULL
- rtlwifi: rtl8821ae: Fix connection lost problem correctly
- Btrfs: fix deadlock in run_delalloc_nocow
- Btrfs: fix crash due to not cleaning up tree log block's dirty bits
- Btrfs: fix unexpected -EEXIST when creating new inode
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute
- ALSA: hda/realtek: PCI quirk for Fujitsu U7x7
- ALSA: usb-audio: add implicit fb quirk for Behringer UFX1204
- ALSA: seq: Fix racy pool initializations
- mvpp2: fix multicast address filter
- dm: correctly handle chained bios in dec_pending()
- x86: fix build warnign with 32-bit PAE
- vfs: don't do RCU lookup of empty pathnames
- ARM: pxa/tosa-bt: add MODULE_LICENSE tag
- ARM: dts: s5pv210: add interrupt-parent for ohci
- media: r820t: fix r820t_write_reg for KASAN
- Linux 4.4.117
* zfs system process hung on container stop/delete (LP: #1754584)
- SAUCE: (noup) zfs to 0.6.5.6-0ubuntu19
- SAUCE: Fix non-prefaulted page deadlock (LP: #1754584)
* apparmor: fix bad __initdata tagging on, apparmor_initialized (LP: #1758471)
- SAUCE: apparmor: fix bad __initdata tagging on, apparmor_initialized
* Xenial update to 4.4.116 stable release (LP: #1756121)
- po
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
Your bug 1759849 was definitely a duplicate of bug 1748450, so the remaining problem here must be a different bug... Please goto comment #26 :) ** This bug is no longer a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725859] Re: zfs frequently hangs (up to 30 secs) during sequential read
Hello Colin, I set a couple of ZFS options a day or two ago, and have bee playing videos to see if we still have the problem. The options I set were: o zfs set xattr=sa storage o zfs set xattr=sa storage/vault o zfs set ralatime=on storage o zfs set ralatime=on storage/vault We've played about four hours of video, and we have not seen the hang. Do you still want to pursue this? I could set the options back and do the trace or leave the options and do the trace, or should we just consider this fixed? My only concern about the latter option is that the installation was a default install with Ubuntu 17.10 and it seems these options should be the default on any linux distro. Let me know what you want to do? Best regards, Colin. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1725859 Title: zfs frequently hangs (up to 30 secs) during sequential read Status in zfs-linux package in Ubuntu: Incomplete Bug description: Updated to artful (17.10) yesterday. Trying to read (play video) from mirrored ZFS disks from an external USB 3 enclosure. Zpool is defined as: root@hetty:/home/crlb# zpool status pool: storage state: ONLINE scan: resilvered 20K in 0h0m with 0 errors on Fri Oct 20 18:38:49 2017 config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 errors: No known data errors root@hetty:/home/crlb# Found that I could re-create the problem with: rsync -av --progress Also found that: dd if=/dev/sdX of=/dev/null status=progress bs=1024 count=1000 Where "X" is either "b" or "c" does not hang. Installed: root@hetty:/home/crlb# apt list --installed | grep -i zfs libzfs2linux/artful,now 0.6.5.11-1ubuntu3 amd64 [installed,automatic] zfs-zed/artful,now 0.6.5.11-1ubuntu3 amd64 [installed,automatic] zfsutils-linux/artful,now 0.6.5.11-1ubuntu3 amd64 [installed] root@hetty:/home/crlb# Help please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1725859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
I have same problem. Linux UbuntuPC 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0) 00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0) 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0) 00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0) 00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0) 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a2c9 00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio 00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] (rev 87) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 07:00.0 USB controller: ASMedia Technology Inc. Device 2142 08:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81) Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Stepping:10 CPU MHz: 824.102 CPU max MHz: 4700. CPU min MHz: 800. BogoMIPS:7392.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:12288K NUMA node0 CPU(s): 0-11 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves ibpb ibrs stibp dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID b58e:9e84 Blue Microphones Yeti Stereo Microphone Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+attachment/5132533/+files/lshw.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://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 1766308] Re: inexplicably large file reported by zfs filesystem
Zero-filled data is not compressed by the set compression algorithm but gets filtered by zero-length encoding, so the zeros never hit lz4 and compressratio does not include them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem Status in zfs-linux package in Ubuntu: Triaged Bug description: I have a zfs filesystem containing a single qemu kvm disk image. The vm has been working normally. The image file is only allocated 10G, however today I became aware that the file, when examined from the ZFS host (hypervisor) is reporting an inexplicable, massive file size of around 12T. 12T is larger than the pool itself. Snapshots or other filesystem features should not be involved. I'm suspicious that the file(system?) has been corrupted. root@fusion:~# ls -l /data/store/vms/plexee/ total 6164615 -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root ^^ !! root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root image: /data/store/vms/plexee//plexee-root file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 5.9G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee NAME USED AVAIL REFER MOUNTPOINT rpool/DATA/fusion/store/vms/plexee 5.88G 484G 5.88G /data/store/vms/plexee root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee NAMEPROPERTY VALUE SOURCE rpool/DATA/fusion/store/vms/plexee type filesystem - rpool/DATA/fusion/store/vms/plexee creation Mon Mar 26 9:50 2018 - rpool/DATA/fusion/store/vms/plexee used 5.88G - rpool/DATA/fusion/store/vms/plexee available 484G - rpool/DATA/fusion/store/vms/plexee referenced5.88G - rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee mounted yes - rpool/DATA/fusion/store/vms/plexee quota none default rpool/DATA/fusion/store/vms/plexee reservation none default rpool/DATA/fusion/store/vms/plexee recordsize128K default rpool/DATA/fusion/store/vms/plexee mountpoint /data/store/vms/plexee inherited from rpool/DATA/fusion rpool/DATA/fusion/store/vms/plexee sharenfs off default rpool/DATA/fusion/store/vms/plexee checksum on default rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee atime off inherited from rpool rpool/DATA/fusion/store/vms/plexee devices off inherited from rpool rpool/DATA/fusion/store/vms/plexee exec on default rpool/DATA/fusion/store/vms/plexee setuidon default rpool/DATA/fusion/store/vms/plexee readonly off default rpool/DATA/fusion/store/vms/plexee zoned off default rpool/DATA/fusion/store/vms/plexee snapdir hidden default rpool/DATA/fusion/store/vms/plexee aclinheritrestricted default rpool/DATA/fusion/store/vms/plexee canmount on default rpool/DATA/fusion/store/vms/plexee xattr on default rpool/DATA/fusion/store/vms/plexee copies1 default rpool/DATA/fusion/store/vms/plexee version 5 - rpool/DATA/fusion/store/vms/plexee utf8only off - rpool/DATA/fusion/store/vms/plexee normalization none - rpool/DATA/fusion/store/vms/plexee casesensitivity sensitive - rpool/DATA/fusion/store/vms/plexee vscan off default rpool/DATA/fusion/store/vms/plexee nbmandoff default rpool/DATA/fusion/store/vms/plexee sharesmb off default rpool/DATA/fusion/store/vms/plexee refquota none default rpool/DATA/fusion/store/vms/plexee refreservationnone default rpool/DATA/fusion/
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
kaihengfeng, I tested with linux-image- unsigned-4.15.0-21-generic_4.15.0-21.22~lp1768292_amd64.deb and was unable to duplicate the 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_atta
[Kernel-packages] [Bug 1766308] Re: inexplicably large file reported by zfs filesystem
1. Yes, compression is on for the parent and inherited. The ratio only shows 1.37x, which seems rather low if a 12T file was all zeros except for >10G? root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee | grep comp rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee refcompressratio 1.37x 2. root@fusion:~# du -h /data/store/vms/plexee/plexee-root 5.6G/data/store/vms/plexee/plexee-root This is what I would expect the VM to be using based on how the file was provisioned and its internal disk state. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem Status in zfs-linux package in Ubuntu: Triaged Bug description: I have a zfs filesystem containing a single qemu kvm disk image. The vm has been working normally. The image file is only allocated 10G, however today I became aware that the file, when examined from the ZFS host (hypervisor) is reporting an inexplicable, massive file size of around 12T. 12T is larger than the pool itself. Snapshots or other filesystem features should not be involved. I'm suspicious that the file(system?) has been corrupted. root@fusion:~# ls -l /data/store/vms/plexee/ total 6164615 -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root ^^ !! root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root image: /data/store/vms/plexee//plexee-root file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 5.9G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee NAME USED AVAIL REFER MOUNTPOINT rpool/DATA/fusion/store/vms/plexee 5.88G 484G 5.88G /data/store/vms/plexee root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee NAMEPROPERTY VALUE SOURCE rpool/DATA/fusion/store/vms/plexee type filesystem - rpool/DATA/fusion/store/vms/plexee creation Mon Mar 26 9:50 2018 - rpool/DATA/fusion/store/vms/plexee used 5.88G - rpool/DATA/fusion/store/vms/plexee available 484G - rpool/DATA/fusion/store/vms/plexee referenced5.88G - rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee mounted yes - rpool/DATA/fusion/store/vms/plexee quota none default rpool/DATA/fusion/store/vms/plexee reservation none default rpool/DATA/fusion/store/vms/plexee recordsize128K default rpool/DATA/fusion/store/vms/plexee mountpoint /data/store/vms/plexee inherited from rpool/DATA/fusion rpool/DATA/fusion/store/vms/plexee sharenfs off default rpool/DATA/fusion/store/vms/plexee checksum on default rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee atime off inherited from rpool rpool/DATA/fusion/store/vms/plexee devices off inherited from rpool rpool/DATA/fusion/store/vms/plexee exec on default rpool/DATA/fusion/store/vms/plexee setuidon default rpool/DATA/fusion/store/vms/plexee readonly off default rpool/DATA/fusion/store/vms/plexee zoned off default rpool/DATA/fusion/store/vms/plexee snapdir hidden default rpool/DATA/fusion/store/vms/plexee aclinheritrestricted default rpool/DATA/fusion/store/vms/plexee canmount on default rpool/DATA/fusion/store/vms/plexee xattr on default rpool/DATA/fusion/store/vms/plexee copies1 default rpool/DATA/fusion/store/vms/plexee version 5 - rpool/DATA/fusion/store/vms/plexee utf8only off - rpool/DATA/fusion/store/vms/plexee normalization none - rpool/DATA/fusion/store/vms/plexee casesen
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 @Daniel I see #1748450 is marked as fix released now, but I still see this behavior (including Xwayland core dumps in my home) with latest bionic packages. Should I open a new bug or unduplicate this one? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Re: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
I can reinstall problematic packages to re-test but need specific instructions how to do is successfully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: Confirmed Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768670] Re: hns3 driver updates
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768670 Title: hns3 driver updates Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The hns3 driver is still under active development upstream, with a number of bug fixes and features that are not yet available in Ubuntu. [Test Case] Smoke testing on a HiSilicon D06 board. [Regression Risk] The code changes here are restricted to the hns3 driver. hns3 drive the NICs in the Hi1620 SoC, which itself is still pre-release. Regressions would therefore be restricted to users doing early evaluation or enablement with the D06 board, upon which these changes were directly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768670] [NEW] hns3 driver updates
Public bug reported: [Impact] The hns3 driver is still under active development upstream, with a number of bug fixes and features that are not yet available in Ubuntu. [Test Case] Smoke testing on a HiSilicon D06 board. [Regression Risk] The code changes here are restricted to the hns3 driver. hns3 drive the NICs in the Hi1620 SoC, which itself is still pre-release. Regressions would therefore be restricted to users doing early evaluation or enablement with the D06 board, upon which these changes were directly tested. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) 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/1768670 Title: hns3 driver updates Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The hns3 driver is still under active development upstream, with a number of bug fixes and features that are not yet available in Ubuntu. [Test Case] Smoke testing on a HiSilicon D06 board. [Regression Risk] The code changes here are restricted to the hns3 driver. hns3 drive the NICs in the Hi1620 SoC, which itself is still pre-release. Regressions would therefore be restricted to users doing early evaluation or enablement with the D06 board, upon which these changes were directly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768663] Re: Fix initialization failure detection in SDEI for device-tree based systems
** Description changed: [Impact] A crash may occur on Device-tree based systems w/ SDEI support, because of an ignored initialization failure. [Test Case] No known test case. [Regression Risk] - I'm unaware of any such system in the field - most SDEI-based systems will likely be ACPI based. + The code is limited to ARM systems, and the fix is obviously correct (IMO). I'm unaware of any such system in the field - most SDEI-based systems will likely be ACPI based. ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768663 Title: Fix initialization failure detection in SDEI for device-tree based systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] A crash may occur on Device-tree based systems w/ SDEI support, because of an ignored initialization failure. [Test Case] No known test case. [Regression Risk] The code is limited to ARM systems, and the fix is obviously correct (IMO). I'm unaware of any such system in the field - most SDEI-based systems will likely be ACPI based. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Re: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: Confirmed Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768663] [NEW] Fix initialization failure detection in SDEI for device-tree based systems
Public bug reported: [Impact] A crash may occur on Device-tree based systems w/ SDEI support, because of an ignored initialization failure. [Test Case] No known test case. [Regression Risk] The code is limited to ARM systems, and the fix is obviously correct (IMO). I'm unaware of any such system in the field - most SDEI-based systems will likely be ACPI based. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) 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/1768663 Title: Fix initialization failure detection in SDEI for device-tree based systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] A crash may occur on Device-tree based systems w/ SDEI support, because of an ignored initialization failure. [Test Case] No known test case. [Regression Risk] The code is limited to ARM systems, and the fix is obviously correct (IMO). I'm unaware of any such system in the field - most SDEI-based systems will likely be ACPI based. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768660] [NEW] r8169 wired link down after suspend
Public bug reported: Everytime i suspend my laptop and back it ON, my ethernet connection shows Cable Unplugged, and r8169 link down. I can mannualy turn it on with sudo rmmod r8169 and then sudo modprobe r8169 but i have to do it everytime i suspend my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed May 2 22:56:49 2018 InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1768660 Title: r8169 wired link down after suspend Status in linux-signed package in Ubuntu: New Bug description: Everytime i suspend my laptop and back it ON, my ethernet connection shows Cable Unplugged, and r8169 link down. I can mannualy turn it on with sudo rmmod r8169 and then sudo modprobe r8169 but i have to do it everytime i suspend my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed May 2 22:56:49 2018 InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
--- Comment From kla...@br.ibm.com 2018-05-02 16:32 EDT--- I think next steps here are: 1) apply all the known firmware workarounds (GH 1158) 2) Bring up system with Doug's recommendations for log verbosity (comment 211 and 215). Also capture the console output to a separate file if possible. 3) re-start the test using this same kernel, but with no stress on the host: proceed to restart the 3 guests with stress, and have a 4th guest migrating between boslcp3 and 4. --- Comment From dougm...@us.ibm.com 2018-05-02 16:36 EDT--- (In reply to comment #218) > I think next steps here are: > > 1) apply all the known firmware workarounds (GH 1158) > 2) Bring up system with Doug's recommendations for log verbosity (comment > 211 and 215). Also capture the console output to a separate file if possible. > 3) re-start the test using this same kernel, but with no stress on the host: > proceed to restart the 3 guests with stress, and have a 4th guest migrating > between boslcp3 and 4. Klaus, let's hold off on making more changes right now. I'd like to let things run as-is a little longer. ** Tags removed: bugnameltc-166588 kernel-key severity-critical triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab
[Kernel-packages] [Bug 1768630] Re: arm64 SDEI support needs trampoline code for KPTI
** Description changed: [Impact] In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). [Test Case] I haven't yet found a way to inject/simulate an SDEI, so I can only regression test by boot testing. [Regression Risk] - The code is restricted to arm64, and should only run on systems that support SDEI. + The code is restricted to arm64, and should only run on systems that support SDEI. I'm unaware of any production firmware that expose the SDEI ACPI table, which means this code isn't actively used yet anyway. ** Description changed: [Impact] - In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). + In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). This may lead to a crash. [Test Case] I haven't yet found a way to inject/simulate an SDEI, so I can only regression test by boot testing. [Regression Risk] The code is restricted to arm64, and should only run on systems that support SDEI. I'm unaware of any production firmware that expose the SDEI ACPI table, which means this code isn't actively used yet anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768630 Title: arm64 SDEI support needs trampoline code for KPTI Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). This may lead to a crash. [Test Case] I haven't yet found a way to inject/simulate an SDEI, so I can only regression test by boot testing. [Regression Risk] The code is restricted to arm64, and should only run on systems that support SDEI. I'm unaware of any production firmware that expose the SDEI ACPI table, which means this code isn't actively used yet anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1768647 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: chaotic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: Incomplete Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
Same problem with another machine (completely different hardware) after upgrading to Kubuntu 18.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/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Re: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
** Attachment added: "working correctly with 4.15.0-20-generic but displays kubuntu instead of ubuntu" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+attachment/5132453/+files/ubuntu-luks.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: New Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Re: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
All graphic fanciness should be removed by default by the way, it's only there to cause problems. https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1768651 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: New Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] [NEW] linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
Public bug reported: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text-only mode and then can enter the password perfectly. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kubuntu-luks-not-working.jpg" https://bugs.launchpad.net/bugs/1768647/+attachment/5132440/+files/kubuntu-luks-not-working.jpg ** Summary changed: - linux 4.15.0-20-generic messes up plymouth and no prompt for cryptfs + linux 4.15.0-20-generic messes up plymouth and no prompt for luks cryptfs ** Summary changed: - linux 4.15.0-20-generic messes up plymouth and no prompt for luks cryptfs + linux 4.15.0-20-generic messes up plymouth and no textbox prompt for luks cryptfs ** Summary changed: - linux 4.15.0-20-generic messes up plymouth and no textbox prompt for luks cryptfs + linux 4.15.0-20-generic messes up plymouth and no prompt for luks password -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: New Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks
ad #3: earlier today, I have tested the kernel 4.15.0-21 under lubuntu-16.04, taken from ppa:canonical-kernel-team/ppa. So far, 3 consecutive boots without problems. I will report back after I have de - installed this kernel again, and have replaced it by what I find in xenial-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767133 Title: linux-image-4.15.0-20-generic install after upgrade from xenial breaks Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Some upgrades from xenial to bionic break. [Test Case] Change sources.list from xenial to bionic, then apt install linux-image-4.15.0-20-generic. [Regression Potential] The kernel may be uninstallable if there is no linux-base with the appropriate version in the archive. When installing the linux-image-4.15.0-20-generic kernel from bionic on xenial breaks because of the unversioned Depends on linux-base. /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.15.0-20-generic (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-image-4.15.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) If the trigger is called, when some meta packages are installed, it won't happen. If all packages are upgraded, it's possible linux-base is going to be upgraded first, so the problem won't happen either. So, not all upgrades will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://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 1761751] Re: Black screen on 18.04 + AMD RX460
I booted the 4.17rc1 kernel. In order to see output I connected an old TV to the DVI output, and that output was successfully detected (through an DVI-HDMI adapter, if that matters). The output of /sys/class/drm/card0-HDMI-A-1 in this case: dpms: Off enabled: disabled modes: (empty) status: disconnected I then tried switching which monitor was connected to which port. Interestingly, in this case both the Dell U2415 and the old TV could show output successfully. // David On 2018-05-02 19:50, Harry Wentland wrote: > Thanks, mind posting the same for the non-working kernel? I'm curious if the > problem is > 1) we don't detect the display > 2) we don't enable the display > 3) we enable the display but wrong > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758545] Re: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer
I would like to say, that I also have this problem. But i don't run Ubuntu. I have the exact same hardware, but I have updated the BIOS to the newer version provided by Lenovo. I run kernel 4.17-rc3. I also believe it is connected to the Wifi card/driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758545 Title: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer Status in linux package in Ubuntu: Incomplete Bug description: My dmesg gets completely spammed with the following messages appearing over and over again, and this keep increasing the size of log file. I can use pci=noaer parameter to suppress these annoying messages, but not sure what this parameter do, will it make my pc lost some function.Is this a bug? below is part of the dmesg infomation -- [ 397.076509] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 397.076517] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 397.076522] pcieport :00:01.1:[20] Unsupported Request(First) [ 397.076526] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 397.081907] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 397.081914] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 397.081918] pcieport :00:01.1:[20] Unsupported Request(First) [ 397.081923] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.983368] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.983376] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.983381] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.983385] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.984773] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.984779] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.984783] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.984788] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.994170] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.994176] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.994180] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.994185] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 399.333957] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 399.333964] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 399.333968] pcieport :00:01.1:[20] Unsupported Request(First) [ 399.333973] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 399.339347] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 399.339353] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 399.339358] pcieport :00:01.1:[20] Unsupported Request(First) [ 399.339362] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ven1747 F pulseaudio /dev/snd/controlC0: ven1747 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 23:24:16 2018 InstallationDate: Installed on 2018-03-07 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) MachineType: LENOVO 81BR ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2017 dmi.bios.vendo
[Kernel-packages] [Bug 1768630] [NEW] arm64 SDEI support needs trampoline code for KPTI
Public bug reported: [Impact] In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). [Test Case] I haven't yet found a way to inject/simulate an SDEI, so I can only regression test by boot testing. [Regression Risk] The code is restricted to arm64, and should only run on systems that support SDEI. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768630 Title: arm64 SDEI support needs trampoline code for KPTI Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] In bug 1756096, we backported SDEI (Software Delegated Exception Interface) support for arm64. However, this backport missed 2 changes that make the SDEI entry point a trampoline which make sure the kernel is mapped before processing. (The kernel may not be mapped if KPTI is enabled and the exception comes in while e.g. executing in usermode). [Test Case] I haven't yet found a way to inject/simulate an SDEI, so I can only regression test by boot testing. [Regression Risk] The code is restricted to arm64, and should only run on systems that support SDEI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-02 14:39 EDT--- The SAN incident in the previous dmesg log shows only a single port (WWPN) glitching. The logs from panics showed two ports glitching at the same time. Also, this incident did not show the port logging back in for about 8 minutes, whereas the panics showed immediate/concurrent login. So, I'm not certain if we've proven the fix yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c038
[Kernel-packages] [Bug 1762844] dmesg log thus far, for May 1 run.
--- Comment (attachment only) From dougm...@us.ibm.com 2018-05-02 14:28 EDT--- ** Attachment added: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/bugs/1762844/+attachment/5132350/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build
--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 EDT--- Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build (in this case, a patched skiroot's kernel -- zImage.epapr), per Dwip's request. Hopefully this might help others in the future. (In reply to comment #203) > The skiroot kernel build is available at: > > http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage. > epapr_4.15.14-openpower1.bz166588c132 ** Attachment added: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/bugs/1762844/+attachment/5132349/+files/file_166588.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a
[Kernel-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
I was able to successfully test this with proposed enabled. Started with 16.04 kernel 4.4 - to 16.04 HWE Kernel - via do-release-upgrade to 18.04. For details see also attached cmd log. Changed tags accordingly. ** Attachment added: "cmd-log.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1766727/+attachment/5132348/+files/cmd-log.txt ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic 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/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Committed Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
I built a Bionic test kernel with commits 36148c2bbfbe and c9f1f58dc2eb. Commit 3a9b76fd0db9 is not needed in Bionic, since it is 3.15 based. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1670041/bionic Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: Update (2017-05-20): Kalle Valo suggested a hack which increased client -> AP TCP performance - so it does not look like a firmware issue as I thought originally, rather an ath10k driver issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11 https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom) Tested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17 Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ - 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :
[Kernel-packages] [Bug 1762844] boslcp3g4 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 EDT--- ** Attachment added: "boslcp3g4 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132341/+files/boslcp3g4.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] boslcp3g1 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g1 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132339/+files/boslcp3g1.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k
--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 EDT--- ** Attachment added: "qla2xxx version 10.00.00.04-k" https://bugs.launchpad.net/bugs/1762844/+attachment/5132344/+files/qla2xxx-10.00.00.04-k.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_
[Kernel-packages] [Bug 1758545] Re: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer
I would like to say, that I also have this problem. But i don't run Ubuntu. I have the exact same hardware, but I have updated the BIOS to the newer version provided by Lenovo. I run kernel 4.17-rc3. I also believe it is connected to the Wifi card/driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758545 Title: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer Status in linux package in Ubuntu: Incomplete Bug description: My dmesg gets completely spammed with the following messages appearing over and over again, and this keep increasing the size of log file. I can use pci=noaer parameter to suppress these annoying messages, but not sure what this parameter do, will it make my pc lost some function.Is this a bug? below is part of the dmesg infomation -- [ 397.076509] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 397.076517] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 397.076522] pcieport :00:01.1:[20] Unsupported Request(First) [ 397.076526] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 397.081907] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 397.081914] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 397.081918] pcieport :00:01.1:[20] Unsupported Request(First) [ 397.081923] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.983368] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.983376] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.983381] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.983385] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.984773] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.984779] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.984783] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.984788] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 398.994170] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 398.994176] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 398.994180] pcieport :00:01.1:[20] Unsupported Request(First) [ 398.994185] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 399.333957] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 399.333964] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 399.333968] pcieport :00:01.1:[20] Unsupported Request(First) [ 399.333973] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 [ 399.339347] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0009(Requester ID) [ 399.339353] pcieport :00:01.1: device [1022:15d3] error status/mask=0010/0440 [ 399.339358] pcieport :00:01.1:[20] Unsupported Request(First) [ 399.339362] pcieport :00:01.1: TLP Header: 3400 01001f10 8c548c54 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ven1747 F pulseaudio /dev/snd/controlC0: ven1747 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 23:24:16 2018 InstallationDate: Installed on 2018-03-07 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) MachineType: LENOVO 81BR ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2017 dmi.bios.vendo
[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build
--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 EDT--- Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build (in this case, a patched skiroot's kernel -- zImage.epapr), per Dwip's request. Hopefully this might help others in the future. (In reply to comment #203) > The skiroot kernel build is available at: > > http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage. > epapr_4.15.14-openpower1.bz166588c132 ** Attachment added: "op-buid instructions for patched skiroot build" https://bugs.launchpad.net/bugs/1762844/+attachment/5132345/+files/file_166588.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a
[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 EDT--- Attached boslcp3 host console logs for step (5) ** Attachment added: "boslcp3_host reboots multiple times" https://bugs.launchpad.net/bugs/1762844/+attachment/5132343/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c
[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
== SRU Justification ==
The following commit introduced a regression identified in bug 1734327:
ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of
the remaining blobs")
The regression causes a kernel panic to occur after multiple TCP connection
creations/closures to the localhost. The bug was found using STAF RPC calls,
but is easily reproducible with SSH.
A revert of commit ac8f82a0b6d9 is needed to resolve this bug. However,
commit 4ae2508f0bed
also needs to be reverted because it depend on commit ac8f82a0b6d9.
== Fix ==
Revert 4ae2508f0bed ("UBUNTU: SAUCE: LSM stacking: add stacking support to
apparmor network hooks")
Revert ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure
management of the remaining blobs")
== Test Case ==
A test kernel was built with these two commits reverted and tested by the
original bug reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
Summary:
Kernel panic occurs after multiple TCP connection creations/closures to the
localhost.
The bug was found using STAF RPC calls, but is easily reproducible with SSH.
The bug doesn't appear on an identical virtual machine booting from the disk.
The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
The bug is reproducible using an older 4.13.0-16-generic kernel
Reproducible on multiple hardware types.
Unable to create a kernel memory dump due to makedumpfile errors.
apport-bug save attached.
NFSRoot boot options:
vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw
Software:
OS: Ubuntu 17.10
Kernel: 4.13.0-17-generic x86_64
Reproduction steps:
1. Boot a system from a nfsroot
2. Configure password-less localhost ssh access
3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
4. Wait for system to crash
Trace:
4,1151,52372730,-;general protection fault: [#1] SMP
4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops
ahci ptp drm libahci pps_core wmi
4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted
4.13.0-17-generic #20-Ubuntu
4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0
12/17/2015
4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
4,1159,52373521,-;RAX: RBX: 241c89490001 RCX:
0004
4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI:
62fac000
4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09:
943bb839
4,1162,52373656,-;R10: 00904c789100 R11: R12:
9d09267ef000
4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15:
9d09267ef000
4,1164,52373746,-;FS: 7f3a53313700() GS:9d092ecc()
knlGS:
4,1165,52373797,-;CS: 0010 DS: ES: CR0: 80050033
4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4:
003406e0
4,1167,52373878,-;DR0: DR1: DR2:
4,1168,52373923,-;DR3: DR6: fffe0ff0 DR7:
0400
4,1169,52373968,-;Call Trace:
4,1170,52373987,-;
4,1171,52374009,-; security_sk_free+0x3e/0x50
4,1172,52374042,-; __sk_destruct+0x108/0x190
4,1173,52374070,-; sk_destruct+0x20/0x30
4,1174,52374095,-; __sk_free+0x82/0xa0
4,1175,52374120,-; sk_free+0
[Kernel-packages] [Bug 1762844] dmesg log thus far, for May 1 run.
--- Comment (attachment only) From dougm...@us.ibm.com 2018-05-02 14:28 EDT--- ** Attachment added: "dmesg log thus far, for May 1 run." https://bugs.launchpad.net/bugs/1762844/+attachment/5132346/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt
--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 EDT--- Attached consolel logs for step(3) & step(4) ** Attachment added: "boslcp3 crashed_used X from xmon prompt" https://bugs.launchpad.net/bugs/1762844/+attachment/5132342/+files/boslcp3_usedX_xmonprompt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/
[Kernel-packages] [Bug 1762844] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-02 14:27 EDT--- Unfortunately, the current test run was executed without "dmesg -n debug" so the captured console output has no value. I corrected that, and so future console output should have what we need. The good news is that the dmesg buffer had not wrapped yet, so I could still grab all of that. There was only one "SAN instability" incident, about an hour ago, and it did not cause a panic. However, I'm not sure if that is conclusive yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380
[Kernel-packages] [Bug 1762844] boslcp3g3 xml
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 EDT--- ** Attachment added: "boslcp3g3 xml" https://bugs.launchpad.net/bugs/1762844/+attachment/5132340/+files/boslcp3g3.dumpxml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Thanks, mind posting the same for the non-working kernel? I'm curious if the problem is 1) we don't detect the display 2) we don't enable the display 3) we enable the display but wrong -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
4.15.0-20-generic from proposed fixes the issue please push this version forward -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767930] Re: ASUS T300F Touchpad only works sometimes and no pertinent setting under Mouse & Touchpad
Firstly, thank you so much for the reply and I have read several articles for how to do that test the latest kernel thing you have told me since I am really new basically to so many things in this computer world. So, I followed the method from the internet to download 4 files from that mainline kernel page you posted. And run that 'sudo dpkg -i *.deb' command but I got some severe error that it even impacted the system update that a No-Entry-road traffic sign appears next to wifi icon in the top menu bar saying "An error occured... The error message was:'Error: BrokenCount > 0'" Here's what happened when I did what I said above in the terminal: # Start of the output benjamin@benjamin-T300FA:~/Desktop/Kernel-v4.17$ sudo dpkg -i *.deb [sudo] password for benjamin: (Reading database ... 282458 files and directories currently installed.) Preparing to unpack linux-headers-4.17.0-041700rc3_4.17.0-041700rc3.201804300800_all.deb ... Unpacking linux-headers-4.17.0-041700rc3 (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Preparing to unpack linux-headers-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-headers-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Preparing to unpack linux-image-unsigned-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-image-unsigned-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postrm ... removing pending trigger Preparing to unpack linux-modules-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb ... Unpacking linux-modules-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) over (4.17.0-041700rc3.201804300800) ... Setting up linux-headers-4.17.0-041700rc3 (4.17.0-041700rc3.201804300800) ... dpkg: dependency problems prevent configuration of linux-headers-4.17.0-041700rc3-generic: linux-headers-4.17.0-041700rc3-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.17.0-041700rc3-generic (--install): dependency problems - leaving unconfigured Setting up linux-modules-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) ... Setting up linux-image-unsigned-4.17.0-041700rc3-generic (4.17.0-041700rc3.201804300800) ... /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postinst: 50: /var/lib/dpkg/info/linux-image-unsigned-4.17.0-041700rc3-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-unsigned-4.17.0-041700rc3-generic (--install): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-headers-4.17.0-041700rc3-generic linux-image-unsigned-4.17.0-041700rc3-generic # end of the output But thanks to the internet again, I found a way to fix the error happened above by running command "sudo apt-get -f install" Then I later learn that what that "fc" at the end of the kernel code 4.17 means, so I went to download the last final version kernel 4.16.6 to give it a shot. But the result was just as same as above. Here's what happened: # Start of the terminal output benjamin@benjamin-T300FA:~/Desktop/Kernel-v4.16.6$ sudo dpkg -i *.deb [sudo] password for benjamin: Selecting previously unselected package linux-headers-4.16.6-041606. (Reading database ... 271321 files and directories currently installed.) Preparing to unpack linux-headers-4.16.6-041606_4.16.6-041606.201804300418_all.deb ... Unpacking linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-headers-4.16.6-041606-generic. Preparing to unpack linux-headers-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-headers-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-image-unsigned-4.16.6-041606-generic. Preparing to unpack linux-image-unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-image-unsigned-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-modules-4.16.6-041606-generic. Preparing to unpack linux-modules-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Setting up linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... dpkg: dependency problems prevent configuration of linux-headers-4.16.6-041606-generic: linux-headers-4.16.6-041606-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.16.6-041606-generic (--install): dependency problems - leaving unconfigured Setting up linux-modules-4.16.6-041606-generic (4.16
[Kernel-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Committed Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://hel
[Kernel-packages] [Bug 1766629] Re: linux-image packages need to Breaks flash-kernel << 3.90ubuntu2
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766629 Title: linux-image packages need to Breaks flash-kernel << 3.90ubuntu2 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Due to the fact that we are no longer guaranteed to produce an initrd from our postinst, flash-kernel can fail on upgrade when it attempts to operate (incorrectly, because it's not smart) on the wrong kernel, and fails to find the initrd we've not yet made. This is worked around in flash-kernel 3.90ubuntu2, but all linux-image packages need to Breaks on << that version to ensure upgrade ordering. This should only apply to kernels which build on arm64 or armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767133 Title: linux-image-4.15.0-20-generic install after upgrade from xenial breaks Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Some upgrades from xenial to bionic break. [Test Case] Change sources.list from xenial to bionic, then apt install linux-image-4.15.0-20-generic. [Regression Potential] The kernel may be uninstallable if there is no linux-base with the appropriate version in the archive. When installing the linux-image-4.15.0-20-generic kernel from bionic on xenial breaks because of the unversioned Depends on linux-base. /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.15.0-20-generic (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-image-4.15.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) If the trigger is called, when some meta packages are installed, it won't happen. If all packages are upgraded, it's possible linux-base is going to be upgraded first, so the problem won't happen either. So, not all upgrades will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Wednesday, 02. May 2018 17:06 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Wednesday, 02. May 2018 17:06 UTC - kernel-stable-phase:Promoted to proposed + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
ok i will check linux-hwe-edge kernels in xenial-proposed, stay tuned -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768496] Re: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system
Thanks, the test was FAILing on artful/arm64 precisely because it was expecting not to find CONFIG_ARM64_SW_TTBR0_PAN set in the 4.13 kernel config, and it was. I have fixed up the qrt script in https://git.launchpad.net/qa-regression-testing/commit/?id=631ed1d195a7a9499caf3e4b5807ba2e423810e0 . Thanks! ** Changed in: qa-regression-testing Status: New => Fix Released ** 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/1768496 Title: test_260_config_arm_pan from kernel_security_test failed on Artful ARM64 system Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Bug description: It looks like this test should be skipped on Artful (kernel < 4.15) But the result returned FAIL instead. Ensure PAN for arm processors is set ... (skipped: CONFIG_ARM64_SW_TTBR0_PAN added/enabled in 4.15 and newer) FAIL == FAIL: test_260_config_arm_pan (__main__.KernelSecurityTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2370, in test_260_config_arm_pan self.assertEqual(expected, self._test_config(config_name)) AssertionError: False != True Also, this CONFIG is available in 4.13 kernel: $ grep ARM64_SW_TTBR0_PAN /boot/config-4.13.0-39-generic CONFIG_ARM64_SW_TTBR0_PAN=y ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-39-generic 4.13.0-39.44 ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 09:54 seq crw-rw 1 root audio 116, 33 May 2 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 2 10:54:29 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1768496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768545] Re: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel
It looks like the commit needed to fix this is f3aefb6a7066e24bfea7fcf1b07907576de69d63, which is in the bionic's linux kernel 4.15.0-20.21 (as commit 17dd0448ee23bbd898c2a9463eb0d0890b29ca02). The corresponding linux-hwe and linux-hwe-edge kernels are in xenial-proposed, going through the kernel Stable Release Updates process. Confirming that the kernel in proposed indeed fixes the issue would be appreciated. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768545 Title: NFS Kerberos broken hwe-edge 4.15.0.15.40 Kernel Status in linux package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: New Bug description: Hi NFS Kerberos is broken hwe-edge 4.15.0.15.40 Kernel see also https://bugzilla.redhat.com/show_bug.cgi?id=1558977 syslog shows something like RPC: couldn't encode RPC header, exit EIO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
