[Kernel-packages] [Bug 1965302] Re: Text-mode console is unavailable in Jammy
This problem disappeared for me when I upgraded my kernel from 5.15.0-22-generic to 5.15.0-23-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965302 Title: Text-mode console is unavailable in Jammy Status in linux package in Ubuntu: Confirmed Bug description: I recently updated a system from Focal to Jammy pre-release, and I've found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is blank. It still seems to accept keyboard input; I can log in "blind" and enter commands that have effects, but I see nothing on the screen. By "nothing," I mean it's completely blank. I also see no kernel or systemd boot messages when I set verbose boot mode by removing the "quiet splash" options. The UEFI firmware's display continues to work, as does the display of my boot manager (rEFInd). Note that kernel options gathered by "ubuntu-bug linux" included with this bug report may include a "vga" option, but I don't normally boot with it; I was trying various options to try to recover my console, and that was the latest change I tried that had no effect. My normal kernel options are: ro root=/dev/mapper/seeker-u2204 quiet splash The text-mode console worked fine with Focal. I tried booting with the Focal kernel (vmlinuz-5.4.0-104-generic) post-upgrade, but it crashed with a kernel panic, complaining that it couldn't read the root filesystem. The kernel version that's currently installed is 5.15.0-22-generic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rodsmith 1462 F pulseaudio /dev/snd/controlC2: rodsmith 1462 F pulseaudio /dev/snd/controlC0: rodsmith 1462 F pulseaudio /dev/snd/controlC1: rodsmith 1462 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 17 08:48:13 2022 HibernationDevice: RESUME=UUID=bf49b324-f388-409c-a93f-d24901a24b60 InstallationDate: Installed on 2014-06-21 (2825 days ago) InstallationMedia: Mythbuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MSI MS-7793 ProcFB: ProcKernelCmdLine: ro root=/dev/mapper/hostname-u2204 initrd=\initrd.img-5.15.0-22-generic vga RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G43 (MS-7793) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd04/20/2015:br4.6:svnMSI:pnMS-7793:pvr2.0:rvnMSI:rnA88X-G43(MS-7793):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7793 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965302] [NEW] Text-mode console is unavailable in Jammy
Public bug reported: I recently updated a system from Focal to Jammy pre-release, and I've found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is blank. It still seems to accept keyboard input; I can log in "blind" and enter commands that have effects, but I see nothing on the screen. By "nothing," I mean it's completely blank. I also see no kernel or systemd boot messages when I set verbose boot mode by removing the "quiet splash" options. The UEFI firmware's display continues to work, as does the display of my boot manager (rEFInd). Note that kernel options gathered by "ubuntu-bug linux" included with this bug report may include a "vga" option, but I don't normally boot with it; I was trying various options to try to recover my console, and that was the latest change I tried that had no effect. My normal kernel options are: ro root=/dev/mapper/seeker-u2204 quiet splash The text-mode console worked fine with Focal. I tried booting with the Focal kernel (vmlinuz-5.4.0-104-generic) post-upgrade, but it crashed with a kernel panic, complaining that it couldn't read the root filesystem. The kernel version that's currently installed is 5.15.0-22-generic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rodsmith 1462 F pulseaudio /dev/snd/controlC2: rodsmith 1462 F pulseaudio /dev/snd/controlC0: rodsmith 1462 F pulseaudio /dev/snd/controlC1: rodsmith 1462 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 17 08:48:13 2022 HibernationDevice: RESUME=UUID=bf49b324-f388-409c-a93f-d24901a24b60 InstallationDate: Installed on 2014-06-21 (2825 days ago) InstallationMedia: Mythbuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MSI MS-7793 ProcFB: ProcKernelCmdLine: ro root=/dev/mapper/hostname-u2204 initrd=\initrd.img-5.15.0-22-generic vga RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G43 (MS-7793) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd04/20/2015:br4.6:svnMSI:pnMS-7793:pvr2.0:rvnMSI:rnA88X-G43(MS-7793):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7793 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965302 Title: Text-mode console is unavailable in Jammy Status in linux package in Ubuntu: New Bug description: I recently updated a system from Focal to Jammy pre-release, and I've found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is blank. It still seems to accept keyboard input; I can log in "blind" and enter commands that have effects, but I see nothing on the screen. By "nothing," I mean it's completely blank. I also see no kernel or systemd boot messages when I set verbose boot mode by removing the "quiet splash" options. The UEFI firmware's display continues to work, as does the display of my boot manager (rEFInd). Note that kernel options gathered by "ubuntu-bug linux" included with this bug report may include a "vga" option, but I don't normally boot with it; I was trying various options to try to recover my console, and that was the latest change I tried that had no effect. My normal kernel options are: ro root=/dev/mapper/seeker-u2204 quiet splash The text-mode console worked fine with Focal. I tried booting with the Focal kernel (vmlinuz-5.4.0-104-generic) post-upgrade, but it crashed with a kernel panic, complaining that it couldn't read the root filesystem. The kernel version that's currently installed is 5.15.0-22-generic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22
[Kernel-packages] [Bug 1909369] Re: linux-headers-5.10.3-051003-generic is not supported
I can confirm that the PPA described in post #2, above, works on a MacBook Air 6,2. Please get this fixed prior to Hirsute's final release! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1909369 Title: linux-headers-5.10.3-051003-generic is not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: > $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 > $ sudo apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installé : (aucun) Candidat : 6.30.223.271+bdcom-0ubuntu5 Table de version : 6.30.223.271+bdcom-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages Hello, I tried to install a wireless network adapter broadcom BCM4360, i nned to install the package bcmwl-kernel-source but when i try to install it i have the following error : "ERROR (dkms apport): kernel package linux-headers-5.10.3-051003-generic is not supported Error! Bad return status for module build on kernel: 5.10.3-051003-generic (x86_64) " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source (not installed) Uname: Linux 5.10.3-051003-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 21:16:07 2020 InstallationDate: Installed on 2020-01-05 (356 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1909369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916962] [NEW] WiFi stopped working on hirsute with bcmwl
Public bug reported: I own a MacBook Air 6,2 on which I've installed several versions of Ubuntu. I recently updated to the hirsute (21.04) pre-release, but WiFi has stopped working. Some web searching suggested re-installing the bcmwl-kernel-source package, which produced the following output: $ sudo apt-get install --reinstall bcmwl-kernel-source [sudo] password for rodsmith: Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://nessus.rodsbooks.com/ubuntu hirsute/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 1s (1,810 kB/s) (Reading database ... 342396 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.10.0-14-generic Building for architecture x86_64 Building initial module for 5.10.0-14-generic Error! Bad return status for module build on kernel: 5.10.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I'm attaching the /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log file referenced above. Some more information: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu7 Candidate: 6.30.223.271+bdcom-0ubuntu7 Version table: *** 6.30.223.271+bdcom-0ubuntu7 500 500 http://nessus.rodsbooks.com/ubuntu hirsute/restricted amd64 Packages 100 /var/lib/dpkg/status $ lshw -C network WARNING: you should run this program as super-user. *-network UNCLAIMED description: Network controller product: BCM4360 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:03:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: latency=0 resources: memory:b060-b0607fff memory:b040-b05f *-network description: Ethernet interface physical id: 2 bus info: usb@2:1 logical name: enx00051bb07d68 serial: 00:05:1b:b0:7d:68 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.10.0-14-generic duplex=full ip=172.24.125.22 link=yes multicast=yes port=MII speed=1Gbit/s WARNING: output may be incomplete or inaccurate, you should run this program as super-user. (Note that the Ethernet device is a plug-in USB adapter; it's not a stock part of the laptop.) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Attachment added: "make.log file referenced in the package installation failure message." https://bugs.launchpad.net/bugs/1916962/+attachment/5467261/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1916962 Title: WiFi stopped working on hirsute with bcmwl Status in bcmwl package in Ubuntu: New Bug description: I own a MacBook Air 6,2 on which I've installed several versions of Ubuntu. I recently updated to the hirsute (21.04) pre-release, but WiFi has stopped working. Some web searching suggested re-installing the bcmwl-kernel-source package, which produced the following output: $ sudo apt-get install --reinstall bcmwl-kernel-source [sudo] password for rodsmith: Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://nessus.rodsbooks.com/ubuntu hirsute/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 1s (1,810 kB/s) (Reading database ... 342396 files and directories currently installed.) Preparing to
[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
** Changed in: checkbox-support (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox-support package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in checkbox-support source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager
]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
1: POSIX ADVISORY WRITE 4149 00:14:817 0 EOF
2: POSIX ADVISORY WRITE 1701
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server, depending on when the problem occurs) is delivering a video mode that the display device can't handle. (With VGA, the display should deliver its capabilities to the computer via EDID, but this doesn't always work correctly.) Thus, the first question is what that "display device" is. The screen shots look like a remote KVM of some sort. Is that the BMC's built-in screen-sharing tool, a network-accessible KVM hardware device (like a Raritan or Avocent), or something else? If possible, I recommend testing in person with a plain monitor plugged directly into the computer, at least as a diagnostic procedure. If that works, then it's likely that the issue is either a matter of a restrictive set of video modes in the remote-access tool, miscommunication between the remote- access tool and the kernel/Wayland/X, or both. Also, if a physical monitor is plugged into the server while it's being accessed remotely, it's conceivable that the kernel/Wayland/X is taking its cues about video mode from the physical monitor rather than from the remote-access tool, thus creating a mismatch. If the problem is caused by the remote access tool, or by an interaction between that and the kernel/Wayland/X, then updating the remote access tool's firmware may fix the problem. Note that the video mode used can vary depending on the kernel version, X vs. Wayland, EFI vs. BIOS boot mode, and other factors. Such variables likely explain why earlier kernels worked but newer ones don't. As a workaround, it might be possibly to forcibly reconfigure the system to use a video mode that will work with the display device. Unfortunately, there are a lot of different ways to do this, depending on the subsystem involved. For instance: * Kernel parameters can set the kernel's video mode. Unfortunately, there are a lot of possibilities even here, including, but not limited to: * nomodeset * video=vga16fb:off * vga16fb.modeset=0 * video=efifb:width:640,height:480 * Try Googling "kernel video mode setting" or something similar for additional possibilities. * X configuration * If you can get X working, even temporarily, you can use the GUI setup tools to change the resolution. * The xrandr tool can be used to probe and set video options; see https://www.x.org/wiki/Projects/XRandR/ * I've not kept up with text-mode (manual) X configuration, but you may be able to find some documentation on how to get it to change video mode. Start here: https://help.ubuntu.com/community/VideoDriverHowto#Xorg.conf.d * Wayland configuration * I'm even less of an expert on this, so I suggest you try Googling "wayland set resolution" or something similar. Finally, note that Ubuntu server certification doesn't cover display devices, so this is NOT a certification blocker. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
I've tested kernel 4.13.0-38-generic #43-Ubuntu from artful-proposed and
the problem does not occur with that kernel.
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linux kernel due to mainline commit 24247aeeabe
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The following mainline commit introduced a regression in v4.14-rc1:
24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")
This commit made it's way into Artful via Launchpad bug 1591609 as Artful
commit
ac2fc5adab0f4b.
This bug was causing regression tests to hang about one in four
times when running cpu_offlining tests.
This patch to fix this regression was just submitted to mainline, so it is
also
needed in Bionic.
== Fix ==
commit d47924417319e3b6a728c0b690f183e75bc2a702
Author: Thomas Gleixner
Date: Tue Jan 16 19:59:59 2018 +0100
x86/intel_rdt/cqm: Prevent use after free
== Regression Potential ==
Low. This patch fixes a current regression that is a use after free.
### Original Bug Description ###
In doing Ubuntu 17.10 regression testing, we've encountered one computer
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when
running our cpu_offlining test. This test attempts to take all the CPU cores
offline except one, then brings them back online again. This test ran
successfully on boldore with previous releases, but with 17.10, the system
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found
no problems; but when I upgraded the 16.04.3 installation to
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident
this is a problem with the kernel. I'm attaching two files,
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg
-w" in a second SSH login; the files are cut-and-pasted from that.)
I initiated this bug report from an Ubuntu 16.04.3 installation
running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Nov 21 17:36:06 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic
Sorry it's taken me so long to get back to you; the affected system is
my main work computer, so I can't just go rebooting it constantly, and
I've been busy with other things.
In any event, I'm afraid I haven't had much luck with these newer
kernels. The bottom line is that to get the VirtualBox modules
installed, I need the linux-headers-{version}-generic package, and for
these newer kernels, that package depends on libssl1.1 or greater; but
the 16.04 I'm using ships with libssl1.0, and I'm unwilling to upgrade
that package and risk far greater (and worse) problems or a return to
the old "dependency hell" issues of the 1990s.
If I get the chance, I may try installing bionic on a removable drive
and try to reproduce the problem in that way.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
System hang with Virtualbox & kernel 4.13.0-32-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Confirmed
Bug description:
Some (maybe all) kernels in the 4.13.0 series are hanging with
Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a
Virtualbox VM, the VM's window appears, clears to black, and then the
mouse freezes. I do NOT see any BIOS/EFI information or boot loader in
the VM; the hang occurs before those messages appear. (I've tried this
with the VM set for both BIOS and EFI booting with no difference.) The
host computer also stops responding to pings or anything else; the
only solution seems to be to do a cold reset. I've tested this on a
different computer running the same kernel and the latest Ubuntu 18.04
alpha and had no problems there. Here's some data from the affected
computer:
$ lsb_release -rd
Description: Ubuntu 16.04.3 LTS
Release: 16.04
$ cat /proc/version_signature
Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
$ dpkg -s virtualbox | grep Version
Version: 5.0.40-dfsg-0ubuntu1.16.04.2
This problem does NOT occur with earlier kernels, such as those in the 4.4.0
series.
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rodsmith 2661 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2014-05-02 (1382 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro
root=/dev/mapper/hostname-trusty_crypt quiet splash
initrd=\initrd.img-4.13.0-32-generic
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware 1.157.15
Tags: xenial
Uname: Linux 4.13.0-32-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago)
UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare
sbuild sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 12/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02AFZ.015.161206.KS
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP740U5M-X01US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 740U5M
dmi.product.version: P02AFZ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
Every other system I've run through this round has shown the same failure on this test. I suspect it's simply a very high false alarm rate, as Jeff suggests, so I'm closing this out as "invalid." ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Invalid Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
>From Jeff Lane via e-mail: > Hi. I can’t see the details right now because I’m on my phone and away from > my desk. That said, > that check is very basic, it fails on any call traces. > > Stress-ng might trigger some call traces if it triggers the OOM Killer which > is fine, and > should be expected during the memory tests. More troubling would be kernel > panics. > > That check is VERY new and fairly trigger happy. It will definitely need some > refinement. > > Point is, take it with a grain of salt and expect a lot of false positives > from that check > for now. Most of the call traces are indeed on stress-ng, so this may not be a problem at all. It might be best if somebody from the kernel team can check the results just to be sure, though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056227/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056226/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056225/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056223/+files/ProcCpuinfoMinimal.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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056224/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056221/+files/PciMultimedia.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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056218/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056220/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056215/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056222/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056219/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
apport information ** Tags added: apport-collected uec-images ** Description changed: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory + Card0.Amixer.values: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro + ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-116-generic N/A + linux-backports-modules-4.4.0-116-generic N/A + linux-firmware 1.157.16 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images + Uname: Linux 4.4.0-116-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 09/10/2015 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: D53427RKE + dmi.board.vendor: Intel Corporation + dmi.board.version: G87971-403 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056214/+files/AlsaDevices.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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic
[Kernel-packages] [Bug 1749818] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056217/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Card0.Codecs.codec.3.txt
apport information ** Attachment added: "Card0.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056216/+files/Card0.Codecs.codec.3.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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: Incomplete Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-116-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
** Attachment added: "Output of "sudo lspci -vnvn"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+attachment/5056108/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: New Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749818] [NEW] Call Trace messages in syslog with 4.4.0-116 kernel
Public bug reported: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/log/syslog from affected system" https://bugs.launchpad.net/bugs/1749818/+attachment/5056107/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel Status in linux package in Ubuntu: New Bug description: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic
Joseph, I'm having problems doing that because of the VirtualBox kernel modules, which don't want to compile for the 4.16 kernel. Here's what I get why I try to re-install dkms and virtualbox-dkms: $ sudo apt-get install dkms virtualbox-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.13.0-26 linux-headers-4.13.0-26-generic linux-image-4.13.0-26-generic linux-image-extra-4.13.0-26-generic linux-signed-image-4.13.0-26-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: dkms virtualbox-dkms 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. Need to get 690 kB of archives. After this operation, 5,319 kB of additional disk space will be used. Get:1 http://nessus.rodsbooks.com/ubuntu xenial-updates/main amd64 dkms all 2.2.0.3-2ubuntu11.5 [66.3 kB] Get:2 http://nessus.rodsbooks.com/ubuntu xenial-updates/multiverse amd64 virtualbox-dkms all 5.0.40-dfsg-0ubuntu1.16.04.2 [624 kB] Fetched 690 kB in 0s (1,499 kB/s) Selecting previously unselected package dkms. (Reading database ... 550655 files and directories currently installed.) Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.5_all.deb ... Unpacking dkms (2.2.0.3-2ubuntu11.5) ... Selecting previously unselected package virtualbox-dkms. Preparing to unpack .../virtualbox-dkms_5.0.40-dfsg-0ubuntu1.16.04.2_all.deb ... Unpacking virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ... Processing triggers for man-db (2.7.5-1) ... Setting up dkms (2.2.0.3-2ubuntu11.5) ... Setting up virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ... Loading new virtualbox-5.0.40 DKMS files... First Installation: checking all kernels... Building only for 4.16.0-041600rc1-generic Building initial module for 4.16.0-041600rc1-generic ERROR (dkms apport): kernel package linux-headers-4.16.0-041600rc1-generic is not supported Error! Bad return status for module build on kernel: 4.16.0-041600rc1-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information. Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details. invoke-rc.d: initscript virtualbox, action "restart" failed. ● virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-02-13 13:30:45 EST; 3ms ago Docs: man:systemd-sysv-generator(8) Process: 9835 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) Feb 13 13:30:45 louiswu systemd[1]: Starting LSB: VirtualBox Linux kernel m. Feb 13 13:30:45 louiswu virtualbox[9835]: * Loading VirtualBox kernel modul Feb 13 13:30:45 louiswu virtualbox[9835]: * No suitable module for running ...d Feb 13 13:30:45 louiswu virtualbox[9835]:...fail! Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Control process exi...=1 Feb 13 13:30:45 louiswu systemd[1]: Failed to start LSB: VirtualBox Linux k...e. Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Unit entered failed...e. Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Failed with result ...'. Hint: Some lines were ellipsized, use -l to show in full. Is there an updated dkms and/or virtualbox-dkms to go along with the 4.16 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1748901] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053621/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053622/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053623/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053630/+files/RfKill.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic
apport information ** Tags added: apport-collected ** Description changed: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 - This problem does NOT occur with earlier kernels, such as those in the - 4.4.0 series. + This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rodsmith 2661 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-05-02 (1382 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic + ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-32-generic N/A + linux-backports-modules-4.13.0-32-generic N/A + linux-firmware 1.157.15 + Tags: xenial + Uname: Linux 4.13.0-32-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) + UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 12/06/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P02AFZ.015.161206.KS + dmi.board.asset.tag: No Asset Tag + dmi.board.name: NP740U5M-X01US + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 31 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: + dmi.product.family: SAMSUNG ATIV + dmi.product.name: 740U5M + dmi.product.version: P02AFZ + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053617/+files/AlsaInfo.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
[Kernel-packages] [Bug 1748901] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053620/+files/IwConfig.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053618/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053628/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053629/+files/PulseList.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053619/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053624/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053626/+files/ProcEnviron.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053625/+files/ProcCpuinfoMinimal.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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053627/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053631/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1748901/+attachment/5053632/+files/WifiSyslog.txt ** 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/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] [NEW] System hang with Virtualbox & kernel 4.13.0-32-generic
Public bug reported: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1748901/+attachment/5053601/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: New Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels
A further update: This problem does NOT occur under Artful on the Dell PowerEdge T610 with the following kernel: $ uname -a Linux hogplum 4.13.0-30-generic #33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I have not yet tested with Xenial or with other kernel series on the PowerEdge T710. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743799 Title: "fwts uefirtmisc" causes reboot in recent kernels Status in Provider for Plainbox - Checkbox: Invalid Status in linux package in Ubuntu: Triaged Bug description: In doing Meltdown regression testing, we found that one server, lucuma, a Dell PowerEdge T710, would spontaneously reboot when running the miscellanea/fwts_test under Ubuntu 14.04.5 with a 3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from our test list for 16.04, so it was not initially tested under more recent kernels. This server has been out of our testing queue for years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet know if the problem is a regression or if it's existed for a long time. We need to do more testing to better isolate the issue; stay tuned for more information The system's entry on C3 is: https://certification.canonical.com/hardware/200910-4539/ The submission showing the error is: https://certification.canonical.com/hardware/200910-4539/submission/126589/ To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels
This bug also affects hogplum, a Dell PowerEdge T610, running Ubuntu 14.04 with a 3.13.0-140 kernel. Here's the uname data from it: $ uname -a Linux hogplum 3.13.0-140-generic #189-Ubuntu SMP Mon Jan 15 16:06:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Running "sudo fwts uefirtmisc" causes a reboot with "33.3%" shown as the percent complete, just as with the Dell T710. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743799 Title: "fwts uefirtmisc" causes reboot in recent kernels Status in Provider for Plainbox - Checkbox: Invalid Status in linux package in Ubuntu: Triaged Bug description: In doing Meltdown regression testing, we found that one server, lucuma, a Dell PowerEdge T710, would spontaneously reboot when running the miscellanea/fwts_test under Ubuntu 14.04.5 with a 3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from our test list for 16.04, so it was not initially tested under more recent kernels. This server has been out of our testing queue for years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet know if the problem is a regression or if it's existed for a long time. We need to do more testing to better isolate the issue; stay tuned for more information The system's entry on C3 is: https://certification.canonical.com/hardware/200910-4539/ The submission showing the error is: https://certification.canonical.com/hardware/200910-4539/submission/126589/ To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
I ran it half a dozen times with your latest kernel and it seemed fine, aside from the usual "error -19" messages. To be sure it's the right one, here's the kernel version information: ubuntu@oil-boldore:~$ uname -a Linux oil-boldore 4.13.0-25-generic #29~lp1733662PatchInMainline SMP Thu Jan 18 15:58:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel due to mainline commit 24247aeeabe 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: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
That seems to have fixed it! I've run the test script six or seven times on both kernels, with nary a hiccup (aside from the "error -19" messages with the 4.13 kernel). Below is the reported kernel information from both your builds, just to be sure I booted the correct kernels. $ uname -a Linux oil-boldore 4.13.0-25-generic #29~lp1733662PatchFromUpstream SMP Wed Jan 17 20:13:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ uname -a Linux oil-boldore 4.15.0-041500rc8-generic #201801172011 SMP Wed Jan 17 20:13:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel due to mainline commit 24247aeeabe Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: Confirmed Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels
I was unable to reproduce this problem on the Dell T110; however, I did
notice that it failed the test at the point where the T710 rebooted.
("Stress test for UEFI miscellaneous runtime service")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743799
Title:
"fwts uefirtmisc" causes reboot in recent kernels
Status in Provider for Plainbox - Checkbox:
Invalid
Status in linux package in Ubuntu:
Triaged
Bug description:
In doing Meltdown regression testing, we found that one server,
lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
the miscellanea/fwts_test under Ubuntu 14.04.5 with a
3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
our test list for 16.04, so it was not initially tested under more
recent kernels. This server has been out of our testing queue for
years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
know if the problem is a regression or if it's existed for a long
time. We need to do more testing to better isolate the issue; stay
tuned for more information
The system's entry on C3 is:
https://certification.canonical.com/hardware/200910-4539/
The submission showing the error is:
https://certification.canonical.com/hardware/200910-4539/submission/126589/
To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels
I tried running apport-collect, as requested by the Ubuntu Kernel Bot, but it didn't work; it tried to open a (text-based) browser, but that hung on "Opening socket", presumably because the system in question is behind strict firewalls in 1SS. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1743799 Title: "fwts uefirtmisc" causes reboot in recent kernels Status in Provider for Plainbox - Checkbox: Invalid Status in linux package in Ubuntu: Confirmed Bug description: In doing Meltdown regression testing, we found that one server, lucuma, a Dell PowerEdge T710, would spontaneously reboot when running the miscellanea/fwts_test under Ubuntu 14.04.5 with a 3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from our test list for 16.04, so it was not initially tested under more recent kernels. This server has been out of our testing queue for years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet know if the problem is a regression or if it's existed for a long time. We need to do more testing to better isolate the issue; stay tuned for more information The system's entry on C3 is: https://certification.canonical.com/hardware/200910-4539/ The submission showing the error is: https://certification.canonical.com/hardware/200910-4539/submission/126589/ To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743799] Re: miscellanea/fwts_test causes reboot
I've managed to isolate this to the fwts "uefirtmisc" test: $ sudo fwts uefirtmisc Running 1 tests, results appended to results.log Test: UEFI miscellaneous runtime service interface tests. Test for UEFI miscellaneous runtime service interfaces. 1 passed, 5 skipped Timeout, server 10.1.11.176 not responding.e service interfaces. : 33.3% | (That last line is partially overwritten by the SSH termination message.) At 33.3% through that test, the system spontaneously reboots. None of the other fwts tests causes any problem. Oddly, the problem disappeared briefly during my testing. This occurred just after I removed the 4.4.0-109 kernel, and a run of fwts produced a message about it being unable to run some tests because it couldn't parse EFI data, but that a reboot should fix the problem. (Sorry, I didn't save the exact wording of the message.) I suspect this was related to EFI variable storage and garbage collection. When I rebooted, the problem reappeared. Some further notes: * The system is rather old (we got it in 2009). * The system is running the latest firmware, version 6.4.0, released in 2013. * The UEFI version is rather old (2.1.0). * It's booted in UEFI mode (of course). I'm going to try re-creating this problem with a Dell T110 of similar vintage. For the moment, I'll leave lucuma, the system with the problem, in its current Ubuntu 14.04 configuration. I can run further tests as directed. As this looks like a kernel bug, or possibly a bug in fwts, I'll mark this as "invalid" for plainbox-provider-checkbox. ** Changed in: plainbox-provider-checkbox Status: New => Invalid ** Summary changed: - miscellanea/fwts_test causes reboot + "fwts uefirtmisc" causes reboot in recent kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743799 Title: "fwts uefirtmisc" causes reboot in recent kernels Status in Provider for Plainbox - Checkbox: Invalid Status in linux package in Ubuntu: Confirmed Bug description: In doing Meltdown regression testing, we found that one server, lucuma, a Dell PowerEdge T710, would spontaneously reboot when running the miscellanea/fwts_test under Ubuntu 14.04.5 with a 3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from our test list for 16.04, so it was not initially tested under more recent kernels. This server has been out of our testing queue for years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet know if the problem is a regression or if it's existed for a long time. We need to do more testing to better isolate the issue; stay tuned for more information The system's entry on C3 is: https://certification.canonical.com/hardware/200910-4539/ The submission showing the error is: https://certification.canonical.com/hardware/200910-4539/submission/126589/ To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
Joseph, The first run of your latest kernel completed; however, I noticed the following in the dmesg output: [ 426.281083] == [ 426.286615] BUG: KASAN: use-after-free in find_first_bit+0x1f/0x80 [ 426.291841] Read of size 8 at addr 883ff7c1e780 by task cpuhp/31/195 [ 426.302209] CPU: 31 PID: 195 Comm: cpuhp/31 Not tainted 4.13.0-25-generic #29~lp1733662KASANenabled [ 426.302213] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 426.302215] Call Trace: [ 426.302233] dump_stack+0xb8/0x12d [ 426.302241] ? dma_virt_map_sg+0xd3/0xd3 [ 426.302252] ? show_regs_print_info+0x41/0x41 [ 426.302263] print_address_description+0x6f/0x280 [ 426.302269] kasan_report+0x27a/0x370 [ 426.302276] ? find_first_bit+0x1f/0x80 [ 426.302288] __asan_load8+0x54/0x90 [ 426.302295] find_first_bit+0x1f/0x80 [ 426.302306] has_busy_rmid+0x47/0x70 [ 426.302314] intel_rdt_offline_cpu+0x4b4/0x510 [ 426.302321] ? clear_closid_rmid.isra.4+0x70/0x70 [ 426.302333] ? sysfs_remove_group+0x7a/0xc0 [ 426.302339] ? clear_closid_rmid.isra.4+0x70/0x70 [ 426.302351] cpuhp_invoke_callback+0x15f/0x7e0 [ 426.302360] ? cpuhp_kick_ap_work+0x2d0/0x2d0 [ 426.302372] ? __schedule+0x4f1/0xeb0 [ 426.302377] ? cpuhp_kick_ap_work+0x2d0/0x2d0 [ 426.302385] ? firmware_map_remove+0x1b1/0x1b1 [ 426.302395] ? migrate_swap_stop+0x2f0/0x2f0 [ 426.302402] ? firmware_map_remove+0x1b1/0x1b1 [ 426.302407] ? migrate_swap_stop+0x2f0/0x2f0 [ 426.302414] ? schedule+0xd8/0x2a0 [ 426.302421] ? __schedule+0xeb0/0xeb0 [ 426.302427] ? default_wake_function+0x2f/0x40 [ 426.302439] ? __wake_up_common+0xa1/0xc0 [ 426.302446] cpuhp_down_callbacks+0x52/0xa0 [ 426.302453] cpuhp_thread_fun+0x117/0x1a0 [ 426.302459] ? cpu_up+0x20/0x20 [ 426.302468] smpboot_thread_fn+0x20e/0x2f0 [ 426.302474] ? sort_range+0x30/0x30 [ 426.302482] kthread+0x1b7/0x1e0 [ 426.302488] ? sort_range+0x30/0x30 [ 426.302493] ? kthread_create_on_node+0xc0/0xc0 [ 426.302500] ret_from_fork+0x1f/0x30 [ 426.307683] Allocated by task 56: [ 426.312817] save_stack_trace+0x1b/0x20 [ 426.312824] save_stack+0x43/0xd0 [ 426.312829] kasan_kmalloc+0xad/0xe0 [ 426.312834] __kmalloc+0x105/0x230 [ 426.312840] intel_rdt_online_cpu+0x5a8/0x830 [ 426.312846] cpuhp_invoke_callback+0x15f/0x7e0 [ 426.312850] cpuhp_thread_fun+0x8b/0x1a0 [ 426.312856] smpboot_thread_fn+0x20e/0x2f0 [ 426.312861] kthread+0x1b7/0x1e0 [ 426.312866] ret_from_fork+0x1f/0x30 [ 426.317887] Freed by task 195: [ 426.322879] save_stack_trace+0x1b/0x20 [ 426.322887] save_stack+0x43/0xd0 [ 426.322891] kasan_slab_free+0x72/0xc0 [ 426.322896] kfree+0x94/0x1a0 [ 426.322902] intel_rdt_offline_cpu+0x17d/0x510 [ 426.322908] cpuhp_invoke_callback+0x15f/0x7e0 [ 426.322912] cpuhp_down_callbacks+0x52/0xa0 [ 426.322917] cpuhp_thread_fun+0x117/0x1a0 [ 426.322925] smpboot_thread_fn+0x20e/0x2f0 [ 426.322929] kthread+0x1b7/0x1e0 [ 426.322935] ret_from_fork+0x1f/0x30 [ 426.327837] The buggy address belongs to the object at 883ff7c1e780 which belongs to the cache kmalloc-8 of size 8 [ 426.338289] The buggy address is located 0 bytes inside of 8-byte region [883ff7c1e780, 883ff7c1e788) [ 426.348805] The buggy address belongs to the page: [ 426.354223] page:ea00ffdf0780 count:1 mapcount:0 mapping: (null) index:0x0 [ 426.359838] flags: 0x57c100(slab) [ 426.365373] raw: 0057c100 000100aa00aa [ 426.371135] raw: dead0100 dead0200 8817f500fb80 [ 426.377004] page dumped because: kasan: bad access detected [ 426.388626] Memory state around the buggy address: [ 426.394498] 883ff7c1e680: fc fc 00 fc fc fb fc fc 00 fc fc fb fc fc 00 fc [ 426.400634] 883ff7c1e700: fc 00 fc fc fb fc fc 00 fc fc fb fc fc fb fc fc [ 426.406721] >883ff7c1e780: fb fc fc fb fc fc fb fc fc 00 fc fc fb fc fc fb [ 426.412737]^ [ 426.418698] 883ff7c1e800: fc fc fb fc fc fb fc fc fb fc fc fb fc fc fb fc [ 426.424961] 883ff7c1e880: fc 00 fc fc fb fc fc fb fc fc fb fc fc fb fc fc [ 426.431154] == [ 426.437413] Disabling lock debugging due to kernel taint [ 426.472795] IRQ 8: no longer affine to CPU31 [ 426.472806] IRQ 9: no longer affine to CPU31 [ 426.472827] IRQ 40: no longer affine to CPU31 [ 426.473962] smpboot: CPU 31 is now offline I ran it several more times without any obvious errors; however, I might have missed something. (The dmesg output is quite verbose and scrolls by quickly!) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel due to
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Yes, it still exists. To confirm the kernel version: $ uname -a Linux oil-boldore 4.15.0-041500rc7-generic #201801072330 SMP Sun Jan 7 23:31:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux The system hung bringing CPU 11 back online, with the following dmesg output: [ 101.179624] smpboot: Booting Node 1 Processor 11 APIC 0x16 [ 101.727507] general protection fault: [#1] SMP PTI [ 101.727812] Modules linked in: nls_iso8859_1 intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds irqbypass ipmi_ssif intel_cstate intel_rapl_perf ipmi_si acpi_power_meter mei_me shpchp ipmi_devintf ipmi_msghandler mei lpc_ich mac_hid acpi_pad ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul mgag200 crc32_pclmul ttm ghash_clmulni_intel pcbc usbhid ses igb drm_kms_helper enclosure dca syscopyarea sysfillrect aesni_intel scsi_transport_sas hid fnic aes_x86_64 sysimgblt ptp crypto_simd libfcoe fb_sys_fops glue_helper ahci pps_core mxm_wmi [ 101.730450] cryptd libfc libahci i2c_algo_bit drm scsi_transport_fc enic megaraid_sas wmi [ 101.730883] CPU: 6 PID: 3205 Comm: python3 Not tainted 4.15.0-041500rc7-generic #201801072330 [ 101.731319] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 101.731773] RIP: 0010:__kmalloc_node+0x16a/0x2c0 [ 101.732224] RSP: 0018:a7d0cf86bbe0 EFLAGS: 00010206 [ 101.732682] RAX: RBX: 3b37355eb8b32f18 RCX: 0349 [ 101.733146] RDX: 0348 RSI: RDI: 00027040 [ 101.733609] RBP: a7d0cf86bc20 R08: 94818ede9cdc R09: 9461bf807c00 [ 101.734075] R10: aaa16cc0 R11: c4c8a1df366db3c4 R12: 014080c0 [ 101.734547] R13: 0008 R14: 94818ede9cdc R15: 9461bf807c00 [ 101.735023] FS: 7f8b0a2c2700() GS:9461bfd8() knlGS: [ 101.735510] CS: 0010 DS: ES: CR0: 80050033 [ 101.735997] CR2: 56075d0c11a8 CR3: 001fe0b32003 CR4: 001606e0 [ 101.736491] Call Trace: [ 101.736988] ? alloc_cpumask_var_node+0x1f/0x30 [ 101.737488] ? on_each_cpu_cond+0x140/0x140 [ 101.737986] alloc_cpumask_var_node+0x1f/0x30 [ 101.738489] zalloc_cpumask_var_node+0xf/0x20 [ 101.738988] smpcfd_prepare_cpu+0x46/0xc0 [ 101.739493] cpuhp_invoke_callback+0x9b/0x550 [ 101.740012] ? init_idle+0x179/0x190 [ 101.740515] _cpu_up+0xb1/0x180 [ 101.741017] do_cpu_up+0x8b/0xb0 [ 101.741515] cpu_up+0x13/0x20 [ 101.742012] cpu_subsys_online+0x3d/0x90 [ 101.742510] device_online+0x4a/0x90 [ 101.743010] online_store+0x89/0xa0 [ 101.743506] dev_attr_store+0x18/0x30 [ 101.744003] sysfs_kf_write+0x37/0x40 [ 101.744501] kernfs_fop_write+0x11c/0x1a0 [ 101.744998] __vfs_write+0x37/0x170 [ 101.745494] ? common_file_perm+0x50/0x140 [ 101.745994] ? apparmor_file_permission+0x1a/0x20 [ 101.746495] ? security_file_permission+0x3b/0xc0 [ 101.746993] ? _cond_resched+0x19/0x40 [ 101.747490] vfs_write+0xb1/0x1a0 [ 101.747988] SyS_write+0x55/0xc0 [ 101.748481] entry_SYSCALL_64_fastpath+0x1e/0x81 [ 101.748977] RIP: 0033:0x7f8b09ea24a0 [ 101.749474] RSP: 002b:7ffd5e22ba78 EFLAGS: 0246 ORIG_RAX: 0001 [ 101.749996] RAX: ffda RBX: 01671410 RCX: 7f8b09ea24a0 [ 101.750490] RDX: 0002 RSI: 01789410 RDI: 0003 [ 101.750971] RBP: 00a3e020 R08: R09: 0001 [ 101.751436] R10: 0100 R11: 0246 R12: 0003 [ 101.751885] R13: 00501520 R14: 7ffd5e22bee0 R15: 7f8b08dbb240 [ 101.752318] Code: 8b 18 4d 33 9f 40 01 00 00 4c 89 c3 4c 31 db 65 48 0f c7 0f 0f 94 c0 84 c0 0f 84 0e ff ff ff 4d 39 d8 74 14 49 63 47 20 48 01 c3 <48> 33 1b 49 33 9f 40 01 00 00 0f 18 0b 41 f7 c4 00 80 00 00 0f [ 101.753201] RIP: __kmalloc_node+0x16a/0x2c0 RSP: a7d0cf86bbe0 [ 101.753642] ---[ end trace ef4dea51947a8216 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
You're right. (I've got too many kernels installed on that system!) When I tested again, it got through eight runs without problems, beyond the "error -19" message. Here's the uname information, just to be sure: $ uname -a Linux oil-boldore 4.13.0-21-generic #24~lp1733662Revert SMP Mon Jan 8 15:35:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
I'm afraid that one fails, too, on the second run when bringing CPU10 back online. Here's the dmesg output: [ 154.987312] smpboot: Booting Node 1 Processor 10 APIC 0x14 [ 154.992953] BUG: unable to handle kernel paging request at 317865646e69 [ 154.993932] IP: __kmalloc_track_caller+0x97/0x1f0 [ 154.994847] PGD 0 [ 154.994848] P4D 0 [ 154.997397] Oops: [#1] SMP [ 154.998250] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ipmi_ssif irqbypass mac_hid ipmi_si shpchp intel_cstate intel_rapl_perf acpi_power_meter ipmi_devintf acpi_pad mei_me lpc_ich ipmi_msghandler mei ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas mgag200 ttm fnic hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper pcbc usbhid syscopyarea igb sysfillrect libfcoe aesni_intel sysimgblt dca fb_sys_fops i2c_algo_bit aes_x86_64 hid crypto_simd glue_helper libfc ptp mxm_wmi ahci drm cryptd [ 155.005714] libahci pps_core scsi_transport_fc enic megaraid_sas wmi [ 155.006913] CPU: 10 PID: 69 Comm: cpuhp/10 Not tainted 4.13.0-13-generic #14~lp1733662Commitac2fc5adab0f4 [ 155.008154] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 155.009427] task: 91c7b8785d00 task.stack: a8760c7e8000 [ 155.010718] RIP: 0010:__kmalloc_track_caller+0x97/0x1f0 [ 155.012014] RSP: :a8760c7ebc48 EFLAGS: 00010206 [ 155.013308] RAX: RBX: RCX: 14b9 [ 155.014618] RDX: 14b8 RSI: RDI: 0001f3e0 [ 155.015946] RBP: a8760c7ebc80 R08: 91c7bf29f3e0 R09: 91a7bf807c00 [ 155.017284] R10: a8760c7ebce0 R11: 0006 R12: 317865646e69 [ 155.018620] R13: 014000c0 R14: 0007 R15: 91a7bf807c00 [ 155.019965] FS: () GS:91c7bf28() knlGS: [ 155.021329] CS: 0010 DS: ES: CR0: 80050033 [ 155.022710] CR2: 317865646e69 CR3: 000ec6c09000 CR4: 001406e0 [ 155.024101] Call Trace: [ 155.025490] ? kvasprintf_const+0x45/0xa0 [ 155.026906] kvasprintf+0x66/0xd0 [ 155.028304] kvasprintf_const+0x45/0xa0 [ 155.029703] kobject_set_name_vargs+0x23/0x90 [ 155.031101] cpu_device_create+0xa4/0x100 [ 155.032485] ? smp_call_function_single+0xb9/0xe0 [ 155.033891] cacheinfo_cpu_online+0x2ac/0x400 [ 155.035295] ? get_cpu_cacheinfo+0x50/0x50 [ 155.036709] cpuhp_invoke_callback+0x84/0x3b0 [ 155.038101] cpuhp_up_callbacks+0x36/0xc0 [ 155.039513] cpuhp_thread_fun+0xd4/0xe0 [ 155.040923] smpboot_thread_fn+0xec/0x160 [ 155.042319] kthread+0x125/0x140 [ 155.043706] ? sort_range+0x30/0x30 [ 155.045107] ? kthread_create_on_node+0x70/0x70 [ 155.046515] ret_from_fork+0x25/0x30 [ 155.047906] Code: 08 65 4c 03 05 ab e5 7d 5b 49 83 78 10 00 4d 8b 20 0f 84 ef 00 00 00 4d 85 e4 0f 84 e6 00 00 00 49 63 41 20 49 8b 39 48 8d 4a 01 <49> 8b 1c 04 4c 89 e0 65 48 0f c7 0f 0f 94 c0 84 c0 74 bb 49 63 [ 155.050922] RIP: __kmalloc_track_caller+0x97/0x1f0 RSP: a8760c7ebc48 [ 155.052426] CR2: 317865646e69 [ 155.053914] ---[ end trace f7bb4aa3c197a453 ]--- To be sure, here's the kernel version information: $ uname -a Linux oil-boldore 4.13.0-13-generic #14~lp1733662Commitac2fc5adab0f4 SMP Fri Jan 5 15:31:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one completed two runs, but on the second run, dmesg included the following message at one point: [ 240.841694] kernel BUG at /home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878! [ 240.842765] invalid opcode: [#1] SMP [ 240.843718] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf ipmi_ssif joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich shpchp acpi_pad mac_hid mei_me mei ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc fnic mgag200 ttm hid_generic drm_kms_helper syscopyarea igb sysfillrect aesni_intel sysimgblt usbhid libfcoe fb_sys_fops aes_x86_64 dca hid crypto_simd i2c_algo_bit mxm_wmi glue_helper ptp cryptd ahci libfc libahci [ 240.851457] drm pps_core megaraid_sas scsi_transport_fc enic wmi [ 240.852693] CPU: 8 PID: 2724 Comm: irqbalance Not tainted 4.13.0-13-generic #14~lp1733662Commitac2fc5adab0f4 [ 240.853965] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 240.855281] task: 9b62a76645c0 task.stack: b973cf6fc000 [ 240.856603] RIP: 0010:kfree+0x11c/0x160 [ 240.857937] RSP: 0018:b973cf6ffa08 EFLAGS: 00010246 [ 240.859280] RAX: f8803cff0020 RBX: 9b62 RCX: [ 240.860632] RDX: RSI: 9b62b0eb5348 RDI: 64dcc000 [ 240.861995] RBP: b973cf6ffa20 R08: 9b62b22f70f0 R09: 000180220021 [ 240.863367] R10: f8803d00 R11: 0001 R12: 9b62b1648780 [ 240.864756] R13: b65dd4e0 R14: 9b62a872f0d8 R15: 9b62a872fac0 [ 240.866145] FS: 7ff8c4d06740() GS:9b62bf20() knlGS: [ 240.867562] CS: 0010 DS: ES: CR0: 80050033 [ 240.868986] CR2: 7fff9ef860f8 CR3: 003fe7876000 CR4: 001406e0 [ 240.870438] Call Trace: [ 240.871882] kfree_const+0x20/0x30 [ 240.873328] kernfs_put+0x71/0x180 [ 240.874778] kernfs_dop_release+0x12/0x20 [ 240.876218] __dentry_kill+0xe5/0x150 [ 240.877644] shrink_dentry_list+0x11f/0x2e0 [ 240.879078] d_invalidate+0x67/0x110 [ 240.880526] lookup_fast+0x2b9/0x310 [ 240.881968] ? dput.part.23+0x2d/0x1e0 [ 240.883393] walk_component+0x49/0x340 [ 240.884811] ? kernfs_iop_permission+0x4f/0x60 [ 240.886253] link_path_walk+0x1bc/0x590 [ 240.887690] ? path_init+0x177/0x2f0 [ 240.889105] path_lookupat+0x56/0x1f0 [ 240.890529] filename_lookup+0xb6/0x190 [ 240.891964] ? sprintf+0x51/0x70 [ 240.893387] ? __check_object_size+0xaf/0x1b0 [ 240.894822] ? strncpy_from_user+0x4d/0x170 [ 240.896240] user_path_at_empty+0x36/0x40 [ 240.897673] ? user_path_at_empty+0x36/0x40 [ 240.899101] vfs_statx+0x76/0xe0 [ 240.900517] SYSC_newstat+0x3d/0x70 [ 240.901934] ? fput+0xe/0x10 [ 240.903365] ? task_work_run+0x7b/0x90 [ 240.904783] ? exit_to_usermode_loop+0x9b/0xd0 [ 240.906181] SyS_newstat+0xe/0x10 [ 240.907559] entry_SYSCALL_64_fastpath+0x1e/0xa9 [ 240.908900] RIP: 0033:0x7ff8c3df6bb5 [ 240.910196] RSP: 002b:7ffe6cf8a928 EFLAGS: 0246 ORIG_RAX: 0004 [ 240.911496] RAX: ffda RBX: 00fe9a40 RCX: 7ff8c3df6bb5 [ 240.912763] RDX: 7ffe6cf8a980 RSI: 7ffe6cf8a980 RDI: 7ffe6cf8c210 [ 240.913985] RBP: R08: R09: 0039 [ 240.915181] R10: R11: 0246 R12: [ 240.916320] R13: 7ffe6cf8b22b R14: 00fe9a40 R15: 00fe92f0 [ 240.917447] Code: 08 49 83 c4 18 48 89 da 4c 89 ee ff d0 49 8b 04 24 48 85 c0 75 e6 e9 0e ff ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 2c [ 240.919769] RIP: kfree+0x11c/0x160 RSP: b973cf6ffa08 [ 240.920909] ---[ end trace 67fe147f4dd931eb ]--- A third run produced a hang when offlining CPU 8, with the following dmesg output: [ 352.776303] EDAC MC1: Giving out device to module sb_edac.c controller Haswell SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT) [ 352.776572] EDAC sbridge: Some needed devices are missing [ 352.801614] EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#1_Ha#0: DEV :ff:12.0 [ 352.825588] EDAC MC: Removed device 1 for sb_edac.c Haswell SrcID#0_Ha#0: DEV :7f:12.0 [ 352.826090] EDAC sbridge: Couldn't find mci handler [ 352.826457] EDAC sbridge: Couldn't find mci handler [ 352.826826] EDAC sbridge: Failed to register device with error -19. [ 353.286163] BUG: unable to handle kernel paging request at 317865646e69 [ 353.286790] IP: __kmalloc_node+0x135/0x2a0 [ 353.287303] PGD 0 [ 353.287304] P4D 0 [
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one completed its first run, but then crashed when bringing CPU 14 back online, with the following dmesg output: [ 163.176945] [ cut here ] [ 163.176949] kernel BUG at /home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878! [ 163.178043] invalid opcode: [#1] SMP [ 163.178995] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate joydev input_leds shpchp ipmi_ssif intel_rapl_perf acpi_power_meter lpc_ich ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid mei_me mei ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas mgag200 ttm drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea pcbc sysfillrect fnic aesni_intel hid_generic sysimgblt igb fb_sys_fops aes_x86_64 dca usbhid crypto_simd i2c_algo_bit glue_helper libfcoe hid ahci ptp libfc mxm_wmi cryptd libahci [ 163.186785] drm pps_core enic scsi_transport_fc megaraid_sas wmi [ 163.188025] CPU: 14 PID: 93 Comm: cpuhp/14 Not tainted 4.13.0-13-generic #14~lp1733662Commite6108d5475696 [ 163.189294] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 163.190606] task: 8dbaf809c5c0 task.stack: ae2acc8a8000 [ 163.191926] RIP: 0010:kfree+0x11c/0x160 [ 163.193255] RSP: :ae2acc8abb80 EFLAGS: 00010246 [ 163.194600] RAX: f9cb3bff0020 RBX: 8dba RCX: ae2acc8abb60 [ 163.195954] RDX: RSI: RDI: 72848000 [ 163.197311] RBP: ae2acc8abb98 R08: ae2acc8abaec R09: 0002 [ 163.198703] R10: f9cb3c00 R11: R12: 8d9aff94beb0 [ 163.200096] R13: a6f2034b R14: 8dbaf27e4318 R15: 8dbaf27e4200 [ 163.201497] FS: () GS:8dbaff38() knlGS: [ 163.202919] CS: 0010 DS: ES: CR0: 80050033 [ 163.204351] CR2: CR3: 00101aa09000 CR4: 001406e0 [ 163.205802] Call Trace: [ 163.207253] acpi_ns_get_node_unlocked+0xac/0xd8 [ 163.208704] ? kernfs_add_one+0xe4/0x130 [ 163.210183] ? down_timeout+0x37/0x60 [ 163.211644] ? acpi_os_wait_semaphore+0x4c/0x70 [ 163.213098] acpi_ns_get_node+0x41/0x58 [ 163.214550] ? acpi_ns_get_node+0x41/0x58 [ 163.216016] acpi_get_handle+0x95/0xbe [ 163.217486] acpi_has_method+0x25/0x40 [ 163.218932] acpi_processor_get_performance_info+0x57/0x580 [ 163.220391] ? wrmsrl_on_cpu+0x57/0x70 [ 163.221870] acpi_processor_register_performance+0x5e/0xd0 [ 163.223354] __intel_pstate_cpu_init.part.16+0xed/0x2e0 [ 163.224835] ? intel_pstate_init_cpu+0xc9/0x2d0 [ 163.226323] intel_pstate_cpu_init+0x24/0x40 [ 163.227819] cpufreq_online+0xd8/0x750 [ 163.229301] ? cpufreq_online+0x750/0x750 [ 163.230781] cpuhp_cpufreq_online+0xe/0x20 [ 163.232262] cpuhp_invoke_callback+0x84/0x3b0 [ 163.233758] cpuhp_up_callbacks+0x36/0xc0 [ 163.235254] cpuhp_thread_fun+0xd4/0xe0 [ 163.236731] smpboot_thread_fn+0xec/0x160 [ 163.238210] kthread+0x125/0x140 [ 163.239693] ? sort_range+0x30/0x30 [ 163.241165] ? kthread_create_on_node+0x70/0x70 [ 163.242629] ret_from_fork+0x25/0x30 [ 163.244061] Code: 08 49 83 c4 18 48 89 da 4c 89 ee ff d0 49 8b 04 24 48 85 c0 75 e6 e9 0e ff ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 2c [ 163.247030] RIP: kfree+0x11c/0x160 RSP: ae2acc8abb80 [ 163.248463] ---[ end trace e22fa4721cb983b5 ]--- [ 168.454846] [ cut here ] [ 168.456219] kernel BUG at /home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878! [ 168.457561] invalid opcode: [#2] SMP [ 168.458849] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate joydev input_leds shpchp ipmi_ssif intel_rapl_perf acpi_power_meter lpc_ich ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid mei_me mei ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas mgag200 ttm drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea pcbc sysfillrect fnic aesni_intel hid_generic sysimgblt igb fb_sys_fops aes_x86_64 dca usbhid crypto_simd i2c_algo_bit glue_helper libfcoe hid ahci ptp libfc mxm_wmi cryptd libahci [ 168.468659] drm pps_core enic scsi_transport_fc megaraid_sas wmi [ 168.470126] CPU: 0 PID: 2683 Comm: irqbalance Tainted: G D 4.13.0-13-generic #14~lp1733662Commite6108d5475696 [ 168.471648]
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Joseph, that one also completed six runs with no problems except the "error -19" messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Thanks, Joseph. My break was good; I hope yours was, too! That latest version you posted completed half a dozen runs of the test script without incident, aside from the "error -19" messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one ran our test script half a dozen times without failure, albeit with the "Error -19" messages in the dmesg output. Note that I'm about to EOD, so I probably won't get to the next one until next year. Have a good holiday, Joseph! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one hung much like the others, with the system responding only to very basic commands (mostly bash internals), although the dmesg output continued further after the kernel bug message. Here's the dmesg output: [ 107.652875] EDAC MC0: Giving out device to module sb_edac.c controller Haswell SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT) [ 107.652995] EDAC MC1: Giving out device to module sb_edac.c controller Haswell SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT) [ 107.653010] EDAC sbridge: Some needed devices are missing [ 107.675559] EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#1_Ha#0: DEV :ff:12.0 [ 107.703606] EDAC MC: Removed device 1 for sb_edac.c Haswell SrcID#0_Ha#0: DEV :7f:12.0 [ 107.703639] EDAC sbridge: Couldn't find mci handler [ 107.704195] EDAC sbridge: Couldn't find mci handler [ 107.704618] EDAC sbridge: Failed to register device with error -19. [ 108.163612] smpboot: Booting Node 1 Processor 8 APIC 0x10 [ 108.189804] intel_rapl: Found RAPL domain package [ 108.189810] intel_rapl: Found RAPL domain dram [ 108.189812] intel_rapl: DRAM domain energy unit 15300pj [ 108.190389] [ cut here ] [ 108.190390] kernel BUG at /home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878! [ 108.191016] invalid opcode: [#1] SMP [ 108.191511] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel kvm input_leds irqbypass joydev mei_me intel_cstate ipmi_si intel_rapl_perf shpchp acpi_power_meter ipmi_devintf ipmi_msghandler mei lpc_ich mac_hid acpi_pad ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas crct10dif_pclmul crc32_pclmul mgag200 ghash_clmulni_intel ttm pcbc fnic hid_generic drm_kms_helper igb syscopyarea aesni_intel usbhid dca sysfillrect i2c_algo_bit sysimgblt aes_x86_64 ptp fb_sys_fops crypto_simd mxm_wmi hid libfcoe glue_helper ahci cryptd libfc drm [ 108.195174] libahci pps_core enic scsi_transport_fc megaraid_sas wmi [ 108.195756] CPU: 8 PID: 302 Comm: kworker/8:3 Not tainted 4.13.0-13-generic #14~lp1733662Commit97327adfdaf5d [ 108.196353] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 108.196971] Workqueue: events cpuset_hotplug_workfn [ 108.197583] task: 8e3432fcae80 task.stack: b5fb4e104000 [ 108.198236] RIP: 0010:kfree+0x11c/0x160 [ 108.198861] RSP: :b5fb4e107cc8 EFLAGS: 00010246 [ 108.199485] RAX: fb0ffeff0020 RBX: 8e34 RCX: 00018020001d [ 108.200121] RDX: RSI: fb0fffd33600 RDI: 720b4000 [ 108.200764] RBP: b5fb4e107ce0 R08: 8e3434cd8c00 R09: 00018020001d [ 108.201405] R10: fb0fff00 R11: R12: 8e343254f058 [ 108.202053] R13: 876ce3d3 R14: 8e34382b6d10 R15: [ 108.202703] FS: () GS:8e343f20() knlGS: [ 108.203367] CS: 0010 DS: ES: CR0: 80050033 [ 108.204031] CR2: CR3: 0026c7609000 CR4: 001406e0 [ 108.204702] Call Trace: [ 108.205377] sd_free_ctl_entry+0x63/0x70 [ 108.206054] sd_free_ctl_entry+0x53/0x70 [ 108.206727] unregister_sched_domain_sysctl+0x36/0x40 [ 108.207396] partition_sched_domains+0x34/0x2f0 [ 108.208070] rebuild_sched_domains_locked+0x5a/0x80 [ 108.208771] rebuild_sched_domains+0x1a/0x30 [ 108.209442] cpuset_hotplug_workfn+0x1b1/0xd30 [ 108.210119] ? mutex_lock+0x12/0x40 [ 108.210790] process_one_work+0x1e7/0x410 [ 108.211470] worker_thread+0x4a/0x410 [ 108.212146] kthread+0x125/0x140 [ 108.212814] ? process_one_work+0x410/0x410 [ 108.213482] ? kthread_create_on_node+0x70/0x70 [ 108.214159] ret_from_fork+0x25/0x30 [ 108.214830] Code: 08 49 83 c4 18 48 89 da 4c 89 ee ff d0 49 8b 04 24 48 85 c0 75 e6 e9 0e ff ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 2c [ 108.216269] RIP: kfree+0x11c/0x160 RSP: b5fb4e107cc8 [ 108.217042] ---[ end trace 8c27258fb7e406c8 ]--- [ 108.225116] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 108.225880] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 108.226442] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 108.227006] EDAC sbridge: Seeking for: PCI ID 8086:2f60 [ 108.227623] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 108.228288] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 108.228809] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 108.229313] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 108.229794] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 108.230253] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 108.230692] EDAC sbridge: Seeking for: PCI ID 8086:2faa [ 108.231110] EDAC sbridge:
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
The build from http://kernel.ubuntu.com/~jsalisbury/lp1733662/ successfully completed about six runs of the test script, albeit with the verbose dmesg output that includes the "EDAC sbridge: Failed to register device with error -19" messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one completed one run of the test OK, but then crashed on the
second one, when bringing CPU 15 back online, with the following dmesg
output:
[ 160.596312] EDAC MC0: Giving out device to module sb_edac.c controller
Haswell SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT)
[ 160.596537] EDAC MC1: Giving out device to module sb_edac.c controller
Haswell SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT)
[ 160.596679] EDAC sbridge: Some needed devices are missing
[ 160.627089] EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#1_Ha#0:
DEV :ff:12.0
[ 160.651100] EDAC MC: Removed device 1 for sb_edac.c Haswell SrcID#0_Ha#0:
DEV :7f:12.0
[ 160.651271] EDAC sbridge: Couldn't find mci handler
[ 160.651422] EDAC sbridge: Couldn't find mci handler
[ 160.651572] EDAC sbridge: Failed to register device with error -19.
[ 161.099074] BUG: unable to handle kernel paging request at 000180040100
[ 161.099512] IP: __kmalloc_node+0x135/0x2a0
[ 161.099704] PGD 1ff1f01067
[ 161.099705] P4D 1ff1f01067
[ 161.099871] PUD 0
[ 161.100373] Oops: [#2] SMP
[ 161.100548] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal
intel_powerclamp coretemp intel_cstate kvm_intel kvm irqbypass intel_rapl_perf
joydev input_leds ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler mei_me mei
shpchp lpc_ich acpi_pad mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure
scsi_transport_sas fnic crct10dif_pclmul crc32_pclmul mgag200
ghash_clmulni_intel ttm pcbc igb hid_generic drm_kms_helper aesni_intel dca
syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt usbhid libfcoe
crypto_simd fb_sys_fops ahci ptp glue_helper hid mxm_wmi libfc cryptd libahci
[ 161.102507] pps_core drm enic scsi_transport_fc megaraid_sas wmi
[ 161.102856] CPU: 2 PID: 3686 Comm: python3 Tainted: G D
4.13.0-13-generic #14~lp1733662Commit8d9d2235a82ea41
[ 161.103230] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L,
BIOS C240M4.2.0.10c.0.032320160820 03/23/2016
[ 161.103624] task: 8f3de5989740 task.stack: a3a7ce288000
[ 161.104024] RIP: 0010:__kmalloc_node+0x135/0x2a0
[ 161.104431] RSP: 0018:a3a7ce28bc30 EFLAGS: 00010246
[ 161.104846] RAX: RBX: RCX: 0f95
[ 161.105274] RDX: 0f94 RSI: RDI: 0001f3e0
[ 161.105705] RBP: a3a7ce28bc70 R08: 8f3dffc9f3e0 R09: 8f3dff807c00
[ 161.106148] R10: bb017760 R11: 8f5df8fa21f2 R12: 014080c0
[ 161.106599] R13: 0008 R14: 000180040100 R15: 8f3dff807c00
[ 161.107057] FS: 7f7849b98700() GS:8f3dffc8()
knlGS:
[ 161.107530] CS: 0010 DS: ES: CR0: 80050033
[ 161.108014] CR2: 000180040100 CR3: 001ff6e6e000 CR4: 001406e0
[ 161.108509] Call Trace:
[ 161.109012] ? alloc_cpumask_var_node+0x1f/0x30
[ 161.109523] ? on_each_cpu_cond+0x160/0x160
[ 161.110036] alloc_cpumask_var_node+0x1f/0x30
[ 161.110558] zalloc_cpumask_var_node+0xf/0x20
[ 161.111084] smpcfd_prepare_cpu+0x64/0xc0
[ 161.111615] cpuhp_invoke_callback+0x84/0x3b0
[ 161.112151] cpuhp_up_callbacks+0x36/0xc0
[ 161.112690] _cpu_up+0x87/0xd0
[ 161.113235] do_cpu_up+0x8b/0xb0
[ 161.113785] cpu_up+0x13/0x20
[ 161.114342] cpu_subsys_online+0x3d/0x90
[ 161.114881] device_online+0x4a/0x90
[ 161.115422] online_store+0x89/0xa0
[ 161.115951] dev_attr_store+0x18/0x30
[ 161.116472] sysfs_kf_write+0x37/0x40
[ 161.116994] kernfs_fop_write+0x11c/0x1a0
[ 161.117510] __vfs_write+0x18/0x40
[ 161.118029] vfs_write+0xb1/0x1a0
[ 161.118544] SyS_write+0x55/0xc0
[ 161.119062] entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 161.119581] RIP: 0033:0x7f78497784a0
[ 161.120081] RSP: 002b:7fff6e69ed48 EFLAGS: 0246 ORIG_RAX:
0001
[ 161.120602] RAX: ffda RBX: 01ea8410 RCX: 7f78497784a0
[ 161.121129] RDX: 0002 RSI: 01fbe400 RDI: 0003
[ 161.121666] RBP: 00a3e020 R08: R09: 0001
[ 161.122202] R10: 0100 R11: 0246 R12: 0003
[ 161.122720] R13: 00501520 R14: 7fff6e69f1b0 R15: 7f7848690240
[ 161.123226] Code: 89 cf 4c 89 4d c0 e8 0b 7f 01 00 49 89 c7 4c 8b 4d c0 4d
85 ff 0f 85 47 ff ff ff 45 31 f6 eb 3c 49 63 47 20 49 8b 3f 48 8d 4a 01 <49> 8b
1c 06 4c 89 f0 65 48 0f c7 0f 0f 94 c0 84 c0 0f 84 20 ff
[ 161.124251] RIP: __kmalloc_node+0x135/0x2a0 RSP: a3a7ce28bc30
[ 161.124738] CR2: 000180040100
[ 161.125220] ---[ end trace 1246d63efc5b2bf0 ]---
Rather than hang, as has happened before, the script crashed ("Killed"
was displayed and I was dropped back to a bash prompt). The system
behaved unreliably and I was
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
OK, I've run tests now. The system did not crash or otherwise misbehave, but the dmesg output was quite verbose, and included "error -19" messages. Here's a sample (apparently for just one CPU core; this sequence was repeated quite a few times): [ 439.341956] smpboot: Booting Node 1 Processor 31 APIC 0x1f [ 439.354783] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 439.354795] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 439.354814] EDAC sbridge: Seeking for: PCI ID 8086:2fa0 [ 439.354836] EDAC sbridge: Seeking for: PCI ID 8086:2f60 [ 439.354849] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 439.354853] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 439.354859] EDAC sbridge: Seeking for: PCI ID 8086:2fa8 [ 439.354866] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 439.354870] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 439.354876] EDAC sbridge: Seeking for: PCI ID 8086:2f71 [ 439.354882] EDAC sbridge: Seeking for: PCI ID 8086:2faa [ 439.354886] EDAC sbridge: Seeking for: PCI ID 8086:2faa [ 439.354892] EDAC sbridge: Seeking for: PCI ID 8086:2faa [ 439.354898] EDAC sbridge: Seeking for: PCI ID 8086:2fab [ 439.354902] EDAC sbridge: Seeking for: PCI ID 8086:2fab [ 439.354909] EDAC sbridge: Seeking for: PCI ID 8086:2fab [ 439.354915] EDAC sbridge: Seeking for: PCI ID 8086:2fac [ 439.354919] EDAC sbridge: Seeking for: PCI ID 8086:2fac [ 439.354925] EDAC sbridge: Seeking for: PCI ID 8086:2fac [ 439.354931] EDAC sbridge: Seeking for: PCI ID 8086:2fad [ 439.354936] EDAC sbridge: Seeking for: PCI ID 8086:2fad [ 439.354942] EDAC sbridge: Seeking for: PCI ID 8086:2fad [ 439.354948] EDAC sbridge: Seeking for: PCI ID 8086:2f68 [ 439.354953] EDAC sbridge: Seeking for: PCI ID 8086:2f68 [ 439.354960] EDAC sbridge: Seeking for: PCI ID 8086:2f68 [ 439.354965] EDAC sbridge: Seeking for: PCI ID 8086:2f79 [ 439.354978] EDAC sbridge: Seeking for: PCI ID 8086:2f6a [ 439.354991] EDAC sbridge: Seeking for: PCI ID 8086:2f6b [ 439.355003] EDAC sbridge: Seeking for: PCI ID 8086:2f6c [ 439.355016] EDAC sbridge: Seeking for: PCI ID 8086:2f6d [ 439.355029] EDAC sbridge: Seeking for: PCI ID 8086:2ffc [ 439.355033] EDAC sbridge: Seeking for: PCI ID 8086:2ffc [ 439.355039] EDAC sbridge: Seeking for: PCI ID 8086:2ffc [ 439.355046] EDAC sbridge: Seeking for: PCI ID 8086:2ffd [ 439.355049] EDAC sbridge: Seeking for: PCI ID 8086:2ffd [ 439.355055] EDAC sbridge: Seeking for: PCI ID 8086:2ffd [ 439.355062] EDAC sbridge: Seeking for: PCI ID 8086:2fbd [ 439.355067] EDAC sbridge: Seeking for: PCI ID 8086:2fbd [ 439.355073] EDAC sbridge: Seeking for: PCI ID 8086:2fbd [ 439.355079] EDAC sbridge: Seeking for: PCI ID 8086:2fbf [ 439.355084] EDAC sbridge: Seeking for: PCI ID 8086:2fbf [ 439.355090] EDAC sbridge: Seeking for: PCI ID 8086:2fbf [ 439.355095] EDAC sbridge: Seeking for: PCI ID 8086:2fb9 [ 439.355101] EDAC sbridge: Seeking for: PCI ID 8086:2fb9 [ 439.355107] EDAC sbridge: Seeking for: PCI ID 8086:2fb9 [ 439.355112] EDAC sbridge: Seeking for: PCI ID 8086:2fbb [ 439.355117] EDAC sbridge: Seeking for: PCI ID 8086:2fbb [ 439.355123] EDAC sbridge: Seeking for: PCI ID 8086:2fbb [ 439.355355] EDAC MC0: Giving out device to module sb_edac.c controller Haswell SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT) [ 439.355601] EDAC MC1: Giving out device to module sb_edac.c controller Haswell SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT) [ 439.355629] EDAC sbridge: Some needed devices are missing [ 439.382001] EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#1_Ha#0: DEV :ff:12.0 [ 439.398059] EDAC MC: Removed device 1 for sb_edac.c Haswell SrcID#0_Ha#0: DEV :7f:12.0 [ 439.398115] EDAC sbridge: Couldn't find mci handler [ 439.399135] EDAC sbridge: Couldn't find mci handler [ 439.399887] EDAC sbridge: Failed to register device with error -19. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
There's nothing at the URL you posted, Joseph. Do I just need to give it more time to build, or is something 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/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
That one failed (the script stopped running after taking CPU 9 offline) with the following dmesg output: [ 119.360953] [ cut here ] [ 119.360955] kernel BUG at /home/jsalisbury/bugs/lp1734327/ac8f82a-revert-test/ubuntu-artful/mm/slub.c:3878! [ 119.361405] invalid opcode: [#1] SMP [ 119.361586] Modules linked in: nls_iso8859_1 kvm_intel kvm irqbypass joydev input_leds ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler acpi_pad ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic pcbc igb usbhid dca aesni_intel hid aes_x86_64 crypto_simd glue_helper ptp cryptd ahci pps_core libahci i2c_algo_bit megaraid_sas [ 119.363826] CPU: 9 PID: 63 Comm: cpuhp/9 Not tainted 4.13.0-19-generic #22~lp1731031TwoReverts [ 119.364209] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 119.364687] task: 98cff8b49740 task.stack: b3274c7b8000 [ 119.364973] RIP: 0010:kfree+0x11c/0x160 [ 119.365133] RSP: 0018:b3274c7bbd60 EFLAGS: 00010246 [ 119.365356] RAX: f57a3bff0020 RBX: 98cf RCX: 0490 [ 119.365663] RDX: RSI: 98cfff25f4a0 RDI: 676f8000 [ 119.365964] RBP: b3274c7bbd78 R08: 0001f4a0 R09: bb5dcf6a [ 119.366262] R10: f57a3c00 R11: R12: bbf98e60 [ 119.366552] R13: bb1dd820 R14: 0009 R15: 0001 [ 119.366844] FS: () GS:98cfff24() knlGS: [ 119.367176] CS: 0010 DS: ES: CR0: 80050033 [ 119.367412] CR2: 55cc84772018 CR3: 000e48e09000 CR4: 001406e0 [ 119.367706] Call Trace: [ 119.367824] kfree_const+0x20/0x30 [ 119.367975] kobject_put+0x91/0x1a0 [ 119.368134] device_unregister+0x28/0x60 [ 119.368311] cpu_cache_sysfs_exit+0x5a/0xc0 [ 119.368486] ? free_cache_attributes.part.7+0x110/0x110 [ 119.368709] cacheinfo_cpu_pre_down+0x48/0x50 [ 119.368897] cpuhp_invoke_callback+0x84/0x3b0 [ 119.369082] cpuhp_down_callbacks+0x42/0x80 [ 119.369253] cpuhp_thread_fun+0x88/0xe0 [ 119.369433] smpboot_thread_fn+0xec/0x160 [ 119.369598] kthread+0x125/0x140 [ 119.369732] ? sort_range+0x30/0x30 [ 119.369882] ? kthread_create_on_node+0x70/0x70 [ 119.370075] ret_from_fork+0x25/0x30 [ 119.370233] Code: 08 49 83 c4 18 48 89 da 4c 89 ee ff d0 49 8b 04 24 48 85 c0 75 e6 e9 0e ff ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 1c [ 119.371052] RIP: kfree+0x11c/0x160 RSP: b3274c7bbd60 [ 119.371313] ---[ end trace edef5d0868ec0d2a ]--- The system continued to run, and I was able to issue other commands (ifconfig, efibootmgr), but I rebooted just to be safe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date:
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
4.13.0-12 seems to be OK; I ran it seven or eight times without a failure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: Triaged Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: Triaged Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
4.13.0-14 failed when offlining CPU 9: [ 104.500965] [ cut here ] [ 104.500968] kernel BUG at /build/linux-0p6sBa/linux-4.13.0/mm/slub.c:3878! [ 104.501256] invalid opcode: [#1] SMP [ 104.501422] Modules linked in: nls_iso8859_1 kvm_intel kvm irqbypass joydev input_leds ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler acpi_pad ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic igb crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid pcbc hid aesni_intel dca aes_x86_64 crypto_simd ptp glue_helper cryptd ahci pps_core i2c_algo_bit libahci megaraid_sas [ 104.503659] CPU: 9 PID: 63 Comm: cpuhp/9 Not tainted 4.13.0-14-generic #15-Ubuntu [ 104.504019] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 104.504537] task: 9a9838b6ae80 task.stack: b7e90c7b8000 [ 104.504827] RIP: 0010:kfree+0x11c/0x160 [ 104.505003] RSP: 0018:b7e90c7bbd60 EFLAGS: 00010246 [ 104.505311] RAX: d9d77eff0020 RBX: 9a98 RCX: 0001802a001a [ 104.505617] RDX: RSI: d9d77fe02400 RDI: 65a74000 [ 104.505938] RBP: b7e90c7bbd78 R08: 9a9838091ec0 R09: 0001802a001a [ 104.506255] R10: d9d77f00 R11: R12: 87798960 [ 104.506763] R13: 869dd4f0 R14: 0009 R15: 0001 [ 104.507216] FS: () GS:9a983f24() knlGS: [ 104.507638] CS: 0010 DS: ES: CR0: 80050033 [ 104.507884] CR2: 7ffdd8f1bff8 CR3: 0016ff209000 CR4: 001406e0 [ 104.508188] Call Trace: [ 104.508311] kfree_const+0x20/0x30 [ 104.508468] kobject_put+0x91/0x1a0 [ 104.508626] device_unregister+0x28/0x60 [ 104.508796] cpu_cache_sysfs_exit+0x5a/0xc0 [ 104.508971] ? free_cache_attributes.part.7+0x110/0x110 [ 104.509201] cacheinfo_cpu_pre_down+0x48/0x50 [ 104.509401] cpuhp_invoke_callback+0x84/0x3b0 [ 104.509616] cpuhp_down_callbacks+0x42/0x80 [ 104.509812] cpuhp_thread_fun+0x88/0xe0 [ 104.509997] smpboot_thread_fn+0xec/0x160 [ 104.510182] kthread+0x125/0x140 [ 104.510322] ? sort_range+0x30/0x30 [ 104.510491] ? kthread_create_on_node+0x70/0x70 [ 104.510706] ret_from_fork+0x25/0x30 [ 104.510870] Code: 08 49 83 c4 18 48 89 da 4c 89 ee ff d0 49 8b 04 24 48 85 c0 75 e6 e9 0e ff ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 2c [ 104.511761] RIP: kfree+0x11c/0x160 RSP: b7e90c7bbd60 [ 104.512003] ---[ end trace 2290fcc444ad32ff ]--- Bash remained active, but I couldn't issue any significant commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: Triaged Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: Triaged Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
The upstream 4.14.0 kernel DOES segfault, but none of the 4.13-series kernels does. Some of the 4.13-series kernels do have "error -19" or "error -22" messages in their dmesg output, though. I've tried the kernel at https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/unstable/+build/13358561, and it ran through the cpu_offlining script five times without error, so I think it's OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: Triaged Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: Triaged Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Joseph, I've just tested 4.15-rc4, and the script crashed and the system became responsive to only the simplest commands when bringing CPU 9 back up, accompanied by this out of dmesg: [ 166.722460] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, BIOS C240M4.2.0.10c.0.032320160820 03/23/2016 [ 166.722540] RIP: 0010:__kmalloc_track_caller+0xc5/0x210 [ 166.722578] RSP: :b75e8c7cbb08 EFLAGS: 00010206 [ 166.722615] RAX: RBX: 43ea0882f873c0e8 RCX: 01bf [ 166.722663] RDX: 01be RSI: RDI: 00021040 [ 166.722711] RBP: b75e8c7cbb40 R08: 9cc35d341eaa R09: 9ca3ff807c00 [ 166.722757] R10: b75e8c7cbd08 R11: bc159441a547de42 R12: 9cc35d341eaa [ 166.722805] R13: 014000c0 R14: 0007 R15: 9ca3ff807c00 [ 166.722852] FS: () GS:9cc3ff24() knlGS: [ 166.722905] CS: 0010 DS: ES: CR0: 80050033 [ 166.722945] CR2: CR3: 001be7e09001 CR4: 001606e0 [ 166.722992] Call Trace: [ 166.723020] ? idr_alloc_cmn+0x97/0xd0 [ 166.723051] ? kstrdup_const+0x23/0x30 [ 166.723081] kstrdup+0x31/0x60 [ 166.723107] kstrdup_const+0x23/0x30 [ 166.723137] __kernfs_new_node+0x2c/0x120 [ 166.723168] kernfs_new_node+0x28/0x50 [ 166.723197] kernfs_create_dir_ns+0x34/0x90 [ 166.723229] sysfs_create_dir_ns+0x40/0x90 [ 166.723261] kobject_add_internal+0xac/0x2b0 [ 166.723294] kobject_add+0x71/0xd0 [ 166.723323] ? device_private_init+0x23/0x70 [ 166.723356] device_add+0x12c/0x680 [ 166.723385] cpu_device_create+0xe1/0x100 [ 166.723418] ? __slab_alloc+0x20/0x40 [ 166.723449] ? _cond_resched+0x19/0x40 [ 166.723481] cacheinfo_cpu_online+0x29a/0x3f0 [ 166.723515] ? get_cpu_cacheinfo+0x50/0x50 [ 166.723549] cpuhp_invoke_callback+0x9b/0x550 [ 166.723587] ? padata_replace+0xf0/0xf0 [ 166.725151] cpuhp_thread_fun+0xc4/0x150 [ 166.726682] smpboot_thread_fn+0xec/0x160 [ 166.728221] kthread+0x11e/0x140 [ 166.729701] ? sort_range+0x30/0x30 [ 166.731145] ? kthread_create_worker_on_cpu+0x70/0x70 [ 166.732551] ret_from_fork+0x1f/0x30 [ 166.733906] Code: 4d 01 e0 4d 8b 18 4d 33 99 40 01 00 00 4c 89 c3 4c 31 db 65 48 0f c7 0f 0f 94 c0 84 c0 74 ac 4d 39 d8 74 14 49 63 41 20 48 01 c3 <48> 33 1b 49 33 99 40 01 00 00 0f 18 0b 41 f7 c5 00 80 00 00 0f [ 166.736776] RIP: __kmalloc_track_caller+0xc5/0x210 RSP: b75e8c7cbb08 [ 166.738188] ---[ end trace 39ce10746b0f4324 ]--- If you want direct access to the affected hardware, that can be arranged. (If you've already got access to the certification network in 1SS, the affected system on which I've been doing most of the testing is boldore.) I'm also happy to run tests using test kernels that you give me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in linux source package in Artful: Triaged Status in linux-hwe source package in Artful: New Status in linux source package in Bionic: Triaged Status in linux-hwe source package in Bionic: New Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
This bug is ***NOT FIXED!*** I've just confirmed it still exists on two systems. Note that the bug is specific to the 3.13 kernel series (it does not affect 4.4 or other kernel series), and to the EFI stub loader (it doesn't manifest when using GRUB 2, for instance). ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Trusty) Status: Fix Released => 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/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Dimitrenko, I'm afraid this bug is NOT FIXED. I've just tested with 3.13.0-123 (installed today via apt-get), and the system still hangs with it. Joseph, I'm still willing and able to test more kernels. ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Trusty) Status: Fix Released => 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/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, Do you have more kernels for me to test? It's been a while since you gave me the last 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/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
** Merge proposal linked:
https://code.launchpad.net/~rodsmith/checkbox-support/+git/checkbox-support/+merge/320862
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in checkbox source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager
]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
1: POSIX ADVISORY WRITE 4149 00:14:817 0 EOF
2: POSIX
[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
** Changed in: checkbox (Ubuntu)
Assignee: (unassigned) => Rod Smith (rodsmith)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rod Smith (rodsmith)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in checkbox source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager
]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
1:
[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
I've been looking at this (on and off), and it seems to reach close to
the end of UdevadmParser.run() (in udevadm.py) with the data intact, but
it gets lost in the last line or in transferring control out, in the
main() function of the udev_resource script.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in checkbox source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager
]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine:
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The kernel in linux- image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit3f049ea_amd64.deb fails to boot, but in different ways that seem to be somewhat random: * Sometimes the warnings "Failed to get file info size" and "Failed to alloc highmem for files" appear. * Sometimes, when launching from rEFInd, the above messages appear along with ASSERT messages from the UDK2014 tool kit used to build rEFInd, as shown in boot-failure.png. * Sometimes the message (shown in boot-failure.png) "ASSERT fsw_efi.c(674): CR has Bad Signature" scrolls across the screen and fills it entirely. (Note that fsw_efi.c is a rEFInd filesystem driver file; however, I've also tested booting the kernel from the FAT32 ESP, and even with the rEFInd filesystem driver never loaded, and the kernel still fails to boot, so this is not a filesystem driver problem per se.) * Sometimes (usually when doing a cold boot), the kernel loads but then panics, as shown in boot-failure-2.png. Note that I've tried to boot this kernel in many ways -- via rEFInd, via the VirtualBox EFI shell; from the ext4fs root (/) filesystem via the rEFInd ext4fs driver, and from the FAT32 ESP; cold booting and warm booting. None of these approaches has worked, but the failure symptoms vary and are somewhat inconsistent, even when booting in exactly the same way -- sometimes the screen hangs with errors, other times that scrolling message about "CR has Bad Signature" appears; and error messages can vary randomly from one attempt to another. ** Attachment added: "Boot failure messages including rEFInd/UDK2014 debugging messages" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+attachment/4826241/+files/boot-failure.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
** Attachment added: "boot-failure-2.png screen shot mentioned in previous comment." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+attachment/4826242/+files/boot-failure-2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The kernel in linux- image-3.13.0-9-generic_3.13.0-9.29~lp1649326_amd64.deb boots fine for me. Also, the newly-release 3.13.0-108 kernel in the regular repos does NOT boot; it crashes like everything else since 3.13.0-101. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
I just did an "apt-get dist-upgrade", and I see there's now a 3.13.0-110 kernel, too. It also crashes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The 3.15.0-0.1 kernel boots fine for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.16.0-23-generic_3.16.0-23.31_amd64.deb kernel (with its associated "extra" package) boots fine for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commitdaa829d kernel boots fine for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, I don't see the usual linux-image-* files at that URL. Could you please double-check that and fix as necessary? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit6edf523 boots fine for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux- image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commitf162bc9_amd64.deb kernel boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, I think there was a typo in your URL, since it was the same as from the previous test. Since you noted a different commit number, I adjusted and pulled the kernel from: http://kernel.ubuntu.com/~jsalisbury/lp1649326/59ed4b6/ This kernel fails to boot, with the "failed to get file info size/failed to alloc highmem for files" message as noted in post #20 of this bug report, rather than VirtualBox crashing, as described in my original bug report description. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, the linux- image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit74bdcac_amd64.deb kernel also boots correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux- image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit528f2d2_amd64.deb kernel boots correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, the 3.19.0-79.87 kernel boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, the 3.13.11-ckt39 kernel boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.13.0-031300 kernel boots fine, Joseph. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
linux-image-3.14.0-031400rc1-generic also boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
linux-image-3.14.0-031400-generic also boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.16.0-031600-generic kernel boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Abalan, you're subscribed to the "linux in Ubuntu" package, which is why you're receiving bug reports: https://bugs.launchpad.net/~fyma/+packagebugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, please note the following from the original bug report: I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux- image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit5bd4d89ffc2_amd64.deb (with linux-image- extra-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit5bd4d89ffc2_amd64.deb) kernel failed with the "failed to get file info size/failed to alloc highmem for files" messages noted earlier. The linux- image-4.10.0-041000rc3-generic_4.10.0-041000rc3.201701081831_amd64.deb kernel booted without problems. Both tests were in a VirtualBox VM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, any more kernels for me to test? It's been a while. Also, I ran across bug #1603476, which reports a failure with kernel 3.13.0-92 that might (or might not) be related to this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Yes, I installed both linux-image and linux-image-extra for all the kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
